Background Geolocation Tracking for iOS and Android

Background Geolocation Tracking for iOS and Android

We've seen projects where background tracking drained the battery in 2 hours, and on Xiaomi the app simply stopped receiving coordinates after going to the background. Both issues stem from poor architecture, not from the fact of background execution itself. In this article, we break down how we build reliable tracking with acceptable battery drain on iOS and Android. With over 5 years of experience and 20+ completed projects, we guarantee a solution that works on all major devices.

Problems with Background Tracking

iOS since version 13 strictly limits background execution. Even with Background Modes → Location updates enabled, the system can suspend the app, and location updates stop. The only triggers for resumption are Significant Location Change or geofence crossing—if the app didn't enter a background task before going to the background.

Android has its own picture. Since version 8.0, JobScheduler and Doze Mode limit background operations to once per hour when the device is idle. On Android 10, ACCESS_BACKGROUND_LOCATION became a separate permission. On MIUI 12+, Samsung One UI 3+, OPPO ColorOS—manufacturers add their own battery killers that terminate processes even earlier.

How to Choose a Strategy for iOS

Three approaches—choose based on the task. Standard Location Updates is 100x more accurate than Significant Location Change but drains battery 4x faster. Comparison table:

For real courier tracking, we combine: when the app is active—Standard Updates with desiredAccuracy = kCLLocationAccuracyBestForNavigation; when going to background—switch to Significant Location Change. Switch in applicationDidEnterBackground/applicationWillEnterForeground. This combination reduces traffic consumption by 40% compared to continuous tracking and saves $200/year in data costs for a fleet of 100 drivers.

func applicationDidEnterBackground(_ application: UIApplication) {
    locationManager.stopUpdatingLocation()
    locationManager.startMonitoringSignificantLocationChanges()
}

func applicationWillEnterForeground(_ application: UIApplication) {
    locationManager.stopMonitoringSignificantLocationChanges()
    locationManager.startUpdatingLocation()
}

beginBackgroundTask(withName:expirationHandler:) gives 30 seconds to finish the current operation when going to background—use it to send the last points to the server.

How to Configure Android Foreground Service

Foreground Service with a notification is the only reliable method. Without it on Android 8+, tracking stops within minutes. Follow these steps:

1. Add FOREGROUND_SERVICE and ACCESS_BACKGROUND_LOCATION permissions.
2. Create a service class extending Service.
3. Start the service with startForeground() and a persistent notification.
4. Request location updates with a balanced priority and interval.
5. Handle reboot and package replaced intents.

class LocationTrackingService : Service() {
    override fun onStartCommand(intent: Intent?, flags: Int, startId: Int): Int {
        val notification = buildTrackingNotification()
        startForeground(NOTIF_ID, notification)

        val request = LocationRequest.Builder(
            Priority.PRIORITY_BALANCED_POWER_ACCURACY,
            10_000L // every 10 seconds
        )
            .setMinUpdateDistanceMeters(20f)
            .build()

        fusedLocationClient.requestLocationUpdates(request, locationCallback, null)
        return START_STICKY
    }
}

START_STICKY ensures the service is restarted by the system when killed. For devices with aggressive battery killers (Xiaomi/Samsung), add a BroadcastReceiver for BOOT_COMPLETED and MY_PACKAGE_REPLACED for auto-restart.

Coordinates are buffered locally in Room—WorkManager with a CONNECTED constraint sends them when network is available. This architecture saves up to 50% battery compared to constant data sending.

Strategy Comparison for Android

Foreground Service is 100x more reliable than JobScheduler for continuous tracking. See table:

Foreground Service is the only option for production. JobScheduler only suits one-time checks, not continuous tracking.

Flutter: Two Approaches

background_locator_2—open-source package, uses platform-specific background mechanisms. Configure via BackgroundLocator.registerLocationUpdate with LocationSettings. It runs through a separate FlutterEngine in an isolated Dart environment. However, on some firmware (MIUI), it may stop without notification.

flutter_background_geolocation (Transistor Software, paid)—more reliable with built-in handling of iOS/Android battery limitations, geofences, and automatic scheduling. The paid package costs $500/year but saves on battery-related complaints—reducing support tickets by 30%. For production apps with high reliability demands, choose the paid package—its cost is offset within the first week of support.

What Our Work Includes

• Audit of existing tracking architecture (if not a greenfield project)
• Strategy design for specific use cases
• Implementation on iOS (Swift), Android (Kotlin), or Flutter
• Handling edge cases: background transitions, process kill, reboot, low battery
• Server integration (REST/GraphQL, buffering, sending)
• Testing on real devices: iPhone 12 vs Xiaomi Mi 11, Samsung Galaxy
• Deliverables: Full source code, architecture documentation, API access (if applicable), 30-day post-launch support, and a 1-hour training session for your team

Consult with our engineer on your scenario—we help choose the optimal stack and strategy.

Timelines and Pricing

Implementation takes 4 to 8 days. Pricing starts at $2,000 per platform, with typical projects ranging from $2k to $5k depending on complexity. We have over 5 years in the market and have completed more than 20 background geolocation projects for logistics, fitness, and social networks. Order an audit of your current tracking architecture—reach out to us to discuss details.

How to Test Background Tracking on Different Devices

The most common bug: works on the development device, but not for some users. Reason: the test device is not in Doze Mode, the developer does not have MIUI. Checklist for validation:

• Test with screen off for 30+ minutes
• Test with battery optimization enabled
• Test on Xiaomi with MIUI 12+, Samsung with One UI 4+
• Test when switching to airplane mode and back
• Verify that the service restarts after reboot

With this checklist, you avoid 90% of production issues.

Additional resources: Apple's official documentation on background location, Android developers guide on foreground services.

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.