Field Service Mobile App Development with Offline Sync
A field technician arrives at a client site, opens the app—and sees a white screen because there's no cellular network. The repair ticket, equipment history, inspection checklist—all frozen. Over 5 years, we've developed 20+ field service solutions where offline mode is a baseline requirement. But it's not just about missing internet. Sync errors, lost photos, unreadable signatures—each of these problems breaks SLAs and hurts reputation. Developing a field service mobile app with offline sync requires deep understanding of field work specifics.
Why Should a Field Service Mobile App Have Offline Sync?
A properly designed offline-first architecture reduces ticket closure time by 30–40% and cuts mobile data costs. Savings come from syncing data only when a network is available, rather than constantly. For example, a technician handling 10–15 daily tickets can save up to 2 hours per day.
How to Implement Offline Sync in a Field Service App?
For bidirectional sync, we use a local database (SQLite via Room or CoreData) and a sync queue. User actions are saved locally; when a network appears, data is sent to the server. Version conflicts are the most painful point. If two technicians close the same ticket offline, a merge strategy is needed. We typically use last-write-wins with an operation log or CRDTs for some data types (e.g., comments—append-only). This approach is 10x faster than direct HTTP upload—the technician doesn't wait for a server response. Learn more about CRDT. In one project, we cut waiting time from 30 seconds to under 1 second.
Example of sync conflict resolution
Two technicians simultaneously changed the status of the same ticket. One set it to "in progress", the other to "completed". Our strategy: priority by data version (last-write-wins), conflict recorded in a separate log. The dispatcher in the web interface sees the discrepancy and can manually resolve or accept the automatic decision.What Technical Problems Does a Field Service Mobile App Solve?
Photos and Media
A work completion report requires "before" and "after" photos. On Android, WorkManager with Constraints.Builder().setRequiredNetworkType(NetworkType.CONNECTED) is the standard way for deferred upload. But here's the nuance: WorkManager does not guarantee task order during batch upload. If photo order matters—we number them in the filename and enforce order on the server. To save traffic, we compress photos to 720p—average size 150 KB instead of 3 MB. Over a day, a technician uploads up to 50 photos—saving about 150 MB per device. WorkManager is the official task queue implementation.
On-Screen Signature
Canvas API (Android View.onDraw with Path, iOS UIBezierPath through CAShapeLayer) for capturing client signatures is simple—until you need high-quality PDF export. We use iText (Android) or PDFKit (iOS) to generate the report right on the device. The signature is saved as a vector path—this takes 100x less space than a raster image and scales perfectly for printing.
How to Optimize Routes for 10–15 Tickets a Day
The dispatcher sees all field technicians on a real-time map via WebSocket or MQTT from a broker (mosquitto / EMQX) to the mobile client. We send coordinates in batches every 30 seconds using FusedLocationProviderClient (Android) or CLLocationManager with desiredAccuracy: kCLLocationAccuracyNearestTenMeters (iOS)—not every second, to preserve battery. With this approach, the phone lasts a full workday (10–12 hours). Fuel savings from route optimization can reach 25% for a team of 10 technicians.
Optimal routing between 10–15 daily tickets is a Traveling Salesman problem, not solved on the mobile client. The server (Google OR-Tools, Vroom) computes the optimization; the mobile app only displays the route via Google Maps SDK or MapKit with turn-by-turn navigation via deep link to Maps/Google Maps. The route sheet is generated automatically based on optimization. In one project, this reduced mileage by 25% and freed up 2 hours of technician time per day.
Tech Stack and Architecture
For Field Service apps with a single codebase for iOS and Android, we choose Flutter or React Native with Expo. Flutter is preferred when custom widgets are required (custom inspection form, drag-and-drop for line items). React Native—if the client's team will maintain the code and has a JavaScript background.
Architecture: MVVM + Repository pattern. Local DB—SQLite (sqflite for Flutter, Room for native Android). Sync layer is a separate service, not mixed with business logic.
| Criteria | Flutter | React Native |
|---|---|---|
| Code reuse | 95% | 80% |
| Performance | High (Impeller) | Medium (Hermes) |
| Custom widgets | Excellent | Adequate |
| Team background | Dart | JavaScript/TypeScript |
Comparison of offline strategies:
| Strategy | Application |
|---|---|
| SQLite + Last-write-wins | Tickets, task statuses |
| CRDT (append-only) | Comments, action log |
| WorkManager + queue | Photos, signatures |
What's Included (Deliverables)
- Detailed documentation: offline data model, sync strategy, API specification.
- Source code with comments and CI/CD (GitHub Actions / GitLab CI).
- MDM configuration for corporate app distribution.
- Preparation of marketing materials for App Store and Google Play.
- Training for administrators and technicians (2–3 sessions).
- 3 months of technical support after release.
Our Expertise
We have been working for over 5 years and have completed 22 field service projects, including an app for vending machine maintenance (200 technicians, 8–15 locations per day). Average NPS across projects is 9.2. We use only licensed software and certified SDKs. Our team holds certifications in AWS, Google Cloud, and Flutter.
From Practice
One of our clients, a vending machine maintenance company, deployed an app for about 200 technicians, each handling 8–15 locations daily. The main mistake in the first version was triggering sync on every user action via a direct HTTP request. On poor networks, this made the technician wait 30 seconds after each item closure. We rewrote it to an operation queue (SQLite table pending_operations + WorkManager)—the technician works instantly, sync happens in the background. Complaints about "the app is slow" dropped to zero. Time savings amounted to up to 40% per ticket closure.
Stages
- Audit of the existing system (ERP, CRM, dispatch module)—we figure out what to sync with.
- Design of the offline data model and conflict resolution strategy.
- UI design considering use with gloves and in bright sunlight (contrast, large buttons).
- Development and phased integration with backend.
- Pilot with a group of technicians (10–20 people) before full rollout.
- Publication in App Store and Google Play with MDM profile for corporate devices.
Timelines range from 6 weeks (simple app with tickets and checklists) to 4–6 months for a full platform with dispatch module, routing, and ERP integration. The cost is calculated individually after requirements analysis. Typical project costs start from $30,000 and vary based on complexity. Get a consultation on field service app development.