Offline support is not complete when an app can display a cached screen. The harder problem is helping someone understand whether their new work has safely reached the business. A technician in a basement or a customer on a train may tap Save and immediately move on. The interface needs to distinguish a local draft, a queued change and a confirmed update.
Describe states in ordinary language
For an inspection app, use messages such as Saved on this phone, Waiting to send and Received by the office. Pair the status with the relevant job rather than relying on a tiny global symbol. Android's offline-first guidance treats local and network data as related parts of the data layer. The product implication is that the screen should not pretend there is only one instant state. Let users inspect pending work, retry when appropriate and see when information was last refreshed without understanding the underlying synchronisation mechanism.
Decide who wins a disagreement
Suppose a technician changes a job note offline while an office coordinator changes the same note. Automatically keeping whichever update arrived last can erase useful information. Identify which fields can be combined, which require one nominated owner, and which need a human decision. Photos and appended observations may merge naturally; a revised appointment time may not. Explain conflicts using the business meaning of the change. Showing two timestamps without the competing values leaves the person responsible for solving a puzzle the app created.
Rehearse the uncomfortable moments
Test loss of reception during saving, repeated taps, app termination, a flat battery and a switch between Wi-Fi and mobile data. Verify that a retry does not create a second inspection or duplicate a chargeable item. Give the user a safe path when storage is full or an attachment cannot be sent. If signing out would remove unsent work, make that consequence visible before it happens. Offline behaviour should be a rehearsed part of the working day, with a support process that identifies pending records without asking staff to recreate everything.
- Can staff tell local saving apart from confirmation by the office?
- Which edits can merge safely, and which require a named decision maker?
- What survives app closure, device restart or an unexpected loss of power?
- How does a user recover a stuck item without creating a duplicate?