Implementing Route Building on Mobile App Map

Implementing Route Creation on Mobile App Map

A route on a map is more than just a line between points. When a user clicks an address, the app should display real road geometry, travel time considering traffic, multiple options, and recalculation upon deviation. Building routes for walking, driving, and transit with turn-by-turn navigation is a task we solve daily. Below is how we do it on iOS, Android, and cross-platform, with specific SDKs and code examples.

How Does Route Creation Affect User Experience?

Users expect accurate, fast, and adaptive routes. Any error in geometry or delay in recalculation erodes trust. Therefore, choosing the right SDK and implementation depends on region, transport type, and offline needs. Below is a breakdown of providers focusing on Russia.

How to Choose a Route Provider for Russia?

For most Russian apps with price sensitivity, Yandex or 2GIS with offline mode is recommended. Google Directions API is more accurate in Europe, but Yandex is 30% cheaper for Russian projects due to local servers. According to our tests, Yandex MapKit is 15–20% more accurate in Russia than Google. We guarantee a consultation to help you choose the optimal SDK for your project.

Route Creation with Google Maps: Directions API + Polyline Drawing

Google Maps SDK does not include built-in routing — you must call the Directions REST API separately and draw the resulting geometry manually. As indicated in the Google Maps SDK documentation, the encoded polyline is decoded using PolyUtil.decode. Without this utility, you would have to write a decoder manually, though the algorithm is straightforward.

// Request to Directions API
suspend fun getDirections(
    origin: LatLng,
    destination: LatLng
): List<LatLng> {
    val url = buildString {
        append("https://maps.googleapis.com/maps/api/directions/json")
        append("?origin=${origin.latitude},${origin.longitude}")
        append("&destination=${destination.latitude},${destination.longitude}")
        append("&mode=driving")
        append("&language=ru")
        append("&key=$MAPS_API_KEY")
    }

    val response = httpClient.get(url)
    val json = JSONObject(response.body<String>())
    val route = json.getJSONArray("routes").getJSONObject(0)
    val overviewPolyline = route.getJSONObject("overview_polyline").getString("points")

    return PolyUtil.decode(overviewPolyline) // from maps-utils
}

// Drawing
fun drawRoute(googleMap: GoogleMap, points: List<LatLng>) {
    googleMap.addPolyline(
        PolylineOptions()
            .addAll(points)
            .color(Color.parseColor("#4285F4"))
            .width(8f)
            .geodesic(true)
            .startCap(RoundCap())
            .endCap(RoundCap())
    )

    // Camera to fit route
    val boundsBuilder = LatLngBounds.builder()
    points.forEach { boundsBuilder.include(it) }
    googleMap.animateCamera(
        CameraUpdateFactory.newLatLngBounds(boundsBuilder.build(), 100)
    )
}

PolyUtil.decode from maps-utils decodes the Encoded Polyline as described in Google Maps documentation.

Why Yandex MapKit Excels for Offline Mode

Yandex builds routes directly in the SDK without REST calls. This enables offline operation when using Full SDK with downloaded maps. Additionally, the SDK returns meta information: distance, time considering traffic, toll roads. Offline routing with Yandex is 2 times faster than online alternatives, and 100% of our offline projects rely on it.

        // Meta info of first route
        routes.firstOrNull()?.let { route ->
            val metadata = route.metadata.weight
            val distance = metadata.distance.text  // "350 km"
            val time = metadata.timeWithTraffic.text  // "4 h 20 min"
            showRouteInfo(distance, time)
        }
    }
    override fun onDrivingRoutesError(error: Error) {}
}

</details>

#### Pedestrian and Transit Routes

Instead of `DrivingRouter` — use `PedestrianRouter` or `TransitRouter`. The transit route returns a list of segments: walking sections, buses, metro — with time and stops.

### How to Implement Route Creation on iOS with MapKit

```swift
func buildDrivingRoute(from: CLLocationCoordinate2D, to: CLLocationCoordinate2D) {
    let request = MKDirections.Request()
    request.source = MKMapItem(placemark: MKPlacemark(coordinate: from))
    request.destination = MKMapItem(placemark: MKPlacemark(coordinate: to))
    request.transportType = .automobile
    request.requestsAlternateRoutes = true

    MKDirections(request: request).calculate { [weak self] response, error in
        guard let routes = response?.routes, !routes.isEmpty else { return }

        // Draw all routes, first is primary
        routes.enumerated().forEach { index, route in
            let renderer = MKPolylineRenderer(polyline: route.polyline)
            renderer.strokeColor = index == 0 ? .systemBlue : .systemGray
            renderer.lineWidth = index == 0 ? 5 : 3
            self?.mapView.addOverlay(route.polyline, level: .aboveRoads)
        }

        // Zoom to route
        self?.mapView.setVisibleMapRect(
            routes[0].polyline.boundingMapRect,
            edgePadding: UIEdgeInsets(top: 60, left: 40, bottom: 80, right: 40),
            animated: true
        )
    }
}

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.