Developing a Mobile Dispatch App for Taxi Services

We develop taxi dispatch mobile apps — not just a map with markers. It's real-time dashboards displaying dozens of drivers, order queues, and trip statuses simultaneously. The taxi driver map is updated in real-time via WebSocket. The map rendering performance requirements are higher than in driver or passenger apps, and the business logic is significantly more complex. In one project with 80 drivers, the map froze for 5 seconds on each update — we rewrote the rendering to Mapbox with a canvas layer, and the freezes disappeared. Over our work, we have implemented more than 15 projects for taxi fleets and delivery services. Taxi app development also includes robust taxi order management and real-time analytics. Our clients save up to 30% time on order processing, which translates to average monthly savings of $5,000 for a fleet of 50 drivers. Typical project costs start from $30,000.

A typical dispatch console runs on an Android tablet or iPad, where the dispatcher sees a map with clustered markers, accepts orders, and assigns drivers. The fleet app includes a dispatch module. For taxi offline mode, we cache last known state and queue updates. Dispatch notifications are sent as push alerts.

Architecture of the Taxi Dispatch App

We use MVVM with ViewModel, Repository, and UseCase layers, reactive state (StateFlow / RxSwift), WebSocket via OkHttp (Android) or URLSessionWebSocketTask (iOS), maps — Google Maps SDK or Mapbox. For cross-platform — Flutter with native plugins.

Ensuring Smooth Map Performance with 100+ Markers

Displaying 50–100 driver markers simultaneously is the first thing that breaks naive implementations. Google Maps SDK and MapKit have performance limitations when constantly updating a large number of markers. On Android, updating 80 markers every 3 seconds via marker.position = newLatLng causes noticeable freezes on budget devices. Taxi map optimization ensures smooth scrolling and clustering of markers. We reduce rendering load by up to 40% using canvas layers.

Solutions:

• Clustering — group nearby markers at low zoom levels. We use Google Maps Utility Library (MarkerClusterManager on Android, GMUClusterManager on iOS) or Supercluster (JavaScript port via React Native Maps). Clustering can be up to 5 times faster than displaying individual markers. Zooming into a specific area breaks clusters into individual cars.
• Renderer optimization — on Android use GoogleMap.setOnCameraIdleListener to update only the visible region. Update markers only for drivers in the current VisibleRegion, batch the rest and update on scroll.
• Canvas rendering — for aggressive scaling: Mapbox Maps SDK with native layer via SymbolLayer — symbol positions are updated through GeoJSON source without creating/removing markers. This is fundamentally faster for 100+ objects.

For iOS we use GMUClusterManager with custom GMUDefaultClusterIconGenerator. Every 2 seconds we get the driver list via WebSocket, update GeoJSON, and call clusterManager.cluster(). Result: 100 markers displayed without freezes on iPad 6th generation.

Order Distribution Without Conflicts

The dispatcher can work in two modes: manual assignment and automatic control. In manual mode, they see the order on the map, press "assign", and select a driver from the list of nearest (sorted by distance from pickup via Distance Matrix API or server-side calculation via PostGIS).

Conflict on simultaneous assignment: two dispatchers assign the same order to different drivers. Solution — optimistic locking on the server (version field in the order) + error message on UI suggesting to reload the list. This approach reduces conflicts by 90%.

Integration Capabilities with Existing Dispatch Systems

We connect to any backend system via REST API and WebSocket. In high-load projects we use GraphQL (Apollo) for flexible data fetching. Dispatch system integration is a key part of our taxi app development. Message queues (RabbitMQ or Kafka) guarantee event delivery even during temporary network failures. Documentation is available in Swagger.

App Functionality with Poor Internet

A dispatcher in a taxi fleet may have weak Wi-Fi. WebSocket reconnect with exponential backoff is mandatory. On connection loss — show a "no connection" banner, request a snapshot of the state (all orders, all drivers) upon recovery, rather than relying on all events during the break coming through the queue.

Notifications and Sound Alerts

New order — sound alert + vibration, even if the app is in the background. On iOS: notification content extension for custom notification UI. On Android: NotificationChannel.IMPORTANCE_HIGH + custom sound via Uri resource. The dispatcher's tablet should sound like a two-way radio — no system "dings".

Real-Time Analytics

A small statistics module within the app: number of active drivers, orders in progress, average wait time. Data from WebSocket events aggregated locally. No need for a separate backend endpoint for each metric — just count from the event stream in memory. Taxi real-time analytics and map optimization are built-in.

How We Work

1. Analysis — gather requirements for screens, order types, and integration with existing systems.
2. Design — draft architecture, choose stack, agree on flows.
3. Implementation — write code with CI/CD, code reviews, unit tests.
4. Testing — load testing with 200+ markers, regression on real devices.
5. Deploy — publish to App Store / Google Play, configure TestFlight and Firebase Distribution.

What's Included

• Source code in a private Git repository with commit history.
• API documentation in OpenAPI (Swagger) format.
• Instructions for deploying backend and configuring cloud services.
• Training for the dispatcher team on using the app (up to 2 hours).
• 12-month warranty support from the date of the acceptance certificate.
• Quality certificate and licensed code purity.

Timelines and Cost

Implementation time: from 10 to 18 weeks depending on integration complexity (number of clients, order types, offline mode). Cost is calculated individually — contact us with a description of your taxi fleet and current processes, and we will prepare an estimate within 2 business days. For accurate calculation, we use an hourly rate and fix the scope in the technical specification. Typical project costs start from $30,000. On average, dispatch time decreased by 40% compared to manual processes. The app handles up to 500 markers with clustering, maintaining 30 fps on budget devices. 95% of orders are assigned within 10 seconds.

For a detailed proposal, please provide your fleet size, number of dispatchers, current software, and specific requirements. We will prepare a tailored solution within 2 business days. We guarantee the app will pass App Store moderation on the first attempt (sections 4.2 and 5.1 of the Review Guidelines).

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.