Field staff, rural branches and travelling teams often work where connectivity is weak or unavailable. An app that stops working without a signal forces people back to paper. Offline-first design treats the connection as a bonus rather than a requirement.
What offline-first means
An offline-first app stores the data it needs on the device, lets the user keep working without a connection and synchronises changes with the server when a connection is available. The user should rarely need to think about whether they are online.
Decide what must work offline
Not every feature needs to. Identify the tasks people must complete in the field, such as recording a visit, capturing a photo or completing an inspection, and the reference data they need to do so. Features like administration or reporting can often remain online-only.
Store data locally and safely
- Use a proper on-device database rather than temporary storage.
- Encrypt sensitive information stored on the device.
- Limit how much data is cached to what each user actually needs.
- Plan for lost or shared devices, including remote sign-out where possible.
Synchronisation is the hard part
When two people change the same record offline, the app must decide what happens. Common strategies include:
- Last change wins: simple, but can silently overwrite work.
- Field-level merging: combine changes to different fields of the same record.
- Conflict review: flag genuine conflicts for a person to resolve.
Choose a strategy per type of data. Inspection results might be append-only, while customer details may need review.
Make status visible
Users need confidence that their work is safe. Show clearly which items are saved on the device, which are waiting to sync and which have synchronised. Never discard unsynchronised work without warning.
Sync efficiently
Send only changes rather than complete datasets, compress where possible and retry automatically with sensible delays. Large files such as photos can upload in the background, preferably when the device is on Wi-Fi if data costs are a concern.
Test in realistic conditions
Test with the network switched off, with intermittent connections and with long periods offline. Many synchronisation problems only appear when real people work in real places.
Offline-first apps take more design effort than always-online apps, but for teams working beyond reliable coverage they are the difference between a tool people use and one they abandon.
