Where the app is going - and why
Curious what's coming next for Family-Tracking? Here's an honest look at what we're building, what's already shipped, and what's still being figured out.
Send feedback on prioritiesPhases of work, laid out plainly
Each phase targets a specific gap - from core Life 360 tracker compatibility to deeper Android reliability. Progress is real but uneven, as it usually is.
Foundation: location core and Android baseline
Rebuilt the location engine from scratch after repeated reports of drift on Life 360 for Android devices. Background tracking now holds position correctly on most mid-range handsets without draining the battery at the old rate.
Location Sharing & Safety - group layer
Expanding from individual tracking to shared group sessions. Families and small teams can now view each other's positions on a shared map without needing separate accounts. Permission controls are being reworked - the current flow is too confusing for first-time users.
Alerts, zones, and cross-platform parity
Geofence alerts have been requested consistently - the plan is to support custom zones with entry and exit notifications. iOS and Android builds will reach feature parity here, something that's been missing since the Life 360 tracker integration was first added.
Offline mode and low-signal handling
Rural users and people in areas with patchy coverage lose location data entirely right now. This phase looks at caching last-known positions and queuing updates for when the signal returns - no promises on timeline yet.
What's guiding the order of work
Priorities shift based on support volume, platform changes, and what breaks unexpectedly. These three areas are shaping most decisions right now.
Android fragmentation pressure
Life 360 for Android runs on hundreds of device variants. Manufacturers modify background process handling differently, which means a fix on one device can break another. Testing coverage has expanded to 34 device profiles this quarter.
- 34 device profiles
- Android 12–14
- OEM-specific patches
Support ticket patterns
Most incoming tickets cluster around two problems: location drift during commutes and group sharing invites that silently fail. Both are in active work. Ticket data from the past 90 days is the primary input for sprint planning.
- Location drift
- Invite failures
- 90-day data window
Location Sharing & Safety standards
Regulations around location data differ by country. The app's permission model is being updated to meet requirements in the EU, UK, and several APAC markets - not just as compliance, but because clearer consent flows reduce user confusion regardless of region.
- EU compliance
- APAC markets
- Consent flow update