The dispatcher looks at the map — 40 trucks, and three haven't updated their position for 20 minutes. Is the transmission stuck? No network in the mountains? Or was the GPS antenna intentionally turned off? These are three different scenarios requiring different reactions, and the app must distinguish them — not just turn the dot gray. Our team has 5+ years of experience building such systems. We offer turnkey app development, including integration with popular telematics platforms and a backend for data processing. This is not just a map with markers — it's a real-time system where each point contains metadata: speed, direction, engine status, tracker battery level. If stationary for more than 5 minutes, the system automatically checks for network connectivity (tracker heartbeat) and ignition status. Only then can you distinguish a breakdown from a planned stop.
What the dispatcher actually needs
A monitoring app is not just "markers on a map." The dispatcher manages a fleet of 20–200 units and needs:
- Real-time data with metadata: coordinates + speed + direction + engine status + tracker battery level
- Route history: daily/weekly trail with geocoded stop addresses
- Geofencing: notification on entry/exit from warehouse, construction site, restricted area
- Alerts: speeding, prolonged idling with engine on, route deviation
All of this requires different client architectures. We have already implemented projects with fleets from 50 to 500 units, so we know how to scale the solution for any task.
How we receive telematics data in real time
Telematics units (Teltonika FMB, Wialon TK, Navixy OEM) send data via TCP or GPRS to a server. The mobile app does not connect to trackers directly — it receives the processed stream via WebSocket or MQTT client.
Data reception process:
- Tracker sends raw data to the server via the manufacturer's protocol (TCP, GPRS).
- The server parses the data, enriches it with meta information, and publishes to an MQTT topic.
- The mobile app subscribes to the topic via WebSocket and receives updates in real time.
On Android, we use OkHttp WebSocket with EventBus or SharedFlow to deliver updates to the ViewModel. On iOS, URLSessionWebSocketTask (iOS 13+) or Starscream for older targets. Updates arrive as JSON or protobuf — protobuf is preferable for large fleets: a packet of 40 vehicles × 10 fields in protobuf takes ~1.5 KB versus ~8 KB in JSON, saving 5x traffic. This reduces mobile internet costs for dispatchers. According to protobuf documentation, the binary format can reduce data size by 3-10 times compared to JSON.
How to ensure map performance with a large fleet
200 markers on a map with movement animation is already stressful. Key solutions:
Annotations instead of SVG overlays
On iOS, MKAnnotationView handles up to ~300 markers without noticeable lag. Beyond that, we use MKOverlay with a custom renderer that draws all points in a single CALayer. On Android, Google Maps SDK with MarkerOptions degrades after ~500 markers — we switch to Mapbox Maps SDK v10 with SymbolLayer based on a GeoJSON source: the entire fleet is updated with a single source.setGeoJson(featureCollection) call.
Server-side clustering
At zoom < 11, clusters are computed on the server (PostGIS ST_ClusterKMeans), and the client receives ready centroids with a counter. Local clustering (Supercluster) works for fleets up to 300–400 units.
Motion animation
Tracker positions update every 10–30 seconds — markers should not "jump." ValueAnimator with LatLngInterpolator (Android) or CABasicAnimation with CGPoint interpolation (iOS) — the marker smoothly "slides" to the new point.
Comparison of clustering methods:
| Method |
Max markers |
Latency |
| Supercluster (client) |
~400 |
<100ms |
| PostGIS ST_ClusterKMeans (server) |
Unlimited |
<50ms (with index) |
Comparison of data formats:
| Format |
Packet size (40 vehicles) |
Traffic savings |
| JSON |
~8 KB |
— |
| Protobuf |
~1.5 KB |
5x |
How route history and geocoding are built
A day's track is 2000–8000 points depending on the recording interval. We display it via Polyline / MKPolyline, but not the entire track at once: we load the visible map bbox and request points only for it. At "entire day" zoom, we discretize the track using the Douglas-Peucker algorithm on the server.
Stop addresses — reverse geocoding via Google Maps Geocoding API or OpenStreetMap Nominatim (self-hosted). We cache results in SQLite to avoid repeated requests when scrolling history.
What to do with alerts and notifications?
Speeding, geofence events, prolonged idling — triggers are calculated on the server, push notifications arrive via FCM/APNs. On iOS, we use UNNotificationCategory with UNNotificationAction — directly from the notification, you can open the map with the specific vehicle.
Geofences — GeoJSON polygons, checked with ST_Contains in PostgreSQL + PostGIS on every incoming tracker message. The mobile client only displays geofences and receives alerts — it does not compute intersections locally.
Common mistakes in notification implementation
- No background state handling: the app does not receive push if the user kills the process. Use
background fetch to reconnect to WebSocket.
- Incorrect geofence setup: if a polygon is too complex (100+ vertices), PostGIS
ST_Contains slows down. Optimize polygons with Ramer-Douglas-Peucker simplification on the server.
- Forgot about APNs/FCM tokens: when a new device is installed, the old token becomes invalid — always update it on the server.
What's included in development?
- Analysis of telematics device protocols and existing platform APIs
- Dispatcher interface design: map, vehicle list, history, notifications
- Development of all modules: data reception, map display, geofences, alerts, route history
- Load testing with simulation of 200+ trackers
- Publication on App Store and Google Play, push notification setup
- Documentation and dispatcher training
- Post-launch technical support
How long does development take?
MVP (map + real-time + history): 6–10 weeks. Full platform with geofences, alerts, mileage analytics, and reports: 3–5 months. Pricing is calculated individually after an audit of your infrastructure.
We guarantee stable operation under load of up to 500 vehicle units. Contact us for a project assessment — get a consultation on architecture and timelines. Request a cost 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
| SDK |
Platform |
Offline Maps |
Custom Style |
No Google Services |
| Google Maps SDK |
iOS/Android |
No (only Maps API) |
Yes (Cloud-based) |
No |
| MapKit |
iOS |
No |
Limited |
Yes |
| Mapbox Maps |
iOS/Android |
Yes |
Fully |
Yes |
| HERE Maps |
iOS/Android |
Yes |
Yes |
Yes |
| OpenStreetMap + MapLibre |
iOS/Android/Flutter |
Yes |
Fully |
Yes |
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
-
Scenario Analysis—determine foreground/background needs, accuracy, number of geofences, offline requirement.
-
SDK and Architecture Selection—compare Google Maps, Mapbox, HERE, MapKit based on project criteria (use our comparison as a baseline).
-
Integration and Permission Setup—configure
Info.plist / AndroidManifest.xml, test review checks (App Store Review Guidelines Sections 4.2/5.1, Google Play policy).
-
Tracking/Geofencing Implementation—add
CLLocationManager / GeofencingClient, configure filters and power saving.
-
Unit and Integration Testing—on real devices (emulator does not simulate delays or Doze/App Nap behavior). Test at least 50 scenarios.
-
Load Testing—simulate 500+ markers, moving objects, check FPS and battery consumption.
-
Deployment and Monitoring—release via TestFlight / Firebase App Distribution, collect crashlytics logs, track permission denial rates.
Timeline and Deliverables
| Stage |
Timeline |
Deliverables |
| Basic map integration with markers and search |
1–2 weeks |
Source code (Swift/Kotlin/Dart), API documentation, build instructions |
| Geofencing with push notifications |
2–3 weeks |
Geofence code, FCM/APNs setup, test zones, delay report |
| Full route tracking (background, smoothing, server sync) |
4–6 weeks |
Code with Kalman filter, server part (optional), battery monitoring |
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.
