Order Status Tracking for Mobile Apps

Architecture of Order Tracking: Two Data Channels

The client opens the app 40 minutes after placing the order and sees the status "Processing"—the same as right after payment. They call support. The problem isn't logistics: the courier is already on the way, coordinates update on the server every 30 seconds. The issue is that the mobile app is not connected to that stream. We've encountered this in 80% of projects at the start. Our team has over 5 years of experience in building delivery mobile apps, and we have implemented more than 15 order tracking systems for e-commerce stores.

The status timeline and the courier map are two different mechanisms with different update requirements, and mixing them within one polling request is the first architectural mistake. We have already tested several approaches and identified optimal solutions for each channel.

Why Statuses and Coordinates Require Different Channels

Order status changes infrequently—5-7 times during the entire lifecycle. For this, long-polling or SSE (Server-Sent Events) works: connection stays open, server pushes an event only when the status changes. WebSocket is overkill here, though often chosen out of habit. Courier coordinates update every 15-30 seconds—this is a different load profile.

The average latency for status updates via SSE is less than 1 second, and for coordinates via WebSocket up to 200 ms.

How to Properly Implement the Timeline on the Client

On iOS, implementing SSE with URLSession looks like this:

let request = URLRequest(url: URL(string: "https://api.example.com/orders/\(orderId)/status-stream")!)
let task = URLSession.shared.dataTask(with: request) { data, response, error in
    // parse text/event-stream line by line
}
task.resume()

Better to use a ready-made library—IVALiveEventSource or the Swift Package swift-eventsource from LaunchDarkly. They handle reconnect and heartbeat properly.

On Android—OkHttp with EventSource from the library com.launchdarkly:okhttp-eventsource. Writing native HttpURLConnection for SSE manually is a waste of time handling edge cases.

Comparison of SSE libraries:

Timeline Structure on the Screen

For displaying the progress of statuses, use RecyclerView (Android) or UICollectionView with a custom layout (iOS). A typical mistake is storing "past" statuses only on the client. If the user uninstalls and reinstalls the app, the history is lost. All completed statuses with timestamps must be returned from the server as an array:

{
  "currentStatus": "courier_assigned",
  "timeline": [
    { "status": "created", "timestamp": "2025-01-01T10:00:00Z" },
    { "status": "confirmed", "timestamp": "2025-01-01T10:02:30Z" },
    { "status": "courier_assigned", "timestamp": "2025-01-01T10:15:00Z" }
  ]
}

How to Handle Courier Coordinates Separately

Courier coordinates update every 15-30 seconds—this is not SSE territory but WebSocket or a separate short-interval polling. Mixing it with the status timeline in one endpoint either overloads the status stream or updates the map too rarely.

In practice, we do this:

• Statuses - SSE or push notifications (Firebase Cloud Messaging)
• Courier coordinates - WebSocket with 15-30 second intervals or polling /orders/{id}/courier-location

Smoothing the Courier Marker

The courier marker on the map jumps if you simply set new coordinates directly. The right way is to animate the movement between points. On Android via ValueAnimator:

val animator = ValueAnimator.ofFloat(0f, 1f).apply {
    duration = 1000
    addUpdateListener { animation ->
        val fraction = animation.animatedValue as Float
        val lat = startLat + (endLat - startLat) * fraction
        val lng = startLng + (endLng - startLng) * fraction
        courierMarker.position = LatLng(lat, lng)
    }
}
animator.start()

On iOS via CADisplayLink or UIView.animate with intermediate coordinates.

To rotate the courier icon in the direction of movement, use atan2(deltaLat, deltaLng)—remember to convert radians to degrees for marker.rotation.

What to Do When Connection Drops?

The user minimizes the app—WebSocket and SSE disconnect. Key status changes (courier picked up, courier nearby, delivered) are duplicated via FCM/APNs. On iOS use UNUserNotificationCenter, on Android FirebaseMessagingService.

A nuance: a "courier nearby" notification loses meaning if it arrives 10 minutes after delivery. The server must check event timeliness before sending a push—this is server-side logic, not mobile.

What's Included in the Work

• Status timeline with SSE or FCM pushes
• Courier map with animated marker (Google Maps SDK or MapKit)
• WebSocket or polling for coordinates with correct lifecycle (onPause/onResume / viewDidDisappear)
• Offline state handling: event queue and sync on network restore
• Code signing for push notifications (APNs and FCM)

Timelines

3–5 days for the full flow: timeline + map + pushes. Timeline only without map—1–2 days. The cost is calculated individually after requirements analysis.

Get a consultation on your project. We'll help you choose the optimal architecture for your delivery app. Request an estimate—it's free.

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.