Launching today
Smart Runner
Your training plan, rewritten after every run
44 followers
Your training plan, rewritten after every run
44 followers
Smart Runner builds an adaptive 5K-to-marathon plan from one race result and rebuilds it after every run. Paces come from your VDOT, load tracking is the usual ATL/CTL/TSB, and workouts follow Pfitzinger, Daniels and Canova. Native Apple Watch app with live pace and HR zones. Two things make it different: it's a one-time purchase, not a subscription, and it runs entirely on-device. No account, no server, nothing leaves your phone. 14-day free trial.
Smart Runner
Mailwarm
As someone who trains a lot, I like the “adaptive after every run” angle. Most plans look good on day one, then life happens: fatigue, missed sessions, bad sleep, unexpected pace.
Also, one-time purchase + on-device is refreshing in fitness apps.
Does the plan adapt more based on performance, heart rate/load, or missed workouts?
Smart Runner
@thamibenjelloun
Thanks Thami, you nailed exactly the problem I built it around. Plans that are perfect on paper and fall apart the first time life gets in the way.
Short answer: all three, but load is the backbone. Here's the order of influence:
Training load (ATL/CTL/TSB) is the primary driver. Every run feeds TRIMP into your acute vs chronic load, so the plan reads fatigue and freshness and adjusts volume and intensity before piling on more. This is what catches the bad-sleep, dead-legs weeks.
Performance sets the paces. Your VDOT updates from how you're actually running, so the target zones move with your fitness instead of staying frozen at whatever you entered on day one.
Missed workouts reshape the block. It runs a 2-week rolling plan and rebuilds after every run, so a skipped session gets absorbed into what comes next rather than guilt-tripping you to cram it in.
Heart rate matters mostly through that load calculation rather than as a standalone dial.
Really appreciate you digging in. If you put it through a real week, I'd love to hear where the adaptation feels right and where it doesn't.
Good one! The on-device plus one-time-purchase combo is the part that actually got me. How do you stop a single bad reading from reshaping the whole block? Do you smooth it, flag it for confirmation?
Smart Runner