How We Build Courier Apps That Don't Kill Background Geolocation

The courier accepted the order, set off—and the app went into background-killed state on an Android Xiaomi with MIUI. FusedLocationProvider stopped providing coordinates, the track was lost, the dispatcher can't see the vehicle. This is not a hypothetical scenario—it's a standard problem for courier apps on aggressive launchers like MIUI, OneUI, EMUI, where foreground services are killed by the battery optimization garbage collector.

Our experience of over 5 years and over 20 delivered projects for courier services allows us to guarantee stable operation even on problematic devices. We develop applications turnkey—from architecture to publishing on App Store and Google Play.

The Problem: Background Geolocation on Android

On Android, continuous geolocation requires a Foreground Service with a visible notification in the status bar. Without it, on Xiaomi/Huawei/OPPO the app will die within 5–10 minutes in the background regardless of WakeLock. But even foreground service is not a panacea: MIUI adds battery restrictions even on running services if the user hasn't manually allowed autostart.

Our Approach: Ensuring Continuous Tracking

The correct approach: on first launch, we show an Intent to the system autostart screen (for MIUI—com.miui.securitycenter, for Huawei—com.huawei.systemmanager). It's not always pretty, but it's the only way to guarantee tracking. Plus—batch coordinate sending: we accumulate points in memory and send them every 10–15 seconds in one request instead of 15 separate ones.

On iOS, problems are fewer: CLLocationManager with allowsBackgroundLocationUpdates = true and pausesLocationUpdatesAutomatically = false works reliably. However, significant-change location updates are not suitable for couriers—they trigger only on cell tower changes (~500 m accuracy), which is not good for real-time map display.

Why Build Two Separate Apps?

A courier service almost always consists of two separate apps: one for the courier and one for the client. Sometimes a third—a dispatcher web interface—is added. But the mobile part can be in one project with different flavors/schemes:

• Android Flavors: courierApp / clientApp—different applicationId, icons, permissions
• iOS Targets: two targets in one Xcode project, shared code via SPM package

This allows reusing business logic (network layer, data models, geolocation module) between the two apps without code duplication. Comparison of approaches:

Order Assignment and Routing Logic

Order distribution logic lives on the server. The mobile client only receives the assignment via push (FCM/APNs with priority: high) and confirms acceptance. Importantly: FCM high priority on Android guarantees delivery even in Doze mode, but only if the app has RECEIVE_BOOT_COMPLETED and correctly configured FirebaseMessagingService.

The route to the recipient is built using Google Maps Directions API or OSRM (if a self-hosted solution without API call costs is needed). We do not implement turn-by-turn navigation in the app—we open Google Maps / Yandex Navigator via deep link, passing the delivery point coordinates.

ETA and Tracking for the Client

The client sees the courier on the map—this uses WebSocket or Server-Sent Events from the server to the client app. Coordinates are updated every 5–10 seconds. On the map, we use a Marker with animateCamera animation to ensure the point moves smoothly, not jumping—ValueAnimator (Android) or CABasicAnimation (iOS).

ETA is calculated on the server side via Google Maps Distance Matrix API or HERE Routing API and transmitted to the client. We do not compute ETA on the device—it doesn't have up-to-date traffic data.

How Is Delivery Confirmed?

Three most common confirmation methods:

• Photo of the package/door—CameraX (Android) or AVFoundation (iOS) + upload to S3/GCS
• PIN code known by the recipient—simple TOTP or static code from the order
• On-screen signature—Canvas/UIBezierPath, saved as SVG or PNG

The signature code uses strokeWidth dependent on finger movement speed—it looks significantly more natural than a constant-thickness line.

What's Included in the Work?

• Architecture documentation and technology stack selection
• Android (Kotlin + Jetpack Compose) and iOS (Swift + SwiftUI) development
• Integration with your OMS/WMS via REST or GraphQL
• Push notification setup (FCM / APNs)
• Publishing to App Store and Google Play
• Staff training (2 days)
• 2 weeks of technical support after launch

Stages and Timeline

Minimum viable product—two apps (courier + client) with geolocation, order assignment, and delivery confirmation: 6–10 weeks with a team of two developers and a designer. Full platform with dispatcher module, analytics, and integration with external OMS/WMS systems: 4–6 months. Pricing is calculated individually after requirements analysis.

We guarantee stable operation on Xiaomi, Huawei, and Samsung devices. Order a turnkey development—contact us for a free project evaluation.

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.