Running a half marathon plan from your phone
Every ranked answer to this question sells hardware. How to execute a published half marathon plan with a phone in your pocket and your splits read aloud.
Blog
Practical answers about training, pace, and tracking, written for runners who train alone with the phone already in their pocket.
Every ranked answer to this question sells hardware. How to execute a published half marathon plan with a phone in your pocket and your splits read aloud.
Local first does not mean nothing is uploaded. The categories that leave a running app, who receives them, and how to read a privacy label for yourself.
Signing in is a separate decision from tracking. What actually needs an account, what still leaves your phone while signed out, and how to check in three minutes.
GPS is useless indoors, so a phone counts steps and multiplies by an estimated stride. What that gets right, what it cannot, and why the number says estimate.
Arriving tonight, running tomorrow. How to judge a route before you have seen it, and why corner count matters more than scenery when you cannot read the signs.
Promenade and riverside routes across several cities, measured the same way, with distance, surface and corner count so you can choose before you land.
Tokyo's default running loop is a little over five kilometres with four corners. What the route data says, which way round runners go, and how to use it.
Crissy Field, the Embarcadero waterfront and the Lake Merced loop, with distance, surface and corner count for each, plus what the downtown grid does to a track.
Cadence comes from a step sensor, not from GPS, so a phone in your pocket can count it. How the number is produced, how often it updates, and what it hides.
Two long Manhattan runs, measured: a park loop that closes on itself with almost no corners, and a riverside line. Which suits the run you actually planned.
The Cheonggyecheon stream path and the Gyeongui Line Forest Park, measured. Two paved routes with almost no corners, each reachable from a subway exit.
Hyde Park, the Thames Path at the South Bank and the Tamsin Trail, with measured distance, surface and corner count, and what is spoken at each corner.
A curated route is geometry until something names its corners. How turns are detected from a route shape, what gets announced, and why this is not navigation.
A board that scores heart rate ranks equipment as much as running. The case for scoring only what every entrant can measure, and what that leaves out.
Four ways free running apps make money, the tells in a privacy policy, and the questions to ask before handing an app a year of your location history.
Free means four incompatible things. A dated audit naming the exact feature each app locks, plus a fifth category for apps that have not decided yet.
A Tabata timer counts seconds. A running repetition ends at a distance, and the useful spoken cue is an instruction about what to do next, not a countdown.
A gap in the track is not a gap in the run. What apps do with missing minutes, why an honest distance under counts, and what a coach should say about it.
Underpasses, covered markets and downtown grids each break a track differently. What you see on the map afterwards, and whether the distance runs long or short.
Same route, same phone, two different distances. Sampling, smoothing, discarded points and the way each app handles a gap explain nearly all of the gap.
Some coaching products only work if you own the hardware. An app by app check of what is gated, degraded or advantaged when you run with a phone alone.
Only some losses are recoverable. What Strava documents, what other vendors do not document, and the steps worth trying in the first hour, quoted and dated.
Switch on spoken splits, pick units, decide what happens to your music, and test it before you go. Including the settings some apps deliberately do not offer.
Six unresolved Strava threads and the same five guesses. A diagnosis organised by cause: speech engine, audio focus, background limits and Bluetooth.
Android kills a run tracker to save power, and manufacturer task killers make it worse. Which settings matter, per manufacturer, and what survives the kill.
Runflake is a running app for a phone. What it records, what it speaks, what leaves the device, and where it is available today, stated with a date attached.
Locked screen, phone in a pocket, and the run stops. What iOS actually does to a recording app, the order to check settings in, and what Always is for.
A phone records distance, pace, splits, cadence and route on its own. What that setup covers, what it cannot, and why the phrase without a watch is ambiguous.
Nobody publishes the wording. Here is every line Runflake can speak with its trigger, what Strava and Runna document, and why the wording is fixed.
A run is usually lost at the save step, not while you run. What happens on your phone during a run, what Strava says it cannot restore, and what to check.