Live tracking
Location update frequency changes according to movement context.
- driving updates every few seconds
- stationary state
- walking state
- movement status
CASE / ANDROID / REALTIME
GPS / GEOFENCING / HISTORY / WEB
Real-time location — Android, geofencing and route history.
The platform combines an Android application, web backend and location logic for frequent updates, zones, daily history and user visibility rules.
CONTEXT
The system needed high-frequency tracking without sacrificing readable history or privacy controls.
The application required different behaviour for stationary, walking and driving states, with data visible both in the mobile app and on the web.
Geofencing, route history, stop merging, map scaling and user-to-user visibility were central requirements.
Geofencing
Users define zones and receive entry and exit events.
- zone radius
- entry / exit
- zone name
- visibility rules
Daily history
Routes and stops are aggregated into a readable reconstruction of the day.
- date selection
- segments
- stops
- event merging
Map and roles
The presentation layer handles avatars, roles, overlapping markers and map focus.
- roles
- avatars
- marker spreading
- person focus
ENGINEERING TAKEAWAYS
Lessons from a real-time location platform.
- Location frequency should depend on movement context rather than always using maximum sampling.
- Geofencing needs tolerance for GPS uncertainty.
- History should aggregate points into meaningful events.
- Map UX is as important as the tracking backend.
CASE / NEXT
SIMILAR ENVIRONMENT?
Discuss the environment