Real-Time Courier Tracking for Mobile Apps

A courier tracking project often starts with a simple task: showing the client where the delivery is. But production requires solving dead-reckoning upon GPS loss, map snapping to the road graph, and synchronization between three components: the courier app, the server bus, and the client app. On a project with 500 couriers, we reduced update latency to 2 seconds by switching from WebSocket to MQTT and configuring Redis with a TTL of 60 seconds. This approach saves development hours and lowers operational costs by up to 30% due to reduced traffic. Mistakes in protocol selection or battery mode configuration lead to code rewrites — so it's crucial to lay the right architecture from the start. Order an audit of your current solution — we'll choose the optimal configuration.

Why Courier Tracking Is Not Just GPS?

A production system includes four key components:

• Dead-reckoning upon GPS signal loss — interpolation of last known coordinates using speed and heading.
• Map snapping to roads — raw GPS points jump relative to the road; they need to be snapped to the road graph.
• Courier state logic: idle → assigned → picking_up → delivering → completed.
• Battery trade-off on the courier app side: 5 seconds versus 15 seconds.

Courier App: Collecting and Transmitting Coordinates

On Android we use FusedLocationProviderClient from play-services-location in a Foreground Service. The update interval is a compromise: 5 seconds gives accuracy, 15 seconds saves battery. For pedestrian couriers — Priority.PRIORITY_HIGH_ACCURACY + 5 seconds. For automotive — Priority.PRIORITY_BALANCED_POWER_ACCURACY + 10 seconds with setMinUpdateDistanceMeters(20f).

On iOS — CLLocationManager with desiredAccuracy: kCLLocationAccuracyBestForNavigation in active mode and switching to Significant Location Changes in background. activityType = .automotiveNavigation activates GPS noise filtering.

Anomalous point filtering is mandatory. GPS in city streets produces jumps of 50–200 meters. A simple filter: discard a point if horizontalAccuracy > 50 meters or calculated speed > 200 km/h.

func shouldAcceptLocation(_ location: CLLocation) -> Bool {
    guard location.horizontalAccuracy > 0,
          location.horizontalAccuracy <= 50 else { return false }
    if let lastLocation = lastAcceptedLocation {
        let timeDelta = location.timestamp.timeIntervalSince(lastLocation.timestamp)
        let distance = location.distance(from: lastLocation)
        let impliedSpeed = distance / timeDelta
        if impliedSpeed > 55.6 { return false }
    }
    return true
}

Buffering in a local database plus batch sending upon network restore is a standard scheme.

Server Bus: WebSocket or MQTT?

For small loads we choose Socket.IO. For scale — MQTT. MQTT defines a binary protocol, achieving up to 70% traffic savings on mobile networks.

Storage of current position — Redis: SET courier:{id}:position with TTL 60 seconds. Route history — TimescaleDB.

Map snapping. Raw GPS coordinates are aligned to roads via Google Roads API or OSRM self-hosted (free, <10 ms).

How to Ensure Smooth Marker Animation?

Updates every 5–10 seconds. Without animation, the marker jumps. We interpolate movement between two points.

On Android via ValueAnimator:

val animator = ValueAnimator.ofFloat(0f, 1f).apply {
    duration = 3000
    interpolator = LinearInterpolator()
    addUpdateListener { animation ->
        val fraction = animation.animatedFraction
        val lat = prevLat + (newLat - prevLat) * fraction
        val lon = prevLon + (newLon - prevLon) * fraction
        marker.position = LatLng(lat, lon)
    }
}
animator.start()

On iOS — CADisplayLink or UIView.animate with custom timing. Marker rotation angle is calculated via atan2.

In Flutter — TweenAnimationBuilder with Tween<LatLng>. For google_maps_flutter we update Marker(position: interpolatedPosition) in a Ticker every 16 ms.

Courier States

Transitions are managed by the server. Order development for your scenario — we'll account for all nuances.

What's Included

• Protocol design (WebSocket/MQTT) and data schema.
• Courier app development with background tracking.
• Server bus implementation with Redis and TimescaleDB.
• Client UI development with smooth animation and states.
• Load testing: 100/500/1000 couriers.
• Documentation and a training session.

Process and Timeline

1. Analysis: audit of current infrastructure, protocol selection.
2. Design: bus architecture, state schemas.
3. Development: app and server implementation.
4. Testing: unit, integration, load.
5. Deployment: release to App Store and Google Play.

Timeline: from 2 to 4 weeks depending on the number of platforms and server API readiness.

Why Work With Us?

We have implemented tracking for 15+ logistics projects. Our engineers are certified in iOS and Android. We guarantee track accuracy up to 5 meters and stability with 10,000 concurrent sessions. Get a consultation for your case — contact us.

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.