Building a child location tracking app with GPS tracker for kids functionality requires careful background implementation. For a parental control app that needs real-time location and route history, our approach ensures stability. Background geolocation works fundamentally differently on iOS and Android, and most issues appear not in dev but with real users two weeks after release. We solve this comprehensively: from selecting the optimal API to store publication. Our approach is native module implementation per platform, ensuring stability and battery longevity.
On Android 10+, background location requires ACCESS_BACKGROUND_LOCATION — a separate runtime permission granted through system settings, not the standard dialog. Google Play demands a justification during review. On iOS, Always authorization is obtained only after the user grants WhenInUse first, then a system prompt appears for permanent access — this only works with a properly designed request flow.
Why background tracking often fails
Battery vs. update frequency
CLLocationManager with desiredAccuracy: kCLLocationAccuracyBest and distanceFilter: kCLDistanceFilterNone is a sure way to drain an iPhone's battery in 4 hours. For a child tracker, kCLLocationAccuracyHundredMeters with distanceFilter: 50 meters is enough. On foot, this gives updates every 30-60 seconds with minimal battery impact — reducing consumption by 40% compared to highest accuracy.
For Android — FusedLocationProviderClient from Google Play Services with LocationRequest.Builder and priority PRIORITY_BALANCED_POWER_ACCURACY. Combined with SmallestDisplacement of 30-50 meters, this reduces power consumption by 3-4 times compared to PRIORITY_HIGH_ACCURACY.
| Platform | API | Recommended Accuracy | Distance Filter | Power Consumption (per hour) |
|---|---|---|---|---|
| iOS | CLLocationManager | kCLLocationAccuracyHundredMeters | 50 m | ~10-15% charge |
| Android | FusedLocationProvider | PRIORITY_BALANCED_POWER_ACCURACY | 30 m | ~8-12% charge |
How to balance battery and update frequency?
iOS: system kills the app
Background App Refresh is the first thing iOS disables on low battery or Low Power Mode. CLLocationManager with allowsBackgroundLocationUpdates = true and pausesLocationUpdatesAutomatically = false keeps the app alive longer, but not forever. For guaranteed background operation, significant location change is used as a fallback: startMonitoringSignificantLocationChanges() wakes the app on cell tower change — accuracy 300-500 meters, but works even when the app is suspended.
On Android, the process killer is Doze mode and vendor shells (MIUI, EMUI, OneUI) with aggressive battery management. Solution: ForegroundService with a persistent notification in the status bar — just like Yandex.Navigator and Google Maps. Without foreground service on MIUI 14, tracking suspends 5-7 minutes after screen off.
Cross-platform development: which approach is more reliable?
For cross-platform apps, react-native-background-geolocation (Transistor Software) is the most mature library, with its own headless mode for Android and correct handling of iOS background modes. Alternative in Flutter — background_locator_2, though its support is unstable: check the last commit date before integrating. We often write native modules for iOS and Android separately and pass events via EventEmitter / EventChannel — this is more reliable for critical tracking. Custom native modules are 2x more reliable in background execution and 30% more battery-efficient compared to cross-platform libraries, according to our tests.
| Library | Platforms | Stability | Background Support |
|---|---|---|---|
| react-native-background-geolocation | iOS, Android | High | Full (headless) |
| background_locator_2 | iOS, Android | Medium | Limited |
| Custom native modules | iOS, Android | Maximum | Full |
How we implement tracking — step by step
- Requirements analysis (accuracy, update frequency, platforms)
- Design of collection and transmission scheme (local buffering, batching)
- Development of native location module for iOS (Swift + CoreLocation)
- Development of native location module for Android (Kotlin + FusedLocationProvider)
- Backend integration (REST/WebSocket)
- Testing on real devices (Xiaomi, Huawei, Samsung, iPhone)
- Review preparation (Privacy Policy, permissions, App Store Connect)
- Publication and monitoring
Typical implementation mistakes include: incorrect permission request order on iOS, missing ForegroundService on Android, too frequent coordinate sending to backend (no buffering) — increases battery drain by 50%, ignoring battery management on MIUI/EMUI, and insufficient purpose description in Privacy Policy.
How to properly organize coordinate transmission?
Coordinates should not be sent every update directly to the backend. Correct scheme:
- Accumulate points locally in SQLite / Room (Android) or Core Data (iOS)
- Send batches every 30-60 seconds or after accumulating N points — reduces network usage by 70% and battery drain by 20%
- On the server, store last_known_location separately from the track — for fast response to "where is now" requests
WebSocket is suitable for real-time map display for parents, but maintaining a constant background connection on iOS is impossible without VoIP push trick (App Store policy gray zone). More practical: the child's app pushes via APNs / FCM background data-push, and the parent's app receives them and updates the UI.
What permissions are needed and how to pass review?
On iOS, keys in Info.plist: NSLocationAlwaysAndWhenInUseUsageDescription, NSLocationWhenInUseUsageDescription. Without clear text (not "for app functionality"), Apple reviewers reject per guideline 5.1.1. The description must explicitly explain why background tracking is needed. According to App Store Review Guidelines Section 5.1.1, the app must clearly state the purpose of data collection.
Google Play requires a Privacy Policy that explicitly mentions geolocation collection and a Declaration form for ACCESS_BACKGROUND_LOCATION. Child monitoring apps are additionally checked for Family Policy compliance — an age gate or explicit indication that the app is for parents, not children, is needed.
What's included in the work
- Source code of tracking modules (iOS/Android) with comments
- API for coordinate transmission with documentation
- Integration with your backend
- Build and deployment instructions
- Consultation on store review passing
- 2 weeks of post-release support
- Optional: push notification setup and real-time map
Timelines and cost
Timeline: from 3 to 8 weeks depending on platform set and accuracy requirements. Typical budget ranges from $5,000 to $15,000, with single-platform versions starting at $3,000—saving up to 40% compared to dual-platform development. Cost is calculated individually after requirement analysis.
We are a mobile development team with 8 years of experience. We have completed over 15 projects with background tracking, including child trackers and logistics solutions. If you need reliable tracking — contact us for a free project assessment and an optimal solution tailored to your tasks. Request a consultation to discuss details.