An app for engineers, surveyors, site teams or community nurses has to do its whole job with no signal: load the day's work, capture the forms, photos and signatures, and sync when a connection comes back. That is what offline mobile app development means, and for field work it is the starting point, because on Ofcom's own figures a team on one network contract will regularly be somewhere that network does not reach, and indoors the numbers get worse. When the app fails on site, the work goes onto paper and someone in the office types it up again. Offline has to be designed into the first build. Adding it later is, in our experience, close to a rebuild.
Why does a field app need to work offline?
Because the UK's 4G headline counts any network, and your team is on one. In January 2026, Ofcom put 4G across 96% of the UK landmass from at least one network and 84% from all four. In its July 2025 figures, each operator on its own covered 89% to 90%. Scotland has no 4G from any network across 9% of its land.
Indoors at rural premises it is worse. Ofcom predicts indoor 4G from all four networks at only 64% of rural premises, and between 13% and 18% of rural premises have no indoor 4G at all from any one network, depending on which network it is. A farm office, a village surgery, a rural plant site or a patient's home can all fall into that gap.
What happens to signal inside buildings?
It drops further than the coverage maps assume. Ofcom's indoor figures subtract a single 10 dB building loss from the outdoor signal, and Ofcom itself says the real experience depends heavily on building materials and insulation. The international model for this, ITU-R P.2109-2 (2023), treats traditional buildings and thermally efficient ones (metallised glass, insulated cavity walls, foil-backed cladding) as two separate groups. On our calculation from its published coefficients, the typical loss is around 15 dB for the first group and 31 dB for the second, which means roughly 35 to 50 times less signal reaching the inside of a modern insulated building.
When Ofcom measured nine public buildings in Greater Manchester for its June 2026 discussion paper, it found that buildings with thick walls, dense materials or deep internal spaces "often blocked signals almost completely", and that the problems "were not limited to basements or corners". Plant rooms, risers and basements are where a lot of maintenance work happens.
Coverage does not guarantee a connection either. Ofcom's Mobile Matters report (October 2026) puts the 4G data connection success rate at just over 96%, which on our arithmetic is up to one attempt in 25 failing, and Ofcom notes that its crowdsourced data cannot see the places with no coverage at all.
What happens when a field app fails without a signal?
The work goes onto paper, and then someone enters it twice. The Queen's Nursing Institute's survey of community nurses (run in 2022, published in 2023) found that 87% of district nurses reported poor connectivity when seeing patients and 27% had to enter data they had already entered; one described doing full assessments by "writing them by hand then rewriting them back in the office". NHS England's guidance for community health workers now says "connectivity can never be guaranteed 100% of the time" and that offline mode design is important, and Mid Cheshire Hospitals NHS Foundation Trust writes into its business cases that community software must work offline.
We see the same pattern outside healthcare. AssetSnap's founders came to us because asset registers were being built by a surveyor with a clipboard and typed up afterwards. Asset Snap was built for Ministry of Defence sites where phones have no connection, so capture works offline and syncs when a signal returns. SourceGo does the same for research nurses running clinical trial visits in patients' homes, and the Classeq engineer app stores its service data locally and sends it when a connection is available.
What does offline mobile app development involve?
Designing the app around a copy of the data on the phone, with the server as the place it syncs to. Google's own guide to building an offline-first Android app starts in the data layer: the local data is the "canonical source of truth", and the screens "must never communicate directly with the network layer". For a field app that means:
- the day's jobs, forms, reference data and drawings downloaded before the engineer leaves signal
- every entry, photo and signature saved on the device first, so nothing is lost if the app closes
- changes queued and sent in the background, in order, when a connection returns
- rules for what happens when two people change the same record while offline
- a visible sync status, so nobody has to guess whether the office has the job sheet
- photos and large files sent separately, so a weak signal does not hold up everything else
Microsoft tells its own Field Service customers to set up offline capabilities "even if you think your field technicians always have a reliable Internet connection", and lists the features that do not work offline. Offline gets decided feature by feature, at design time.
Can you add offline to an existing app?
You can, but it is rarely a small change. An app whose screens call the server directly has to be restructured around a local store before it can work without one, which is Google's rule above in reverse, and in our experience that touches most of the app. Sync and conflict rules are cheaper to agree in a discovery than to retrofit after the engineers have stopped trusting the app.
Whether the field side works offline is one of the things that moves the price of a business system, which typically costs £15,000 to £60,000 excluding VAT on our published cost guide. Every field app on our construction and field service page works offline, and so do the engineer tools in our connected device and healthcare work.
If your field team keeps a paper backup for when the app drops out, get in touch.