The van goes out and the day comes back incomplete
Deliveries, inspections and site visits happen where the connection does not. Paper catches up eventually, or it does not.
What it looks like from the inside
An app that needs a signal is an app that stops working exactly where the work happens. Drivers then keep a paper list, the office keys it in later, and both copies drift. When the office changes a job while the phone is offline, somebody has to decide which version wins, and usually nobody decided in advance.
Offline is not a feature you bolt on at the end. It is a decision about what the phone owns, what the server owns, and what happens when they disagree.
- Work is recorded twice: once on the phone, once on paper
- Jobs reassigned by the office arrive late or not at all
- Sensor and telemetry readings are only checked after something spoils
- Nobody can say what a driver actually did, in order, on a given day
What we do about it
Decide what the phone owns
Work done offline is queued on the device and never lost. The queue syncs in order when the connection comes back.
Write down the conflict rule
When the office and the phone disagree, a rule you can read decides, and the person sees what changed rather than having their work silently overwritten.
One codebase, both stores
React Native for iOS and Android, with the release pipeline set up before the first build so shipping is not a person following a checklist at midnight.
Bring the hardware in
Where there is telemetry, a cold box or a tracker, the readings land somewhere useful and alert before the loss rather than after it.
What you end up with: signed iOS and Android builds, both store listings, an automated release pipeline, and a sync rule your team can explain
The services this draws on
Other weeks that are not working
Does this sound like you?
Send a paragraph about how it shows up in your week. We reply within two working days with questions, a rough shape, and an honest answer on whether we are the right people for it.
Start a project