GPS Child Tracking: Mobile App Implementation

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.

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.

How we implement tracking — step by step

1. Requirements analysis (accuracy, update frequency, platforms)
2. Design of collection and transmission scheme (local buffering, batching)
3. Development of native location module for iOS (Swift + CoreLocation)
4. Development of native location module for Android (Kotlin + FusedLocationProvider)
5. Backend integration (REST/WebSocket)
6. Testing on real devices (Xiaomi, Huawei, Samsung, iPhone)
7. Review preparation (Privacy Policy, permissions, App Store Connect)
8. 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:

1. Accumulate points locally in SQLite / Room (Android) or Core Data (iOS)
2. Send batches every 30-60 seconds or after accumulating N points — reduces network usage by 70% and battery drain by 20%
3. 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.

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.