We develop mobile apps for children's GPS trackers that solve a real problem: a parent sees the child hasn't left school on time but the tracker's battery died. We ensure that a low-battery push notification arrives ahead of time, and the route history is accessible for any past day. This is not just a map — it's a safety system with geofences, an SOS button, and data privacy. Our experience includes more than 10 IoT and telematics projects, 5 years on the market. We guarantee compliance with App Store Review Guidelines and Google Play Policy.
Architecture: Device + Server + App
A children's GPS tracker is a watch, pendant, or small keychain with a SIM card. It does not run a mobile app. It sends SMS commands or GPRS packets to a server over a proprietary protocol. Popular models: Wonlex GW400S, WONLEX KT07, Smart Baby Watch Q90 — all use a simplified ASCII protocol over TCP or SMS.
The mobile app is the interface to the telematics server that already parsed the tracker's packets. The development challenge is creating a good UX on top of an existing or custom API.
How to Implement Map and Route History?
The current position of the child on the map is the top interface priority. A marker with the child's photo, last update time, battery level, and GSM signal strength. This is the first screen when opening the app.
History for the day — a track with stop markers. A stop is a cluster of points with speed < 3 km/h longer than 5 minutes. The address is reverse geocoded. "At school from 08:35 to 14:25, then at the mall from 14:38 to 15:02".
A timeline at the bottom of the screen — horizontal time scale with visit points. The user drags a slider — the map marker jumps to the position at the selected time. This is more convenient than scrolling through a list of addresses.
Safe Zones and School Schedules
Home geofence — a circular zone, the user sets a radius (e.g., 200 m). When the child leaves the zone — push to parents (both parents if both have the app).
School geofence — entering the zone at expected time: push "Vanya arrived at school at 08:42". This is called safe zone arrival/departure and it is the main feature parents want.
Schedule notifications. The parent sets: "Notify if the child hasn't arrived at school by 09:00". This is a scheduled check — a server-side task that at 09:00 checks if the child's point was inside the School zone in the last 30 minutes. Not an IoT event, but a scheduled check via cron.
SOS Button: What to Know?
The physical device has an SOS button. Child presses → tracker sends an emergency packet to the server → server pushes to all parents with an "SOS" label and current coordinates.
The push must arrive immediately with maximum priority. APNs critical alert (requires special entitlement from Apple) — arrives even in Do Not Disturb mode and vibrates twice. On Android — FCM priority: high with channelId: "emergency" with IMPORTANCE_HIGH and setBypassDnd(true).
Sound alert when the app screen is open — AVAudioPlayer (iOS) or SoundPool (Android) with the system alarm sound.
How to Protect Child Data in GPS Tracker?
The child's coordinates are data of a minor. Storage and processing require compliance with GDPR (Europe) or 152-FZ (Russia). Specific requirements:
- Encryption at rest (iOS Data Protection Class A, Android Keystore)
- Transmission only over TLS 1.3
- Access only by authorized parents/guardians
- Retention policy: location history max 90 days (configurable)
- Ability to export and delete data
In the App Store, such apps fall into the "Kids" category if explicitly positioned for children — then COPPA restrictions and limited advertising apply. If the app is for parents (not for children), it can go into the regular Navigation or Utilities category.
What Protocols Do Popular Kids Trackers Use?
Wonlex GW400S uses a GPRS-based protocol: short ASCII packets with coordinates, status, and commands. Position update interval — from 10 to 60 seconds. WONLEX KT07 supports SMS commands for configuration and call, with position sent every 5–15 minutes. Smart Baby Watch Q90 is a hybrid: GPRS for tracking and voice calls, SMS for SOS. We audit your tracker's protocol and implement the parsing.
Chat with the Child
A simple chat via server — text messages from parent to tracker (displayed on the screen), voice messages, or short predefined responses from the child. Limitation: the tracker's screen is small or absent — child's responses are often "button responses" (1 = OK, 2 = Coming home, 3 = SOS).
Implementation: WebSocket for real-time chat, push for new message notifications, MQTT from server to tracker for delivering SMS commands to the device.
Work Process and Timelines
| Stage |
Content |
Duration |
| Tracker audit |
Device protocol, server API, supported features |
1-2 days |
| Map + history |
Position, daily track, timeline |
2-3 weeks |
| Geofences and schedules |
Home, school, scheduled checks |
1-2 weeks |
| SOS and notifications |
Critical alerts, emergency pushes, sound |
1-2 weeks |
| Chat |
Parent ↔ child messages |
1-2 weeks |
| Privacy compliance |
GDPR/152-FZ audit and adjustments |
1-2 weeks |
| Publication |
App Store + Google Play, code signing, provisioning |
1 week |
Checklist: Typical Tracker Integration Mistakes
- Protocol incompatibility: tracker sends data in HEX, server expects ASCII.
- Absence of heartbeat: if tracker does not send packets for >5 minutes, app loses connection.
- Ignoring timezone: coordinates come in UTC but are displayed without offset.
- Incorrect packet parsing: tracker may change field order in different firmware versions.
MVP (map + geofences + SOS + history): 6–10 weeks. Full platform with chat, schedules, audio, and compliance: 3–5 months. Cost is calculated individually after auditing the tracker's API and security requirements.
Our Strengths
Over 5 years of experience in IoT app development, 10+ projects for children's trackers. We guarantee compliance with app store policies and personal data legislation. Contact us — we will assess your project in 2 days. Get a consultation on tracker integration today.
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.
