Field apps that work without a signal
A field app that needs a connection fails exactly where it is needed most. Property technicians, for example, spend much of the day in plant rooms and basements with little or no signal. Building for that properly is a design decision made on day one, not a feature added later.
Treat the phone as the place work is saved
An offline-first app saves every action on the device first and shows it as done. Sending it to the server is a separate step that happens whenever a connection is available. The person in the field never waits for the network.
Give every action an identity
Each job update, photo or signature gets a unique ID created on the phone. When the app reconnects and sends a backlog, the server recognises anything it has already received. Nothing is lost if the upload stops halfway, and nothing is recorded twice when it is retried.
Download only what the person needs
Sync the technician’s own jobs, the assets at their sites and the forms they use — not the whole database. Then fetch only what has changed since the last sync. Small, incremental downloads are fast on weak connections and kind to data plans.
- Keep a “last synced” marker per device and ask only for newer changes.
- Mark deleted records as deleted rather than removing them, so devices learn about removals.
- Compress photos on the device before upload.
- Show a clear sync status, including how many items are waiting.
Decide what happens when two people change the same thing
Conflicts are rare but certain. Decide the rule in advance for each kind of record: the latest change wins, the office wins, or the conflict is shown to a person to resolve. Most problems come from never having decided.
Test it in the basement
Airplane mode on a desk is not a field test. Use the app where it will really be used, lose the signal mid-upload, and check the office sees exactly what the technician did.
Software Project Brief Template
A 3-page, fill-in brief that gets you a sharper estimate from any developer.
- 3-page PDF
- About 45 minutes
- Print or fill on screen
More articles
Planning
Build or buy: when custom software is the right call
Off-the-shelf software is usually the right answer — until the way you work is the thing that sets you apart. A practical test for deciding, and the middle path most businesses miss.
Planning
How to brief a software project so the quote means something
Two quotes for the same project can differ five-fold because each team imagined a different system. A one-page brief that makes estimates comparable — and what to leave out.
Commercials
Fixed price or time and materials: how to pay for software
Fixed price feels safe but prices in uncertainty; time and materials is flexible but needs trust. When each fits, and the phased model that combines the strengths of both.
Start a project
Planning something like this?
Tell us what the software has to do and who will use it. We reply within one business day.