Case study
Works where
there is no signal.
Field crews entering data in basements, on sites and in vehicles. The connection is the exception, not the rule.
Offline first
Sync model — the network is treated as optional
The problem
Their existing tool was a web app in a wrapper. It worked in the office and failed in exactly the places the work happens, so crews kept paper notes and typed them up later — which meant the data was always a day old and occasionally invented.
Any fix had to survive a phone that had been offline for a full shift and then reconnected next to three colleagues doing the same thing.
What we did
Native, offline-first, with conflict resolution designed before the interface. We wrote down what should happen when two people edit the same record on the same day with no connection, and built to that answer rather than discovering it in testing.
The backend was built alongside the app rather than bolted on afterwards, which is why sync is boring — the interesting decisions were made once, at the start.
What changed
Crews enter data where the work happens and it is correct when it arrives. The paper step is gone.
We handle the App Store releases, the annual iOS upgrades that break things, and the retainer that covers both.
Tell us what you are trying to ship.
A real technical opinion back within two business days — not a sales call.
