The basement has no signal. The job still has to be recorded.
Think about where the work actually happens. A basement storage cage. A service lift between floors twelve and fourteen. A steel-clad warehouse. A farm road two hours past the last tower.
Every one of those places kills mobile data, and every one of them is where a crew is expected to photograph a scratch, tick an inventory line, or collect a signature.
An offline failure is not a delayed request
Most field apps treat connectivity as a temporary inconvenience. The request spins, then fails, then shows a toast nobody reads. The crew is standing in a customer's hallway with a job to finish, so they do the rational thing: they carry on without the app.
That is the real cost. You did not lose an HTTP request. You lost the condition report on the antique sideboard, the photo of the pre-existing dent, and the customer's signature confirming the count. Those are the three things you will want in ninety days when a claim lands.
And nobody backfills them. The crew has moved on to the next job, and reconstructing a walkthrough from memory produces a document that is worse than useless, because it looks authoritative and is not.
Offline as the normal case
Moveezi Field treats no signal as the expected state, not the error state. The job, the inventory, the property walk and the signature capture all work with the aircraft mode switch on. Everything queues on the device and syncs the moment the phone reconnects, in the background, without anyone pressing anything.
The crew never sees a spinner and never makes a judgement call about whether to wait. From their side there is no difference between a signal and no signal, which is the only design that survives contact with a real move.
The test that matters
If you are evaluating any field app, do this before you sign: put the phone in aircraft mode, complete a whole job, then turn the signal back on and confirm every photo and signature arrived.
It takes four minutes and it tells you more than the demo will.