FIELD-SERVICES WORKFORCE — MOBILE APP DEVELOPMENT
Trilha Field Ops
Job logging time down from 6 minutes to under 90 seconds.
The problem
A previous mobile project, built by a generalist agency, had shipped an Android-only app that technicians largely ignored because it required a data connection field crews often didn't have. The team needed a mobile product planned for both platforms and for genuinely offline conditions from the start, not retrofitted after launch.
Trilha's field technicians logged completed jobs on paper forms, photographed and emailed at the end of each shift — often the next day, when details had already blurred.
Our approach
- Mobile Product Blueprint (1 week) — Platform decision (cross-platform, for one codebase across both stores), offline-first data sync plan, store-readiness checklist.
- Build — Offline-capable job logging with background sync, camera integration for job photos, both app stores targeted from the same build.
- Store submission — Both stores submitted together; one round of review feedback addressed before approval.
- Rollout — Phased rollout across field teams, starting with the crew that had abandoned the previous app.
Outcome
| Metric | Before | After |
|---|---|---|
| Average time to log a completed job | ~6 minutes (paper + email) | Under 90 seconds |
| Platforms supported | 1 (Android only, prior app) | 2 (iOS + Android) |
| App store review rounds to approval | — (prior app: 3) | 1 |
What Trilha Field Ops said
“The last mobile build only worked for half our team's phones and needed signal our crews often don't have in the field. This one was planned for both from day one, offline included — and it's the first version people actually use.”
Diogo Serra — Operations Director, Trilha Field Ops
