OpenTracks is a sport tracking application that completely respects your privacy.
| Free | Paid (same as free) | Donations | Translations |
|---|---|---|---|
|
|
|
Transifex |
- Tracking: track your sport and outdoor activities
- Photos and Markers: mark interesting locations while tracking (also with photos)
- Bluetooth LE sensors:
- heart rate
- cycling: speed and cadence
- Export data: export tracks either as KMZ (incl. photos), KML or GPX
- No Internet access: Internet is not used
- Voice announcements
- No advertising
- Privacy:
- does not contain any in-app analytics
- does not use Google Play Services
- has no cloud integration
Only required permissions:
- ACCESS_FINE_LOCATION: required to use the GPS.
An overview of Bluetooth LE sensors that are known to work with OpenTracks is in README_TESTED_SENSORS.md.
Please note: OpenTracks does not contain a map (as this would required Internet access).
As of v3.3.1 OpenTracks enables to use custom dashboards. The reference implementation is OSMDashboard, which presents an OpenStreetMap map (showing the current track, incl. updates). The developer documentation is in README_API.md.
Alternatively, recorded tracks can be shared as KMZ/GPX to installed applications (e.g., OsmAnd or MAPS.ME). However, this is rather slow and does not provide updates while recording.
OpenTracks is based upon Google My Tracks app (code). Initially, My Tracks was initially released by Google in 2010 as open-source software. In 2016, Google decided to discontinue My Tracks and stopped distributing it via the Google Play store in April 2016. The Plonk42 conducted some maintenance work until 2016, so My Tracks could still be used (based upon version Google's MyTracks version 2.0.6). Plonk42's version is available here. In 2019, OpenTracks was forked from Plonk42's My Tracks and major rework was conducted.
Rework of OpenTracks included:
- removing Google's analytics code,
- removing integration into Google Drive,
- removing Google Maps integration,
- removing Google Earth integration,
- removing use of Google Play service,
- removing calorie estimation and activity estimation,
- removing support for ANT+ and Classic Bluetooth,
- adding support for Bluetooth LE heart rate sensors,
- removing Protobuf (store sensosensorr data in SQLite columns directly), and
- removing Android Service API for other apps.
Artwork, logos and user interface remained more or less unchanged.
More information about Google My Tracks: