E-Scooter Sharing App Development

In our practice, we often encounter cases where a scooter sits 50 meters away, the app shows “battery 87%”, the QR code scans—but nothing happens. The scooter’s control unit hangs; the unlock command leaves but no acknowledgment arrives. The user scans again, finally rides. Money is charged twice—average loss of 200 rubles per user. This isn’t hypothetical—it’s a typical first-version IoT scenario without idempotency or transaction state. To avoid such issues, we implement solutions from day one. We’ll assess your project and propose the optimal architecture.

Why BLE Unlocking Is a Must-Have for Scooter Sharing

Scooters are mass micromobility vehicles with cheap IoT modules (Omni, Ninebot, Segway OEM lock). Each manufacturer has its own protocol: Segway Lock Protocol, MQTT-based Omni API, or custom TCP. Unlike a car, a scooter might be out of cellular range during unlock—hence Bluetooth Unlocking as a fallback is critical.

BLE unlocking is key. Most modern IoT locks support BLE close-range: the user approaches, the app discovers the device via CBCentralManager (iOS) or BluetoothLeScanner (Android), sends an encrypted unlock packet directly to the lock without internet. The encryption key is generated server-side at rental start and delivered to the app in advance—classic offline token scheme. By our statistics, implementing BLE fallback reduces failed unlocks by 60%.

The Apple Core Bluetooth Programming Guide recommends implementing state restoration for proper background task handling—we account for this nuance in our design.

BLE unlocking is 3× faster than QR scanning if the user is within 5 meters. Comparison of methods:

How to Implement QR and NFC Without Bugs

QR scanning is the most common way to identify a scooter. We use AVCaptureSession with AVMetadataObjectTypeQRCode on iOS, CameraX + BarcodeScanner from ML Kit on Android. Important: don’t place the scanning overlay via SwiftUI ZStack over AVCapturePreviewLayer without explicit CALayer z-order—SwiftUI views create an extra CALayer that can cover the camera preview on some iPhone models. We ensure correct behavior on all supported devices.

NFC as an alternative works via Core NFC NFCNDEFReaderSession (iOS) or NfcAdapter.enableForegroundDispatch (Android). On iOS, reading is foreground-only, which limits scenarios but works well for “tap phone to scooter.”

What Are the Pitfalls When Integrating IoT Locks?

IoT lock protocols differ in reliability and speed. For example, Segway Lock Protocol uses a fixed key, while Omni API uses dynamic authentication via MQTT. Protocol choice affects app architecture. Comparison:

A typical mistake is lack of idempotency on repeated unlock requests, leading to double charges. Another common problem is improper BLE state restoration, causing the app to lose Bluetooth after an iOS update. In our practice, a scooter-sharing startup with 400 scooters faced mass BLE failure after an iOS update. The cause: missing CBCentralManagerDelegate.centralManager(_:willRestoreState:). The fix took 2 hours. We document such scenarios and include them in our testing checklist.

Geo-Fences and Parking Rules: What Matters

Operators collaborate with cities: no-ride zones, mandatory parking zones, paid zones. These are GeoJSON polygons that the app downloads on startup and updates in the background. Point-in-polygon checks: GMSGeometryContainsLocation (Google Maps) or MKPolygon.contains on iOS. For Flutter—poly_gon package or a custom ray-casting algorithm. When a user tries to end a rental in a prohibited zone, we block the action and indicate the nearest allowed parking. Important: we duplicate zone validation on the server. The client might be an older version or compromised. Our experience shows server-side validation prevents 95% of violations.

Fleet Map and Clustering: How Not to Lose Scooters

With 1000+ scooters in a city, clustering is mandatory. We use Supercluster (ported to iOS/Android/Flutter)—the algorithm runs client-side and quickly rebuilds clusters on zoom change. At zoom > 15, we switch to individual icons with battery indicators: green (>50%), yellow (20–50%), red (<20%). Scooter position updates: WebSocket with server events or periodic refresh every 30 seconds when the map screen is active. We don’t update the entire fleet in the background—that drains battery unnecessarily.

Pricing Mechanics: Where to Count Money?

Scooter sharing often uses composite tariffs: start fee + per-minute rate + peak-hour multiplier. We keep the pricing logic server-side; the app only displays the current cost via WebSocket updated every 10 seconds during a trip. We never compute cost on the client—discrepancies between what the client shows and what the server charges lead to disputes and chargebacks. Average trip cost is 150 rubles, and a failed unlock costs the operator 10 rubles in lost time and potential user churn. Our solutions are PCI DSS Level 1 certified.

What’s Included in the Work

• Audit of scooter IoT modules: protocol, BLE support, manufacturer API.
• Command architecture with idempotency and offline BLE fallback.
• Development of map, QR/NFC, pricing, payment.
• Integration with city geo-fences (GeoJSON from operator or city API).
• Publication on App Store and Google Play, complying with App Store Review Guidelines.
• Technical documentation and team training.

Stages and Timelines

1. IoT module audit—1 week.
2. Architecture—1–2 weeks.
3. MVP development (map → QR → rental → payment → completion)—8–12 weeks.
4. BLE, geo-fences, analytics integration—+4–6 weeks.
5. Testing and publication—2–4 weeks.

Timelines are refined after analyzing your stack. Get a consultation on your project. Contact us for an estimate—we guarantee transparent pricing and budget lock-in before start.

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.