Mobile apps for field teams: forms, photos and offline
What a field app must do to be trusted in a van, a basement or a rooftop, and how to choose between web, hybrid and native for it.
The short answer
A field app has a short list of jobs done repeatedly under bad conditions: show the next job, capture forms, photos and signatures, and get all of that back to the office. The conditions are the design brief: no connection in the basement, gloves on the rooftop, sun on the screen, a customer waiting, an interruption mid-form. An app trusted in those conditions stores everything locally first, syncs when it can, shows exactly what has and has not been sent, and never loses an entry. A progressive web app covers many field needs; native or hybrid earns its place for heavy offline data, reliable background sync and device features the web cannot reach.
What a field app must do
| Job | What good looks like | Common failure |
|---|---|---|
| Next job | One screen: where, what, who, with directions and history | Searching a list; details in another system |
| Forms | Defaults from the job; minimal typing; resumable; validation that helps | Long forms that reset when interrupted |
| Photos | Capture, annotate, attach; compressed; queued upload in background | Uploads that block; photos lost offline |
| Signatures and proof | One screen, timestamp, location, attached | Proof that cannot be found later |
| Offline | Everything above works with no connection; sync when possible; status per item | ”No connection” errors; silent data loss |
| Status | What is saved, syncing, sent, failed, per item | No idea whether the office received anything |
| Speed | Under a few seconds per action | Spinners between every step |
Designing for the conditions
- Shadow the team for a shift and note every point of friction: the wait, the retype, the lost photo, the small button.
- Reduce every form to what the office actually uses; pre-fill from the job; make the rest optional.
- Large targets and high contrast, tested in sunlight with gloves.
- Store first, always; sync in the background; show per-item status; never block the next job on an upload.
- Make forms resumable across interruptions and restarts.
- Test the connection cut at every step on real devices, including cheap ones.
- Ship to the team early, watch them use it, and iterate weekly.
Web, hybrid or native
A progressive web app: one codebase, no app stores, installed to the home screen, offline forms and photos and location on modern devices. Right for most inspection, delivery and service teams. Hybrid: web code in a native shell for store distribution and more device access. Native: full device capability, best background behaviour and performance, at the cost of two codebases. Choose from the tasks: barcode scanning at speed, large offline datasets, reliable background sync and specialised hardware push towards native; forms, photos, signatures and location do not.
What this means for you
Build field apps offline-first, for gloves and sun and hurry, around the few jobs done all day: next job, forms, photos, proof, sync with visible status. Choose web, hybrid or native from the tasks rather than from habit. Test in the worst conditions before the best. The app the team trusts in the basement is the one that replaces paper for good.
Frequently asked questions
Can a field app be a web app, or must it be native?
A progressive web app installed on the home screen handles offline forms, photos, signatures and location on most modern devices, without app stores, with one codebase. It is the right start for many field teams. Native or hybrid earns its place when the app needs large offline datasets, reliable background sync, barcode scanning at speed, or device features the web cannot reach. Decide from the tasks, not from habit.
What do field workers actually complain about?
Apps that lose their entries when the connection drops, forms that cannot be paused and resumed, small buttons, too much typing, slow photo uploads that block the next job, and no way to see what has actually been sent. Every one of those is a design decision, and each fixed one raises trust and adoption.
How do photos work offline?
They are captured and stored on the device, compressed sensibly, attached to the job and queued; they upload in the background when a connection appears, with progress visible and the worker free to continue. Photos that must upload before the next job can start are the reason field workers turn off the app and use their camera roll.