Development of a Parking Mobile App

Introduction

Developing a parking mobile app faces a core problem: real parking occupancy is a stream of events, not a static table. A user sees "free" spots on the map near a mall, drives there, and finds the lot full — data was 15 minutes stale. We solve this by directly integrating with hardware and payment systems, providing a trustworthy real-time picture.

Integration with Parking Equipment

Real occupancy data comes from barriers, loop detectors, or ultrasonic sensors via MQTT or WebSocket to a broker (mosquitto, EMQX). The mobile app subscribes to parking topics and receives live updates. This requires a persistent connection, implemented on mobile via Starscream (iOS WebSocket) or OkHttp WebSocket (Android). The connection drops when the app goes to background — for iOS we use BGProcessingTask, for Android WorkManager with periodic checks.

If the budget doesn't allow hardware integration, we use payment system data: entry is recorded upon payment, exit upon payment/barrier lift. Accuracy is lower, but data is real.

Seamless Payment

The most critical UX moment is paying for parking without queuing at a terminal. Three common scenarios:

• Prepayment by license plate. User enters plate, selects time, pays. At exit, an ANPR camera matches the plate and opens the barrier. Integration with Russian ANPR systems (Vocord, ITRIUM) or international ones (Genetec, Milestone).
• Scan & Pay. QR code at entry, user scans, app records entry time, payment at exit. Implemented via AVCaptureSession (iOS) or CameraX with BarcodeScanner from ML Kit (Android) — no separate QR SDK needed.
• NFC tags. Tap an NFC tag at entry/exit. Core NFC (iOS 11+) or NfcAdapter (Android). iOS limitation: NFC works only in foreground, cannot scan in background without special entitlement.

For payments we integrate Stripe, YooKassa, or CloudPayments depending on geography — all three provide native iOS/Android SDKs.

Payment Method Comparison — Parking App Development

How to Ensure Live Parking Status?

The key is choosing the data exchange protocol. MQTT or WebSocket with an event-driven model. In one project for a network of 8 parking lots (about 2000 spaces), we replaced polling (every 60 seconds) with an event-driven architecture using MQTT and a WebSocket proxy. Update latency dropped from 60 to 1–2 seconds, and traffic reduced 30 times: 1440 requests per day vs. 10–50 messages. Result: real-time status became the main driver of user satisfaction.

Why Real-Time Status Is Critical in a Parking Mobile App?

When a driver sees a free spot and arrives to find it taken — that's lost time and trust. Polling at a one-minute interval gives stale data during peak hours. Event-driven architecture (MQTT/WebSocket) ensures users receive only actual changes, with no parasitic traffic. Comparison: event-driven beats polling by 30x in traffic volume and 30–60x in latency.

Load Comparison: Polling vs Event-Driven

Map and Navigation to a Free Spot

We render the parking lot map (level-by-level spot layout) via SVG rendering or custom Canvas. Google Maps and MapKit don't fit — indoor layout is needed. We use SVG with identifiers for each parking bay, colored by status through DOM manipulation or native Canvas.drawPath.

Navigation to the parking lot uses standard Google Maps/MapKit deep links. Indoor navigation to a free spot is optional via BLE beacons (Estimote, Kontakt.io) with Indoor Positioning. This adds complexity and cost, justified only for large multi-level parking garages.

How to Implement Real-Time Status: Step-by-Step

1. Audit parking equipment (barriers, sensors, payment terminals).
2. Choose protocol: MQTT or WebSocket based on load.
3. Set up broker (mosquitto, EMQX) and subscribe mobile app to topics.
4. Implement persistent connection on mobile side (BGProcessingTask/WorkManager).
5. Integrate with payment gateway (Stripe, YooKassa) to sync entries/exits.
6. Test with real equipment for 2 weeks.
7. Deploy and monitor (Firebase Crashlytics + Sentry).

What's Included in Turnkey Development

• Audit of existing equipment and payment infrastructure
• Integration design (MQTT/REST from controllers, ANPR, payment gateway)
• Design of parking layout and mobile interface
• MVP development in 6–10 weeks; full version with indoor navigation up to 4 months
• Testing on real equipment (barriers, sensors)
• Publication to App Store and Google Play, monitoring setup (Firebase Crashlytics + Sentry)
• 3-month warranty support, admin training

Stages and Timeline

Pricing is determined individually after an audit. We have many years of experience and have delivered over 15 projects for commercial parking lots. We'll evaluate your project within 2 days — get a consultation and timeline estimate tailored to your infrastructure. Contact us to discuss developing a mobile app for your parking lot.

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.