Health, home and travel decision
3AK Track & Field
A competent developer can build and maintain a minimal Track & Field session recorder and exporter in about a week; there are no evident durable moats on the supplied App Store page that would make rebuilding impractical.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Record timed runs/sessions, track laps/splits, store sessions locally, view past sessions and basic stats, export session data (CSV).
What it still won’t have
- Official App Store marketing placement and editorial features
- Built-in App Store distribution conveniences (updates, ratings) until published
- Any vendor-specific closed-source features the original app may offer
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
3AK Track & Field does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal iOS Track & Field session recorder using Swift + SwiftUI, Core Data (or SQLite), and AVFoundation for optional audio cues. Core features in scope: start/stop/pause session timer, record lap/split timestamps, save sessions with metadata (date, notes), session history list with basic stats (total time, number of laps, best lap, average pace), CSV export and share via UIActivityViewController, and simple unit tests for timer and storage logic. Out of scope: server sync, user accounts, in-app purchases, and complex coaching AI. Include error handling for storage failures, permission checks for background/gps where used, and automated tests covering timer accuracy and data persistence.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 3 cited sources+3
- Evidence score86
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productToday for iPhone - App Store
- open sourceendurain-project/endurain
- open sourcejovandeginste/workout-tracker
Integrity checks
What held up, and what did not.
