Mile32 is a native iOS training dashboard for serious runners. Sync your runs from Apple Health, visualise your fitness load, track your recovery, and build towards your A-race — no account, no analytics, no servers of ours holding your training and health data.
The same screens are in the App Store listing. They show a demo athlete's data, not anyone's real training. Swipe or scroll for more, and tap a screen to enlarge it.
A plan from your starting long run, peak-week target and race date. Phases are assigned automatically. Reschedule at any time — completed weeks are kept.
Plan your distance progression and track it against what you actually ran. The Bulk Plan Editor updates every upcoming week in one screen. Completed runs leave the plan on their own.
Building a new plan archives the one it replaces, so a finished training block leaves a record rather than being overwritten. Volume, adherence and how the block ended, kept for the next one.
Fitness, Fatigue and Form on a 90-day chart. The Fitness tile colours by whether you are building, holding or fading; Form says whether you are ready to race.
Finish times from marathon to 150+ km, using your recent runs, logged results (Riegel), an imported GPX course and race-day conditions. Add a run/walk strategy to model your execution plan.
Draws on fitness, form, HRV trend, long-run consistency and race proximity. Five labels from Base Building to Race Ready, with a per-component breakdown.
Three separate channels: how hard your heart worked, the pounding your legs took, and the braking load of descents. Each measured against your own recent normal — no population thresholds, no risk labels, no blended score.
Flags dips in your resting heart rate and HRV trends, so you can back off before a hard block becomes a problem.
Log an injury — the body part, the type, when it started and when it cleared. Each one draws as a bar across the weeks it affected, over a strip of your weekly distance, so a flare-up next to a hard week is there to notice. Shown for context, never as a cause: minor entries are recorded and never touch your readiness or training scores.
Your own routine, with the sets ticked off as you do them and the days you are meant to do them on. A month calendar shows the shape of a whole block at a glance, and your adherence feeds the Durability score. With an injury open it reads as rehab rather than prehab.
Live queries for resting heart rate, HRV, sleep, active calories, wrist temperature and weight. No export needed.
Log every race, upcoming or completed. The Race Day Card lays out your checkpoint plan with target times, ETAs and cut-offs.
A race-week checklist in four phases — 2 Weeks Out, Race Week, Day Before, Race Morning. Items surface at the right time, with a status on the Overview tab.
Weekly and yearly distance targets, with a monthly view derived from the weekly one. Each shows distance achieved against target.
Full run history, filterable by All, Runs or Walks, with an adjustable minimum distance and a configurable number of results.
What each pair has carried: distance, the terrain it is used for, how it rotates with the rest, effort-matched pace, and how familiar it is with your next race. Pairs can be imported from a RunGap export and matched to runs already in the app.
Personal bests across 25 distance categories, plus auto-detected milestones in eight: Distance, Vertical, Volume, Training, Endurance, Consistency, Conditions and Progress.
A pre-race kit checklist in collapsible sections. Export it in the app's dark style, ready to screenshot before race morning.
Five Home Screen widgets — Distance, Elevation, a combined Training widget, a Volume Heatmap and your last run's route. Two Lock Screen widgets: Fitness alone, or Fitness, Fatigue and Form together.
Long-press a run to build a card. Three styles, three crops, an optional background photo, and your GPS route traced on top. Share it, or save it to your camera roll.
Import a race's GPX for grade-adjusted checkpoint splits, aid-station markers and a cut-off time-bank — so your plan reflects the course, not just the distance.
Adjusts your predicted finish for race-morning heat or cold, allowing for the heat acclimatisation you have built in training.
Fills in temperature and conditions for past runs, and tracks the range of weather you have actually trained in.
Import your pre-plan Apple Health history, so your fitness baseline stands on more than a few weeks.
Capture how a run felt — gut, legs, low point, and what you took on — so you learn your own patterns before race day rather than during it.
Finish times, bib numbers and medal photos kept alongside each completed race, with every medal on one wall in Achievements.
Track injection timing against your training load. A niche need, kept out of the way for everyone else.
Five screens: features, your race details, HR zones (with a Tanaka max-HR suggestion from your age), training targets and HealthKit permissions.
No account, no analytics, no Mile32 servers. Your data lives on your iPhone and syncs through your own private iCloud; the only other network calls are anonymous weather lookups.
Mile32's Fitness number reads higher than Strava's or TrainingPeaks' for the same training, often by a lot. Different formula, not inflation.
Fitness, Fatigue and Form use the Banister TRIMP model — heart-rate impulse, exponentially weighted. TrainingPeaks' CTL uses TSS, a pace- or power-based scale that reads 1.5–2× lower. Neither is right; they measure different things.
What Mile32 will not do with the number matters more: turn it into a verdict. No safe zone, no injury-risk score, no blend of heart, legs and descent into one traffic light. Those averages come from team-sport cohorts and say little about a training log of one. You get where today sits against your own history, and the reading is yours.
Yes — but how well depends on what your watch sends to Apple Health, and the differences are larger than you would expect.
Mile32 reads everything from Apple Health. It never talks to a watch directly, which is what keeps your data on your phone.
The fix is RunGap — a separate paid app that reads from Garmin, COROS, Polar, Suunto and around fifty other services and writes the full workout, route and heart rate included, into Apple Health. Mile32 then sees it like any other run.
One step matters and is easy to miss: turn off Workouts and Heart Rate in your watch app’s own Apple Health sharing first. RunGap skips any workout already in Health with the same start time, so if your watch’s summary copy lands first, nothing improves and you will not be told why.
To check what you are actually getting: Settings → Troubleshooting → Check Health Sources. It lists every type Mile32 reads, which app wrote it, and whether your workouts carry routes and a real heart-rate series.
Separately, the Health tab (resting HR, HRV, sleep, wrist temperature) needs a watch that records those metrics. Wrist temperature and heart-rate recovery are Apple Watch only; where a signal is missing, Recovery and Race Readiness reweight across what is left rather than counting the gap against you.
Long-press any run row in the Run History list (Runs tab).
From there you can pick:
For Apple Watch runs the route comes from HealthKit, drawn in green with start and finish markers. Tap Share… for the iOS share sheet, or Save to Photos for full resolution.
Two ways:
Bulk Plan Editor — the ⋯ menu on the Training tab, then Edit Plan…. A scrollable table of upcoming weeks, with target distances and phase labels (Re-entry, Build, Build+, Recovery, Peak, Taper, RACE, Injury) editable inline. Save commits everything at once; Cancel discards. Only future, uncompleted weeks appear.
Per-week — tap any week row in the Plan view.
From Apple Health. Apple Watch activities are already there — open Mile32 and they appear, with distance, pace, heart rate, elevation and GPS route.
Any app that writes running workouts to Apple Health syncs too, Garmin Connect, Strava and Runkeeper among them. Set how far back to import in Settings → Apple Health Sync.
Read-only access to:
All of it is queried on-device. Nothing is sent to Mile32; what Mile32 derives from it syncs through your own private iCloud so your training matches across your devices. Revoke at any time in Settings → Privacy & Security → Health → Mile32.
The Karvonen heart rate reserve method, which accounts for your resting HR. Set your max and resting HR in Settings → HR Zones. Defaults, all adjustable:
Shown as a bar on Overview and broken down on Training. Changing the boundaries applies retroactively to every synced run.
The three numbers behind the Fitness Load chart:
All three update daily, plotted over 90 days on the Training tab.
Walks and hikes count fully towards Training Load and time on feet, but not towards running distance, pace, zone or personal-best stats — a walk is not a run, whatever its load.
A pace filter catches slow activities HealthKit has not already tagged: slower than 9:00/km is treated as a walk. Mark a session as deliberate run/walk practice and it is exempt, blended pace included.
Excluded activities still appear in your run list. They just do not feed the Fitness Load chart, zone distribution or weekly volume.
Home Screen — long-press an empty area, tap +, search for Mile32. Five are available: Distance and Elevation (small/medium), a combined Training widget and a Volume Heatmap (large), and your last run's route.
Lock Screen — long-press the lock screen, tap Customise, then a widget area. Two are available: Fitness alone, or Fitness, Fatigue and Form together.
Set your weekly targets and long run day in Settings → Training Targets to keep them current.
Settings → Data → Clear All Data permanently deletes your runs, training plan, races, kit, gear, injuries, physio history and everything you have earned — on this device and in your iCloud, so it does not come back on another one. Your settings and preferences are kept, so you do not have to set the app up again.
Deleting the app removes the local copy. HealthKit data lives independently in Apple Health and is unaffected by any of this.
The full policy covers what Mile32 reads from Apple Health, exactly what leaves your phone (a rounded run start point or race location, and a date, for weather) and how to remove your data.
Read the full privacy policy →
Questions? support@mile32.app
When reporting a bug, it helps to include your iOS version, iPhone model, and a description of what you expected vs what happened. Screenshots are always welcome.
Feature requests are very welcome — Mile32 is actively developed and the roadmap is shaped by runner feedback.