Driver App Development: Key Architecture and Features for Taxi

The driver app is technically the most complex of the three system clients (driver, passenger, dispatcher). It must work in the background for hours, accept orders even with unstable internet, track the route accurately, and not drain the phone battery during a shift. On Android 13+, the system kills background services after 3 minutes if requirements are not met. This happened with one client: drivers complained they didn't see new orders. We had to rework the location module to use a ForegroundService and add a persistent notification. After that, order loss dropped by 25%. Our team has over 5 years of experience and 50+ completed projects in mobile development. Proper architecture saves up to 40% of time on post-launch refinements. We develop such apps turnkey. Typical development cost starts from $30,000.

How to organize background geolocation in a taxi driver app?

The driver doesn't hold the phone constantly. The app must receive orders via push, track the route, and update the server every 3–5 seconds. On iOS we use CLLocationManager with allowsBackgroundLocationUpdates. We disable pausesLocationUpdatesAutomatically. In standby mode, we switch to significant-change for battery saving. On Android — ForegroundService with a notification. Without it, MIUI 14, EMUI 12, and Samsung OneUI 6 kill the process within 5–10 minutes. We use FusedLocationProviderClient with PRIORITY_HIGH_ACCURACY during trips and PRIORITY_BALANCED_POWER_ACCURACY while waiting. Switching based on order status. According to Android documentation, ForegroundService is the only way. ForegroundService is 2–3 times more reliable than background services for Android location tracking.

How to ensure reliable order reception with poor internet?

New orders arrive as FCM/APNs data pushes. The driver accepts or declines — this must work even with a poor connection (tunnels, parking garages). Correct scheme: local queue of accepted/declined decisions with retry logic on WorkManager (Android) or BackgroundTasks (iOS). If the response doesn't reach within 10 seconds, retry, otherwise the dispatcher considers the order not accepted. Using MQTT with QoS 1 guarantees faster message delivery than standard REST. Order acceptance timeout is a classic pitfall. The server gives the driver 15–20 seconds. If the push is delayed (FCM can delay up to several minutes in Doze mode) — the driver sees the order, taps 'accept', gets an error 'order already assigned'. Solution: include the order creation timestamp in the push payload, the client checks the order age before displaying the dialog. A local queue with WorkManager reduces data loss by 90%.

Why is the order state machine important?

The driver app is strictly a finite state machine. States:

Each transition is a request to the server with confirmation. The UI blocks buttons until the response is received to prevent double taps. 'Arrived' button pressed twice is a real problem: the driver pressed the button, no response (network lag), pressed again, both commands reached. The server must be idempotent for transitions, the client must show a spinner and block repeated taps until the response.

How to choose a navigation SDK for taxi?

Map integration is key. For the driver app, turn-by-turn with voice instructions is compared to offline maps, Mapbox is 30% faster in rerouting. Mapbox Navigation SDK for iOS and Android provides a ready-made NavigationViewController/NavigationView with customizable UI. Google Maps does not provide a ready turn-by-turn UI — you'd have to build it yourself using Directions API + TTS. Mapbox requires less integration time than Google Maps with custom implementation. Also available are 2GIS (good CIS coverage) and HERE Navigation SDK (real-time traffic). The choice depends on operating regions and budget. Rerouting on deviation — should trigger automatically when the driver deviates from the route by more than 50–100 meters. Mapbox has this built into the SDK, Google requires custom implementation.

What architecture suits a taxi app?

Clean Architecture with layers: presentation (ViewModel/BLoC), domain (use cases), data (repositories). For cross-platform — Flutter with native modules for location and push; for native — Swift + UIKit/SwiftUI on iOS, Kotlin + Jetpack Compose on Android. Real-time data exchange — WebSocket or MQTT for coordinates and statuses. MQTT is preferable for unstable connections: QoS 1 guarantees delivery, low overhead, built-in reconnect. ProGuard/R8 configuration requires rules to preserve models and Location API.

What's included in the work

• Design of order FSM and architecture
• Implementation of location module with background mode
• Integration of navigation and push notifications
• Configuration of code signing and provisioning profiles (iOS), ProGuard/R8 (Android)
• Publication to App Store and Google Play, including TestFlight and Firebase App Distribution
• API and code documentation
• Training drivers on app usage
• Post-release support for one month

What are the stages and timeline?

1. Analysis of driver work scenarios — 1–2 weeks
2. Design of FSM and architecture — 1–2 weeks
3. Development of location module — 2–3 weeks
4. Integration of navigation and push — 2–3 weeks
5. Integration with backend — 2–3 weeks
6. Testing on real devices — 1–2 weeks
7. Publication — 1 week

Total timeline: from 8 to 16 weeks. Cost is calculated individually, based on integration complexity and platform requirements.

With over 5 years in the market and 50+ completed projects, we have the expertise to deliver. Get a consultation on app architecture and development timeline. Contact us to discuss your project.

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

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

1. Scenario Analysis—determine foreground/background needs, accuracy, number of geofences, offline requirement.
2. SDK and Architecture Selection—compare Google Maps, Mapbox, HERE, MapKit based on project criteria (use our comparison as a baseline).
3. Integration and Permission Setup—configure Info.plist / AndroidManifest.xml, test review checks (App Store Review Guidelines Sections 4.2/5.1, Google Play policy).
4. Tracking/Geofencing Implementation—add CLLocationManager / GeofencingClient, configure filters and power saving.
5. Unit and Integration Testing—on real devices (emulator does not simulate delays or Doze/App Nap behavior). Test at least 50 scenarios.
6. Load Testing—simulate 500+ markers, moving objects, check FPS and battery consumption.
7. Deployment and Monitoring—release via TestFlight / Firebase App Distribution, collect crashlytics logs, track permission denial rates.

Timeline and Deliverables

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.