A complete overhaul of how the app handles long stretches without signal. Records lock locally, sync resumes automatically when you're back.
Australian freight routes spend a lot of time outside coverage. An EWD that quietly depends on a connection is not an EWD; it is a form that sometimes works. So we rebuilt the storage and sync layer around the assumption that there is no signal, and treated connectivity as the exception.
Records lock locally
Every status change is written to encrypted storage on the device the moment you make it, sequenced and locked at that point. Nothing waits on a network round trip, and nothing is held in memory hoping for a tower.
The record you can see at the roadside is the record that was written, whether or not it has reached us yet.
Sync resumes on its own
When signal returns, the queue drains in order. Entries are de-duplicated on the way in, so a flaky connection that drops mid-upload cannot produce a double record.
There is no sync button, because a sync button is a thing you can forget to press at the end of a fourteen-hour day.
What drivers notice
Ideally, nothing — which was the point. The visible change is that the app no longer stalls or warns when you are out of range; it simply keeps recording.
