Built for one runner first.

My wife runs almost every day. Rain, heat, exhaustion, doesn't matter. Discipline was never her problem.

Meaning was. She'd finish a run and her app would tell her "Good job. Here's a number." And she'd think, so what? Then she told me she wished running felt more like an adventure.

I'm a builder, so I disappeared for two weeks to build something for her. But I built the wrong thing. Dashboards. Leaderboards. Achievement badges. An XP system. I demoed it proudly, and she watched politely, and then she said: "That's really cool. But it's not what I meant."

All I had done was add more numbers. She wanted her miles to mean something beyond the number. So I deleted the whole thing and started over with one question: what did she actually need?

This is the answer. You pick a road: a real one like the Boston Marathon, a legendary one like the walk to Rivendell, or one you invent. You lay milestones along it. Every time you run, walk, bike, or swim, you log your miles and your marker moves down the route. One morning you open the app and you've reached Bree, and you earned that with your effort, one run at a time.

Data can tell you what you did. It can't tell you why it mattered. Story does that.

Runquesting is free, built and run by one person. If you find a bug or a road you wish existed, tell me (opens in new tab).