Mobile App Development for Goods Delivery

Mobile App Development for Goods Delivery

Delivery of goods differs fundamentally from food delivery: large-sized freight, interval time slots, signature upon receipt, integration with external ERP/WMS. We create apps for delivery services and online stores that solve these problems — with accurate rate calculation, optimized routes, and reliable parcel tracking. Our experience: 5 years in the market and over 20 delivery projects. We know how to combine the client app, courier app, and admin panel into a single system.

How does a mobile delivery app solve the complex tariff problem?

Calculating delivery cost is the first pain point for any logistics business. The tariff depends on weight, dimensions, fragility, and even temperature regime. Storing the tariff matrix on the server is the only correct solution: a POST /delivery/calculate request returns available options with price and time. Hardcoding in the app inevitably leads to errors when conditions change. Server-side rate calculation allows flexible tariff adjustments without releasing a new app version. For example, when fuel costs change or a new tariff appears, it's enough to update the config on the server. To optimize routes, we use OR-Tools — a library from Google that can reduce mileage by 15-20%. A delivery goods API standardizes data exchange between the app and the warehouse.

Managing time slots is another challenge. Clients choose a 2-4 hour window, not an exact time. Slots are generated N days ahead, each with an order limit. When a slot is full, it becomes unavailable. Capacity is calculated based on the number of active couriers and average load per route. This avoids overloading couriers and reduces complaints. In one project with a hypermarket chain, we implemented dynamic route rebuilding when a new order is added — delivery time decreased by 25% compared to a fixed route.

Why is ERP integration important?

Without integration with ERP (1С, MyWarehouse, SAP), the app risks selling out-of-stock items. We implement synchronization via REST API or asynchronous queues (RabbitMQ/Kafka). The product catalog is cached locally (Room/Core Data) with TTL and invalidation on an "assortment update" event. A double check — when adding to cart (server confirms availability) and at final checkout — almost completely eliminates scenarios where an item is ordered but not available. For a home goods store chain, we implemented integration with 1С via REST API. When a price or stock changes in 1С, it sends an event, the app updates its cache and immediately blocks the order if the item is unavailable. This reduced returns by 30%. For product returns, the client initiates a request through the app, the server creates a return invoice and starts a refund.

Server-side rate calculation is three times more accurate than hardcoding — the error margin drops from 15% to 5% thanks to centralized rule updates. Additionally, we automatically generate reports on courier efficiency in Power BI or Tableau.

How to set up server-side rate calculation? Step-by-step process

1. Define parameters: weight, dimensions, fragility, temperature regime, tariff zone.
2. Backend development: create a calculate endpoint with injected pricing rules.
3. Load tariff matrix: as a JSON config that can be changed without redeployment.
4. Integration with a mapping API: to calculate distance and time based on accurate routes.
5. No request failures: on error, a fallback tariff (maximum or last successful) is used.
6. Testing: 100+ scenarios, including edge cases for weight and fragility.

What we use?

Push notifications are implemented via APNs in strict compliance with App Store Review Guidelines Section 4.2. On Android, via FCM with high priority.

What's included in the work?

Timeline and cost

MVP (one platform + courier app) takes 8–14 weeks. Full platform (iOS + Android, 1С integration, slots, returns, dispatcher panel) — 4–8 months. Cost is calculated individually after requirements analysis. We guarantee transparent stages and fixed deadlines. Get a consultation for your project — we'll estimate the timeline and cost. Contact us to discuss details.

Try our approach — order a preliminary project estimate. Find out how we can help your business automate delivery and reduce costs.

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.