Stride
Run tracking that earns the location permission.
GPS run tracking with live route mapping, analytics and a social feed — built so that the most sensitive permission it asks for is used for exactly one purpose.
Background modes
location only
Auth flow
PKCE
Deep links
Verified
Overview
Stride records runs. Live GPS tracking with the screen off, a mapped route, splits and pace, a history you can replay, and analytics that make a training block legible rather than just logged.
It also asks for the most sensitive permission in this whole portfolio — precise, background location — so the app is built to justify it narrowly. The only background mode declared is `location`; nothing performs a background fetch, because an unused background mode is something store review asks about and a user should not have to trust blindly.
The social layer is opt-in: follow friends, see their runs, compare over a period. Release builds refuse to compile without their credentials configured, so a signed binary cannot ship pointing at nothing.
What it does
Precise location, used for one thing
Live GPS run tracking
Records the route with the screen off via a foreground location service, with the run visible as it happens.
Mapped routes
Every run rendered on a Mapbox map, replayable from history.
Splits, pace and analytics
Per-kilometre splits, pace trends and a training view that makes a block of work legible.
History
Every recorded run, with its route, stats and detail view.
Social feed
Follow friends and see their runs. Opt-in, and scoped to people you choose.
Deep links
Verified App Links so a shared run opens directly in the app rather than a browser.
Notifications
Preferences you control, per category.