Mobile App Development for Parking Spot Finder with Real-Time Data

Parking search is a real-time data problem. Users don't just want to know "a parking lot exists at address X" — they need to know "how many spots are free right now." Without up-to-date data, the app is useless: the driver arrives and sees "no spaces." That's why the first question in development is where the occupancy data comes from. In our practice, we've worked with various sources and guarantee timeliness through a combination of methods.

Parking Data Sources

Smart parking lots with sensors (ultrasonic, magnetic) transmit data via IoT gateways. Integration via REST API or MQTT. Data updates every 30-60 seconds. This is the best scenario — accuracy close to 100%. City APIs — many cities publish municipal parking data through open APIs. London, Berlin, Barcelona — ready feeds exist. Format is usually JSON REST or CSV. Crowdsourcing — users mark "occupied" / "freed spot." Accuracy is low (40-60%), suitable as a supplement. Data providers — ParkWhiz API, SpotHero API, Parkopedia — aggregators with US/Europe coverage. Paid but comprehensive.

Architecture: a server aggregates data from all sources, normalizes into a unified model ParkingSpot { id, lat, lng, capacity, available, price, type, schedule }, and the client receives it via REST or WebSocket.

How to implement an occupancy map?

Markers on the map show occupancy by color: green (>50% free), yellow (20-50%), red (<20%), gray (no data). Google Maps SDK GMSMarker with custom iconView or Mapbox SymbolLayer with data-driven styling — marker color from the available_percent field in GeoJSON. Mapbox with data-driven styling handles up to 10,000 points without lag, whereas Google Maps already stutters noticeably at 5,000 — Mapbox is 2x more performant on large datasets. Real-time sensor data is 10 times more accurate than crowd-sourcing but requires IoT integration.

Clustering at low zoom: the cluster shows the total number of free spots from all parking lots inside. DefaultClusterRenderer (Google Maps Utility) is overridden for custom display. On approaching a parking lot (tap on marker) — a bottom sheet shows details: access diagram, hourly prices, opening hours, entrance photo.

Address search with route building

The user enters a destination address → the app shows parking lots within 300-500 meters, sorted by distance + availability. "Route" button → route to the selected parking lot via Google Maps SDK openWithBundleId deep link or in-app navigation via Mapbox.

What about booking and payment?

Pre-booking — reserving a spot for a specific time. Not all parking lots support it; it depends on having a barrier with remote control. Booking form: entry/exit date/time, server-side cost calculation. Payment via Stripe, YooKassa, Apple Pay / Google Pay. After payment — confirmation with QR code for entry or PIN for the barrier. For parking lots without automatic barriers — pay-by-phone via the app. Push notification 15 minutes before paid time expires, with an option to extend directly from the notification (UNNotificationAction).

Additional features

Recently visited parking lots — automatically from order history. Favorites — manual addition. Synced via backend, available on all user devices. Notification "your favorite parking lot near the office is free" — geofence + monitoring available > 0 via WebSocket. The user subscribes to a specific parking lot. Indoor navigation for large shopping centers: photo of the parking layout with description "entrance from the mall, floor -2, sector C." A more advanced option is WiFi fingerprinting or BLE beacons.

Process and timeline

1. Requirements analysis and UX/UI prototype (1-2 weeks)
2. Backend development (data aggregation, WebSocket) (2-3 weeks)
3. iOS and Android apps on SwiftUI/Jetpack Compose (3-5 weeks)
4. Integration with parking APIs (1-2 weeks)
5. Payment integration (1 week)
6. Testing and release on App Store and Google Play (1-2 weeks)
7. Documentation and 3 months of warranty support

Development timeline: from 8 to 14 weeks. Cost is calculated individually based on functionality and integrations. Our experience: 5+ years in mobile development, 20+ parking projects in Europe and CIS. We guarantee data timeliness and stable operation under load. Get a consultation for your project — we will estimate timeline and budget within 2 days.

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.