Implementing Safe Zones for Kids Tracker in a Mobile App
Safe Zones — geofencing: the app should provide reliable location monitoring and notify a parent when a child leaves school or arrives home. Sounds simple. In practice — notification delay up to 5-10 minutes, triggering when a bus stops at the school fence, and false alarms due to GPS drift of 50-100 meters in urban areas. We solve these problems using a combination of native geofencing, server-side filtering, and adaptive thresholds. This guide covers both iOS CLCircularRegion and Android Geofencing API implementations. We'll evaluate your project within 1 day — just reach out to us.
How Geofencing Works on iOS and Android
iOS — CLLocationManager.startMonitoring(for: CLCircularRegion) (the iOS CLCircularRegion API). The system monitors up to 20 regions simultaneously per app. Entry/exit detection accuracy is around 100-200 meters, delay up to 3-5 minutes. Regions are persisted by the system and continue monitoring even after device reboot, which is crucial for a child tracker. Apple Developer Documentation
Android — Geofencing API via GeofencingClient from Google Play Services (the Android Geofencing API). Limit — 100 geofences per app. Notifications come via PendingIntent to BroadcastReceiver or IntentService. On Android 12+, FINE_LOCATION is mandatory for geofencing, BACKGROUND_LOCATION for background operation. Adding a geofence: GeofencingRequest.Builder with setInitialTrigger(GEOFENCE_TRANSITION_ENTER) and the necessary loiteringDelay to filter out momentary passes.
| Parameter |
iOS |
Android |
| Max zones |
20 |
100 |
| Urban accuracy |
100-200 m |
50-150 m |
| Notification delay |
3-5 min |
1-5 min |
| Background monitoring |
Yes (persistent regions) |
Yes (with Doze limitations) |
How to Reduce False Alarms?
In dense urban areas, GPS accuracy drops to 50-150 meters due to multipath signal reflection. If the Safe Zone radius is 100 meters (typical yard), drift easily pushes the point outside. Solution: use not a single point but a median of the last 3-5 measurements before deciding on a transition. On the server — a track smoothing algorithm (Kalman filter or simple weighted moving average based on horizontalAccuracy). Our median filter is 3 times more accurate than single-point detection.
Second layer of protection: loiteringDelay in the Android Geofencing API — 60-120 seconds. This means the DWELL event will only fire if the device stays within the zone for that time, not just passing through. Our filtering reduces false alarms by up to 5 times compared to standard geofencing.
What's Included in the Turnkey Implementation of Safe Zones
| Stage |
Result |
| Analytics |
Define scenarios, select radius and sensitivity |
| Design |
Client-server architecture, geofence scheme |
| Implementation |
Integration with maps, zone setup, event processing |
| Testing |
Field tests in different locations, debugging false alarms |
| Deployment |
Publish to App Store / Google Play, monitoring |
Deliverables include: API documentation, commented code, push notification configuration, team training (1-2 hours), and 30-day support after delivery.
Work Process
-
Analytics — discuss scenarios: school, home, extracurriculars. Determine radii and priorities.
-
Design — draw architecture: server stores zones, child's app receives them via APNs FCM, registers geofences.
-
Implementation — write code in Swift/Kotlin/Dart, configure server-side filter.
-
Testing — visit locations (school, park) with real devices, adjust thresholds.
- Deployment — upload to stores, set up CI/CD, provide access to monitoring dashboard.
Common Mistakes with Geofencing Implementation
- Too small radius (<50 m) → frequent false alarms due to GPS drift.
- No server-side filtering → notifications on every passing-by.
- Ignoring Doze mode on Android → notifications don't arrive at night.
Notifications and Reliability
Push notification must reach the parent as fast as possible. APNs FCM with high-priority — delay is usually 1-3 seconds. But the geofence event from the system may be delayed: iOS guarantees firing "on the next significant motion or location update," Android in Doze mode — only when it exits Doze.
For critical notifications (leaving zone at night), consider duplicating via SMS as a fallback — especially for children with budget Android phones without stable internet.
Timelines and Pricing
Implementation time for Safe Zones module — 1-3 weeks. Costs start at $5,000 for a single platform (iOS or Android) and range up to $15,000 for both platforms, depending on complexity. Clients typically save $2,000 per month on support costs due to reduced false alarms. Over the years, we have completed more than 30 projects with geolocation. Get in touch with us to evaluate your project — we'll prepare a commercial proposal within 1 day.
Editing Zones in the Parent App
UI for Safe Zones: the user should be able to draw a zone on the map or enter an address + radius. Both Google Maps SDK and MapKit support overlays for drawing circles. Minimum sensible radius — 50 meters (otherwise too many false alarms), maximum — 5 km.
Zones are synced with the server and pushed to the child's device via APNs FCM data-push, after which the child's app re-registers geofences. When changing smartphones or reinstalling the app — automatic zone download from the backend.
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
| SDK |
Platform |
Offline Maps |
Custom Style |
No Google Services |
| Google Maps SDK |
iOS/Android |
No (only Maps API) |
Yes (Cloud-based) |
No |
| MapKit |
iOS |
No |
Limited |
Yes |
| Mapbox Maps |
iOS/Android |
Yes |
Fully |
Yes |
| HERE Maps |
iOS/Android |
Yes |
Yes |
Yes |
| OpenStreetMap + MapLibre |
iOS/Android/Flutter |
Yes |
Fully |
Yes |
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
-
Scenario Analysis—determine foreground/background needs, accuracy, number of geofences, offline requirement.
-
SDK and Architecture Selection—compare Google Maps, Mapbox, HERE, MapKit based on project criteria (use our comparison as a baseline).
-
Integration and Permission Setup—configure
Info.plist / AndroidManifest.xml, test review checks (App Store Review Guidelines Sections 4.2/5.1, Google Play policy).
-
Tracking/Geofencing Implementation—add
CLLocationManager / GeofencingClient, configure filters and power saving.
-
Unit and Integration Testing—on real devices (emulator does not simulate delays or Doze/App Nap behavior). Test at least 50 scenarios.
-
Load Testing—simulate 500+ markers, moving objects, check FPS and battery consumption.
-
Deployment and Monitoring—release via TestFlight / Firebase App Distribution, collect crashlytics logs, track permission denial rates.
Timeline and Deliverables
| Stage |
Timeline |
Deliverables |
| Basic map integration with markers and search |
1–2 weeks |
Source code (Swift/Kotlin/Dart), API documentation, build instructions |
| Geofencing with push notifications |
2–3 weeks |
Geofence code, FCM/APNs setup, test zones, delay report |
| Full route tracking (background, smoothing, server sync) |
4–6 weeks |
Code with Kalman filter, server part (optional), battery monitoring |
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.
