Mobile App for Courier Dispatch: Development & Integration

A courier service without a reliable dispatcher tool is like an airport without a control tower. We know this firsthand: we've worked with dozens of courier services, deploying solutions for real-time order flow management. A dispatcher needs to simultaneously view a map with couriers, process an order queue, and react to changes—all on a mobile device. On a tablet or phone: a map with dozens of points, a queue of unprocessed orders, and statuses of active deliveries. The UI requirements are tighter than in a customer app, and reliability demands are higher than in a courier app. Below, we break down how we solve these tasks using a modern stack including Flutter, Google Maps SDK, and WebSocket.

How to Ensure Map Responsiveness with Dozens of Couriers?

Two types of markers on one map: green dots for available couriers, red dots for active deliveries. When zooming, clustering is needed to prevent the map from turning into a mess of icons. According to Google Maps SDK documentation, clustering is mandatory for more than 100 markers. MarkerClusterManager (Google Maps Android) or GMUClusterManager (iOS) with a custom ClusterRenderer—the cluster color shows the type of objects inside.

Tap on a courier marker—a popup card appears: name, current status, orders in progress, ETA to next point. From that card, assign a new order or call immediately. Tap on an order marker—order details, status, assigned courier (if any), and a reassign button.

Filtering and Zones—Mobile App Development

A courier service may operate by city zones. The dispatcher must filter the map by zone and see only their couriers. Polygon overlay with GMSPolygon / MKPolygon and semi-transparent fill to display zones. Zone switching via a tab or dropdown at the top.

How to Automate Order Distribution?

Manual assignment: the dispatcher sees a new order, looks at the map for nearby free couriers (highlighted), and selects from a list. The list is sorted by distance from the pickup point (server-side calculation via PostGIS ST_Distance). On average, a dispatcher processes up to 50 orders per hour. Our algorithms cut distribution time by 30%.

Automatic distribution—an "auto" button triggers a server-side algorithm. The dispatcher can intervene and reassign. When an order is reassigned, the previous courier receives a push notification "order removed." Without this, a courier might arrive at the address only to find the order was already delivered by someone else.

Unprocessed Orders Queue

A real-time list of new orders via WebSocket. DiffUtil (Android) / SwiftUI AnimatedList for animated row addition/removal. Priority: urgent orders are highlighted in color; default sorting by creation time. Badge on the tab icon for unaccepted orders. If the dispatcher doesn't process the queue for more than 5 minutes, an audible alert sounds.

Why Is Courier Chat Important?

Real-time communication reduces errors and speeds up problem resolution. We recommend an in-app chat, but for small teams a deep link to Telegram or WhatsApp with the courier's number suffices. For enterprise solutions, we use Firebase Realtime Database or Supabase Realtime as the chat backend, with a simple RecyclerView / LazyColumn on the client. Voice messages—a priority on the mobile dispatcher. Recording and sending is faster than typing.

Shift Analytics

A simple dashboard: orders accepted / in progress / completed / cancelled. Average delivery interval. Couriers by status. Updates in real time via WebSocket stream. For deeper analysis, we add a metrics table:

No separate analytics screen needed—just a widget over the map or a side panel on tablets. This allows the dispatcher to quickly assess the situation.

What’s Included in Development?

• Architectural documentation—component descriptions, flow diagrams.
• Source code—under version control (Git) with CI/CD.
• Store access—publication to App Store and Google Play.
• Team training—2 sessions on the admin panel.
• Warranty—bug fixes for 6 months after release.

We have been doing mobile development for over 5 years and have completed 30+ projects for logistics and delivery. Our solutions are battle-tested—we guarantee stability and performance. If you want to improve your courier service, order a mobile dispatcher app development.

Timelines and Cost

Timeline: from 8 to 14 weeks, including integration. Cost is calculated individually—contact us for an accurate estimate. Get a consultation for your project today.

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.