Geofencing Implementation in Mobile Apps: Overcoming Platform Limitations

An app with geofences that stops delivering notifications on iOS 17 is not a bug in your code. Apple rewrote the background location monitoring logic, tightened permission description requirements, and added new limits. A similar picture on Android: Doze mode, aggressive vendor battery optimizations, and a separate permission for background location with manual review in Google Play. Developers ignoring these nuances get a silent app and poor reviews.

We integrate geofences considering all platform constraints. With 10+ years of experience and 50+ geofencing projects, we ensure stable operation on the latest OS versions.

Platform Limitations: Comparison Table

iOS. CLLocationManager supports up to 20 active geofences simultaneously—system limit, not ours. Minimum radius is 100 meters; smaller radii are not monitored. On devices without A12+ chips, accuracy is even lower. CLCircularRegion delivers didEnterRegion / didExitRegion events, but delay can be 3-5 minutes depending on power saving mode. On iOS 13+ you must request Always authorization through a two-step dialog: first whenInUse, then the user goes to Settings. You can't directly ask for Always anymore—Apple will reject during review.

Android. Geofencing API in com.google.android.gms:play-services-location requires Google Play Services. On Huawei without GMS—need a separate path via HMS LocationKit. Android 10+ introduced ACCESS_BACKGROUND_LOCATION as a separate permission that the user grants in Settings, not in the standard dialog. On Android 12 SCHEDULE_EXACT_ALARM was added for precise alarms—without it, Geofencing on Doze devices may not trigger at the right time. Some manufacturers (Xiaomi MIUI, Samsung One UI with aggressive battery saver) kill background services before the API delivers the event.

How to Solve the Geofence Limit Exceeded Problem?

iOS: Basic Scenario

let region = CLCircularRegion(
    center: CLLocationCoordinate2D(latitude: 55.7558, longitude: 37.6173),
    radius: 200,
    identifier: "office_zone"
)
region.notifyOnEntry = true
region.notifyOnExit = false
locationManager.startMonitoring(for: region)

When exceeding the 20-zone limit, we prioritize by distance from current position and dynamically reload the set of active regions via stopMonitoring / startMonitoring. Rotation logic is in locationManager(_:didUpdateLocations:).

For projects needing more than 20 zones or radius less than 100 meters, we switch to Visit Monitoring (startMonitoringVisits()) or Significant Location Changes combined with server-side geofence check by coordinates.

Android: Geofencing API + WorkManager

val geofence = Geofence.Builder()
    .setRequestId("warehouse_exit")
    .setCircularRegion(lat, lon, 150f)
    .setExpirationDuration(Geofence.NEVER_EXPIRE)
    .setTransitionTypes(Geofence.GEOFENCE_TRANSITION_ENTER or Geofence.GEOFENCE_TRANSITION_EXIT)
    .setLoiteringDelay(30_000) // DWELL after 30 seconds
    .build()

val request = GeofencingRequest.Builder()
    .addGeofence(geofence)
    .setInitialTrigger(GeofencingRequest.INITIAL_TRIGGER_ENTER)
    .build()

geofencingClient.addGeofences(request, geofencePendingIntent)

The PendingIntent leads to a BroadcastReceiver that launches a WorkManager task instead of executing logic directly. This is important: direct execution of a long task from a Receiver on Android 8+ causes a BackgroundExecutionLimits exception.

For Huawei HMS, com.huawei.hms:location provides almost identical API, but requires a separate PendingIntent registration via GeofenceService.

Why Server-Side Validation Is Not an Option But a Necessity?

Mobile geofencing is inherently unreliable. For critical business scenarios (transport departure control, gamification with prizes) we build an additional server-side check: the device periodically sends coordinates, the server checks polygon intersection via PostGIS or geofence via Redis GEORADIUS. Mobile Geofencing provides a fast trigger; the server is the final arbiter.

Handling Permissions Correctly

The most common reason for App Store rejection is improper explanation of NSLocationAlwaysAndWhenInUseUsageDescription. Apple reads the strings in Info.plist and requires a specific description: "to send a notification when entering the pickup zone" instead of "for app operation".

In Google Play, since May 2023, background location undergoes manual review. The application must explain the specific use case and show a video demo. Allow 3-7 days for this.

What Is Included in the Work

• Geofencing API integration code for iOS (Swift 5.9+, SwiftUI/UIKit) and Android (Kotlin, Jetpack Compose).
• Handling limits and zone rotation.
• Proper permission management with text for App Store/Google Play.
• Testing: Walk Test on iOS and real drives on Android.
• Architecture documentation and description for review.
• Post-launch support: refinements, monitoring, bug fixes.

Work Process

Analysis of requirements: number of zones, minimum radius, platforms, presence of GMS in the target audience. Architecture design considering platform constraints. Implementation with correct permission management. Testing: Walk Test via Xcode Simulator Location, real drives for Android. Preparation of descriptions for review.

Timeline: from 3 to 6 days depending on the number of platforms and complexity of triggers. We will evaluate your project in 1 day—contact us for a consultation. Order turnkey geofencing implementation with a guarantee of correct operation on the latest OS versions.

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.