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.
How to Integrate Maps and Geolocation in Mobile Apps: Google Maps, MapKit, Geofencing, Tracking
We integrate geolocation and mapping services into mobile apps—it's more than just "adding a map." It involves permission setup, managing accuracy and power consumption, and accounting for iOS and Android specifics. Whether it's a delivery tracker, running app, or store locator, each case requires a tailored approach. Contact us for a free project assessment within 2 hours.
Permissions: One of the Most Common Sources of Bad Reviews
On iOS, location permission is the most sensitive after microphone and camera. Since iOS 14, the system shows an indicator in the status bar when location is used in the background—users notice this. NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription must contain honest explanations, otherwise the app may be rejected during review. Requesting always permission immediately on launch is a sure way to get denied by 80–90% of users. The correct flow: first request whenInUse, then always only when the user reaches a feature that requires it, with a clear explanation of why.
On Android (API 29+), ACCESS_BACKGROUND_LOCATION is a separate permission that cannot be requested together with foreground. First request foreground permission, then background separately. Google Play requires justification for background location in a questionnaire during publication. If the justification is weak, the app may be rejected or forced to remove background location. Over 5 years of work, we have successfully completed over 20 reviews; none of our apps were rejected for this reason.
Accuracy and Power Consumption: How to Avoid Battery Drain
Continuous GPS at maximum accuracy consumes 100–150 mW—battery drains in 4–6 hours. For most tasks, this is excessive.
On Android, FusedLocationProviderClient (Google Play Services) combines GPS, Wi-Fi, and cellular network, selecting the optimal source. LocationRequest.Builder with priorities:
-
PRIORITY_HIGH_ACCURACY — GPS on, for navigation
-
PRIORITY_BALANCED_POWER_ACCURACY — accuracy ~100 meters, Wi-Fi + cellular
-
PRIORITY_LOW_POWER — accuracy ~10 km, only cellular
-
PRIORITY_PASSIVE — coordinates from other apps, no active request
For a running tracker in active mode—HIGH_ACCURACY with 2–5 second interval. For geofencing background notifications—PASSIVE or LOW_POWER; the system wakes up on event. GPS accuracy is well-documented.
On iOS, CLLocationManager with desiredAccuracy (kCLLocationAccuracyBest, kCLLocationAccuracyHundredMeters, etc.) and distanceFilter—minimum movement in meters before next update. For route tracking with battery saving: desiredAccuracy = kCLLocationAccuracyNearestTenMeters, distanceFilter = 10—updates only on actual movement.
Significant Location Changes—iOS mode that works at OS level without active GPS: updates on cell tower change, minimal battery drain. Accuracy ~500 meters—suitable for logging user location history, not for navigation.
How to Choose a Mapping SDK? Comparative Analysis
| SDK |
Platform |
Offline Maps |
Custom Style |
No Google Services |
| Google Maps SDK |
iOS/Android |
No (only Maps API) |
Yes (Cloud-based) |
No |
| MapKit |
iOS |
No |
Limited |
Yes |
| Mapbox Maps |
iOS/Android |
Yes |
Fully |
Yes |
| HERE Maps |
iOS/Android |
Yes |
Yes |
Yes |
| OpenStreetMap + MapLibre |
iOS/Android/Flutter |
Yes |
Fully |
Yes |
Google Maps SDK is the default choice for most projects: familiar UI, good documentation, Directions API, Places Autocomplete. Limitation—dependency on Google Play Services (issue for Huawei) and pricing at high request volumes (paid after certain usage).
Mapbox is preferable when you need custom map styles (corporate branding, dark theme), offline maps for offline work, or compatibility with devices without GMS. MapboxNavigation SDK provides full navigation with voice instructions, route recalculation, and lane guidance. Mapbox renders polygons 2x faster when loading 500+ markers compared to Google Maps—confirmed by our load tests.
For Flutter—google_maps_flutter (official), flutter_map (OpenStreetMap + MapLibre, fully open-source), mapbox_maps_flutter (after official SDK release).
Example: App with Offline Maps and Geofences for 100+ Points
A retail chain client needed a map with offline mode and push notifications on store entry. We chose Mapbox—it supports downloading entire regions and offline geocoding. Result: zero network failures, 30% battery reduction due to PASSIVE mode.
Why Does Geofencing Have Delays?
Geofencing triggers an event on entry/exit of a geographic zone (circle of given radius). In practice, delay can be 1–3 minutes—the cost of energy efficiency.
On Android—GeofencingClient from Google Location Services. Add Geofence objects with setTransitionTypes(GEOFENCE_TRANSITION_ENTER | GEOFENCE_TRANSITION_EXIT) and PendingIntent for BroadcastReceiver. Limitations: max 100 active geofences per app, minimum radius ~150 meters (due to accuracy), delay of several minutes for battery saving.
On iOS—CLCircularRegion + CLLocationManager.startMonitoring(for:). Limit: 20 regions per app. The OS decides when to check—developer cannot control delay. For more precise geofencing with small radius—iBeacon (CLBeaconRegion) or CLVisit for places where user spent time.
If you need more than 20 (iOS) or 100 (Android) zones—server-side logic is required: periodically send coordinates to server, server checks zone entry and sends push. Less time-accurate but scales to thousands of zones. Geozone working principles are well-documented.
Route Tracking and Background Geolocation
Tracking a run or a courier route in the background are technically different tasks.
On iOS, background geolocation works via UIBackgroundModes: location in Info.plist. Without this key, when the app goes to background, CLLocationManager gets a few minutes and then sleeps. With the key, it works continuously, but the system may pause it at critically low battery.
For a running tracker on iOS: startUpdatingLocation at start of workout, write coordinates to Core Data every 5 seconds; on pause—stopUpdatingLocation, but keep startMonitoringSignificantLocationChanges to avoid losing the app's position completely.
On Android for courier tracking, you need a Foreground Service with FOREGROUND_SERVICE_TYPE_LOCATION (mandatory from API 29). Foreground service shows a persistent notification—this is a platform requirement, not a bug. Without it, Android Doze will kill location updates. WorkManager for background tasks is not suitable—it does not guarantee continuity.
Algorithmic part of route tracking: raw GPS coordinates are noisy. For smoothing—Ramer-Douglas-Peucker algorithm for track simplification or Kalman Filter for real-time noise filtering. Without filtering, the track looks like random zigzags, and the estimated distance is 20–30% more than actual.
How We Implement Maps and Geolocation: Step-by-Step Process
-
Scenario Analysis—determine foreground/background needs, accuracy, number of geofences, offline requirement.
-
SDK and Architecture Selection—compare Google Maps, Mapbox, HERE, MapKit based on project criteria (use our comparison as a baseline).
-
Integration and Permission Setup—configure
Info.plist / AndroidManifest.xml, test review checks (App Store Review Guidelines Sections 4.2/5.1, Google Play policy).
-
Tracking/Geofencing Implementation—add
CLLocationManager / GeofencingClient, configure filters and power saving.
-
Unit and Integration Testing—on real devices (emulator does not simulate delays or Doze/App Nap behavior). Test at least 50 scenarios.
-
Load Testing—simulate 500+ markers, moving objects, check FPS and battery consumption.
-
Deployment and Monitoring—release via TestFlight / Firebase App Distribution, collect crashlytics logs, track permission denial rates.
Timeline and Deliverables
| Stage |
Timeline |
Deliverables |
| Basic map integration with markers and search |
1–2 weeks |
Source code (Swift/Kotlin/Dart), API documentation, build instructions |
| Geofencing with push notifications |
2–3 weeks |
Geofence code, FCM/APNs setup, test zones, delay report |
| Full route tracking (background, smoothing, server sync) |
4–6 weeks |
Code with Kalman filter, server part (optional), battery monitoring |
What you get in any case:
- Source code with comments (Swift, Kotlin, Dart, TypeScript)
- Integration with your backend (REST/GraphQL/WebSocket)
- 1 month support after delivery (bug fixes, help with store reviews)
- Guide for publishing to App Store and Google Play (including background location justification)
- Code signing certificates, provisioning profiles, Google Maps/Mapbox keys
Our expertise: 10+ years in mobile development, 50+ geolocation projects, certified Apple and Google developers (Google Associate Android Developer). Every app undergoes triple code review and load testing.
Order turnkey map and geolocation integration—contact us for a consultation and preliminary project estimate within 2 hours.
