Mobile App Development for Fleet Management

A mechanic records an oil change in the field—no internet, on a tablet inside the truck cab. Data syncs to the server 40 minutes later when the truck returns to base. Then the dispatcher had already assigned the same vehicle for a trip in an hour. This conflict would not have occurred if the scheduled maintenance was visible in the schedule before route assignment. It's these intersection points—between mechanic, dispatcher, and driver—that we automate in our Fleet Management projects. We offer turnkey development: assess your fleet, design the architecture, and deliver an MVP in 10–14 weeks. Average fuel savings from route control reach 30%, and time spent on waybills drops by 70%. Contact us for a consultation and preliminary estimate.

In fleets of 50+ vehicles, manual coordination leads to wasted time and money. We solve this with a custom mobile app that connects all participants in a unified information space.

How a Fleet Management App Solves Coordination Problems

Fleet Management is a rare case where a single mobile app doesn't cover all scenarios. Typically, it's three separate apps with shared business logic:

• Driver app – waybill, daily route, checkpoint confirmations, fuel receipts, incident capture. Works primarily offline, syncs during stops.
• Mechanic/technician app – maintenance log, pre-trip inspection checklists, spare parts requests, defect photos linked to the vehicle.
• Dispatcher/manager app – real-time fleet map, route assignment, driver status, fleet KPIs, alerts.

Technically, all three are built as one Flutter or React Native project with different entry points and role-based logic. Flutter 3.x delivers 60 FPS on budget devices—critical for drivers in the cab. Platform choice depends on team experience and performance requirements; Flutter updates instantly, unlike native apps where each platform must be updated separately. Custom development provides 40% more flexibility than off-the-shelf TMS solutions and processes route assignment requests twice as fast.

Why Integration with Telematics Matters

Modern commercial vehicles are equipped with OBD-II / J1939 ports. Through them you can get: engine RPM, speed, fuel consumption, DTC codes, mileage. A telematics unit (Teltonika, Wialon, Omnicomm) reads the bus and sends data to the server. The driver's mobile app can read OBD directly via Bluetooth: android.bluetooth.BluetoothSocket with ELM327 protocol or through ready SDKs. On iOS—via an ELM327 WiFi adapter and URLSession on a local IP. This works for diagnostics, but production tracking systems use a dedicated onboard unit, not the driver's smartphone. We use an offline-first approach: data is stored locally (SQLite/Hive), sync via WorkManager with network constraints. 95% of data syncs within 5 minutes after connection is restored.

Pre-Trip Inspection: Mandatory Before Departure

Before departure, the driver completes a digital checklist: brakes, tire pressure, lights, first aid kit, fire extinguisher. Each item requires confirmation or defect marking with a photo. Without a completed inspection, the trip cannot start—blocked at the app level. The checklist is configurable per vehicle type (car, truck, special equipment) via an admin panel. In the app, these are dynamic forms—JSON Schema rendered into native widgets: FormBuilder on Flutter/React Native. Defect photos are uploaded via WorkManager with NetworkConstraint—the driver doesn't wait for upload, goes on route, data syncs in background. For Russia, Federal Law 259 on electronic waybills applies; for the USA, the ELD mandate from FMCSA; for Europe, AETR. Our app takes these requirements into account.

How We Develop a Fleet Management App: Step-by-Step Process

1. Infrastructure audit: Fleet inventory, telematics, current systems, integration points. Identify bottlenecks—7 out of 10 clients discover that up to 30% of their vehicles are not connected to the tracking system.
2. Design: Role model, workflows, API contracts, interface prototypes. Align with key users (dispatchers, mechanics).
3. MVP development: Driver and dispatcher apps with tracking and waybills. Basic functionality in 10–14 weeks.
4. Mechanic module: Maintenance log, defects, repair planning, photo uploads. Added in 4–6 weeks.
5. Integrations: OBD-II, telematics, GIS Waybills, ERP/1C. Timelines depend on number of systems—2 to 4 weeks.
6. Pilot deployment: Test on 2–3 vehicles in real conditions, adjustments, staff training. Takes 2–3 weeks.
7. Documentation and support: Admin guides, API documentation, 30-day warranty.

Dispatching: Map and Routes

The dispatcher sees the entire fleet on a map in real time. Each vehicle marker carries context—whether a driver is assigned, if a trip is in progress, open defects, next maintenance due. Route assignment: the dispatcher drags a task onto a vehicle on the map or selects from a list. Routes are built using Google Maps Directions API or HERE Routing (corporate tier with unlimited requests), considering road weight restrictions (truck routing profile). Custom development provides 40% more flexibility than off-the-shelf TMS and reduces operational costs by 25% per year. A fleet of 30 vehicles cuts waybill time by 70% after implementation.

Analytics and Maintenance: Planning Fleet Service

Maintenance planning is not just "every 10,000 km." It depends on mileage, engine hours, type of operation. Stored as a maintenance_schedule with trigger rules. The mobile client shows upcoming maintenance and sends notifications—push via FCM/APNs to mechanics and fleet managers. KPI dashboard: mileage per period, fuel consumption per 100 km (actual vs. normative), utilization rate, accident count. Data from PostgreSQL, aggregated on the server, displayed in native chart components. Average fuel savings from route control reach 12%. Operational cost reduction for the fleet—up to 25% per year.

What's Included in Turnkey Development

Phases and Timelines

Cost is calculated individually after the fleet infrastructure audit. We guarantee compliance with App Store Review Guidelines and Google Play Console—all builds pass code signing and provisioning profile checks. Certified developers with 5+ years of experience in Fleet Management ensure reliable push notification integration (APNs/FCM) and deep linking (Universal Links / App Links). Get a preliminary cost estimate after your fleet audit. Contact us to discuss details. Order MVP development—pilot on 3 vehicles in just 3 months.

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.