Mobile App Development for Food Delivery Couriers

We develop mobile apps for food delivery couriers. This role is specific: short routes (1–5 km), up to 30 orders per shift, frequent bike or scooter trips, tight timeframes — food must stay hot. The app must work without lag, with minimal taps on key actions, and accurately show the route from restaurant to customer. Over 7 years, we have released 15+ delivery apps and know every technical detail.

Why Is Order Acceptance Timer Synchronization Critical?

A new order arrives as a push notification with a timer. The courier has 30–45 seconds to accept or decline. If no response, the order goes to the next courier. The screen shows the restaurant address, customer address, distance, estimated time, and order cost.

The timer is implemented as a circular progress bar with countdown. On iOS we use CAShapeLayer with strokeEnd animation; on Android, a custom View with Canvas.drawArc. The timer is client-side, synchronized with the server using the offer creation timestamp, not the push reception time — push can be delayed 8–10 seconds due to FCM. We’ve seen the error: the timer counted from push receipt, the courier saw 22 seconds instead of 30, tapped 'accept' at the last moment, but the server had already assigned the order to another courier. Solution: include offer_created_at in the push payload; the client calculates the difference with Date.now().

How We Configure Navigation for Different Courier Types?

The route consists of two legs: first to the restaurant (pickup), then to the customer (delivery). Each leg provides turn-by-turn navigation. For bike and pedestrian couriers, we use walking routes; for cars, driving routes. The mode is determined automatically by speed (GPS speedometer: >15 km/h — car, otherwise pedestrian/bike) or selected manually during registration.

Mapbox Navigation SDK supports cycling and walking profiles out of the box. Google Maps Navigation SDK also supports them, but at large order volumes it becomes more expensive. Mapbox SDK is 2.5 times cheaper than Google Maps SDK at 100,000 requests per month.

Multiple Orders at Once

Advanced feature (Yandex.Lavka, Delivery Club 'batch'): courier takes 2–3 orders from one restaurant, delivers to different addresses. The route is built as a sequence of points with optimal ordering via waypoints in the Directions API. On the client, a list of points with a 'completed' button for each.

What Is Included in Courier App Development?

We provide a complete set of deliverables:

• Technical documentation and architecture
• Screen design (Figma) with UX for quick actions
• Source code for iOS/Android/cross-platform
• Push notification setup (APNs/FCM) and geofences
• Payment gateway integration (Stripe, PayPal)
• Deployment to App Store and Google Play with review passage
• Customer team training (2–3 hours)
• Support for 1 month after launch

Work Process: From Analysis to Publication

Timeline: from 6 to 10 weeks to first release. Cost is calculated individually.

How to Ensure Offline Data Access?

A bike courier in a basement restaurant — no network. Critical data (customer address, phone number, door code) is cached when the order is received. For status updates, we use exponential backoff: if the 'delivered' request fails, we retry with increasing delay until server confirmation. The courier should not manually tap 'resend'.

let operationQueue = OperationQueue()
operationQueue.maxConcurrentOperationCount = 1
// Use Reachability for network monitoring

Order Pickup Confirmation at Restaurant

The courier picks up the order and confirms by scanning a QR code on the receipt (reliable) or pressing a 'picked up' button (simpler, but no verification). QR scanning via MLKit or Vision takes 0.5–1 second. To auto-show the 'picked up' button, we use a GPS geofence with a radius of 50–100 meters — the button is active only when the courier is actually at the restaurant. This prevents false taps from elsewhere.

Tips and Ratings

After delivery — a screen prompting to leave a tip (optional). We use Stripe Payment Intents for post-payment. The customer rates the courier; the rating is aggregated in the profile. At the end of the shift, the courier sees total earnings, number of deliveries, and average rating. Charts are built with SwiftCharts (iOS 16+) or MPAndroidChart — a simple bar chart by shift hour. On average, a courier receives 150 rubles in tips per order, which at 20 orders per day adds an extra 3,000 rubles.

How to Increase Courier Earnings Through the App?

1. Optimize routes — less idle mileage.
2. Add a rating system — high rating improves trust and tips.
3. Implement offline mode — courier doesn't lose orders when network is lost.

Get a consultation on your project — we'll assess timeline and cost for free. Order turnkey development with quality guarantee and deadline compliance. We guarantee first-time store review pass — our experience confirms this.

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.