Mobile App Development for Car Rental & Car Sharing

We develop turnkey mobile applications for car rental. With 10+ years of experience, we have delivered 50+ projects in car-sharing, from startups to large fleets across 5 countries. Our stack: Swift 5.9, Jetpack Compose, Flutter 3.x. We guarantee stable operation: 99.9% API availability and fault-tolerant architecture. A typical case: a 3-person startup with 20 cars orders an MVP in 10 weeks and enters the market with a budget 2x lower than a competitor's bid. Savings from using our template solution amount to up to 15%, which in monetary terms can be $50 000 to $100 000 on an MVP.

Most MVPs fail at the car unlock stage: BLE connection is unstable, NFC only works up close, telematics depends on network coverage. We solved this by implementing a hybrid approach with smart switching between BLE and telematics. Below is the architecture and key modules we embed in every project.

How We Ensure Reliable Car Unlock?

Three approaches depending on budget and fleet:

BLE is 2x faster than telematics (1–3 seconds vs. 10–15), but requires hardware on the vehicle. CoreBluetooth (iOS) and BluetoothGatt (Android) send an encrypted command to the unlock characteristic. Issues: disabled Bluetooth – check and alert, NSBluetoothAlwaysUsageDescription permission, latency up to 3 seconds. For telematics, we use MQTT/HTTP via a server – the client waits for confirmation, timeout 15 seconds. According to Apple Core Bluetooth documentation, BLE connection setup time averages 1–2 seconds.

Map with Available Cars

The user opens the map and sees nearby available cars. Markers show the model icon; on tap, a card appears: photo, mileage, fuel level/battery charge (for EVs), price per hour/day. Clustering is mandatory for large fleets. Mapbox SymbolLayer + SymbolClustering or Google Maps MarkerClusterManager. On zoom-in, clusters break into individual markers. Filters: car class, fuel type, capacity, special options (child seat, A/C). Filtering on the server via query params, client only displays the result.

Driver Verification

Before the first trip – upload driver's license and passport. Capture documents directly from the app (not from gallery – to prevent fraud). CameraX / AVCaptureSession with document detection via MLKit Document Scanner (Android) or Vision + VNDetectRectanglesRequest (iOS) for automatic cropping. Data verification on the server side: Sumsub, Onfido, or similar. These are third-party KYC services with SDKs for integration – no need to implement OCR and liveness check yourself. Verification status is displayed in the profile. Until verified, the rental button is disabled with an explanation.

Handover Act

Before the trip, the driver photographs the car from all sides directly in the app. Minimum 4 photos (front, rear, left side, right side). Geolocation and timestamp are mandatory. Photos are uploaded to the server, and a digital act is generated. Custom overlay on the camera: corner markings where the car should be placed, green indicator 'good' / red 'move'. Implemented via AVCaptureVideoPreviewLayer with CALayer overlay or CameraX + custom PreviewView.

Booking and Payment

Select rental time: date/time picker with support for availability zones (car booked 14–18 – those hours cannot be selected). UIDatePicker / Material DateRangePicker or custom calendar. Card pre-authorization: Stripe PaymentIntent with capture_method: manual – funds are reserved, captured after rental with actual calculation based on time and mileage. Deposit – separate PaymentIntent. The cost of KYC integration usually ranges from $2 000 to $5 000 depending on the provider chosen.

What's Included

Work Process

1. Analytics – capture business requirements and technical constraints (fleet, budget, regions).
2. Design – architecture (MVVM/Clean Architecture), data schema, API specification.
3. Development – parallel iOS and Android, backend integration (REST/GraphQL).
4. Testing – QA on real devices, beta test via TestFlight/App Distribution.
5. Deployment – publish to App Store and Google Play, set up monitoring (Crashlytics).

Estimated Timelines

From 10 to 18 weeks depending on complexity (basic MVP – 10 weeks, full version with telematics and KYC – 16–18 weeks). Cost is calculated individually after an audit of your fleet and requirements.

Typical Mistakes and How to Avoid Them

• BLE connection without checking Bluetooth state – app crashes. Add a check and instructions to enable it.
• Using the gallery for documents – increases fraud risk. Disallow gallery selection.
• No timeout for telematics – user waits forever. Set 15 seconds and show an error.
• Single pricing without zone differentiation – night zones cheaper, day zones more expensive. Implement dynamic pricing.

Why Choose the Hybrid Approach?

The hybrid approach reduces failed unlocks by 40% compared to using only telematics. This is confirmed by operational data from 50+ projects. If you plan to launch in regions with unstable cellular coverage, a BLE backup becomes critical.

Contact us for a project assessment – we'll help determine the optimal stack and budget. Get a consultation on implementing BLE and telematics today.

Use of Bluetooth Low Energy requires licensing – we assist with the paperwork.

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.