Mobile App Development
A field-service app that works without signal
An illustrative engagement, written from how we work. Client details are withheld and no outcome figures are claimed.
Context and constraints
The situation this example is drawn from: field technicians logging work orders, inspections and photos in locations where mobile connectivity couldn't be assumed — basements, rural sites, and buildings with poor signal. The existing approach was paper forms, photographed and emailed at the end of the day, with a real lag between work being done and the office knowing about it.
Approach
Survey work centred on the device constraints and the environments technicians actually work in, not an office-based assumption of connectivity. Key decisions:
- Design for offline-first from the start — every screen had to function with no network, syncing when a connection reappeared.
- Resolve sync conflicts deterministically (last-completed-action wins per record) rather than surfacing a manual merge decision to a technician mid-job.
- Keep the interface to what a technician could operate one-handed, on a device that might be in a work glove.
Architecture Decisions
Offline-first local storage with background sync
the app is fully usable with zero signal; sync happens automatically once connectivity returns.
Deterministic conflict resolution
no manual merge step required in the field.
Native camera and location APIs
not a web-view wrapper — reliability mattered more than code-sharing convenience for these two features specifically.
Minimal, glove-friendly interface
large tap targets, short forms, no dependency on precise multi-touch gestures.
What Shipped
ENTRY — RESULT
A cross-platform field-service app that technicians use fully offline, with automatic sync once back in signal range. The end-of-day paperwork lag — work completed but not visible to the office until the technician was back at a desk — was replaced by near-real-time visibility once a device reconnects.