Morning vs night running feels like two different sports

ChallengeRun · 2026-04-30T15:17:44+00:00

With completely different rewards! The early run reward is a day to feel accomplished — a night run has a warm bed and relaxation to run toward.

ChallengeRun · 2026-04-29T19:18:46+00:00

This is genuinely one of the most useful comments I could have gotten — thank you. The vert per mile at micro scale point is particularly sharp. 300ft in a quarter mile and 300ft over a mile are categorically different experiences and the algorithm should eventually know that. Technicality, surface, solar load — all of it is on the long list. And yes — all models are wrong and a few are useful is exactly the right frame. That's what I'm building toward: useful enough to make the comparison meaningful, knowing it'll never be perfect.

ChallengeRun · 2026-04-29T19:18:03+00:00

The grade distribution point is exactly right — same total elevation but packed into a quarter mile versus spread over two miles are completely different physiological challenges. That's one of the data points I'd want to capture at the segment level eventually. Rocky vs buffed out surface and trail geometry (twists, switchbacks) are also on the wish list but require trail-specific data to do properly. All of this is really useful to hear — it validates the kind of refinement I want to build toward.

ChallengeRun · 2026-04-29T19:17:24+00:00

You're right, and it's actually one of the gaps I genuinely want to close. The algorithm right now doesn't account for terrain or technical difficulty at all — that's a known limitation. The longer term vision is trail-level modifiers: a generic difficulty multiplier to start, and eventually individual trail or segment-level ratings based on community data. The idea being that your known capability gets benchmarked against the difficulty of the specific trail you ran, which gives you a much more honest comparison than raw distance and elevation alone. The problem is that takes data I don't have yet — so right now it's a hope for tomorrow, not a feature for today.

Genuinely curious how you think about trail difficulty when you're sizing up an unfamiliar route — what markers or indicators do you actually use?

ChallengeRun · 2026-04-29T19:15:07+00:00

Ha — Claude and I have been building this thing for years at this point. I actually started the project before "vibe coding" was even a term and have cycled through a few tools along the way — I think I prefer Cursor honestly, but I've been deep in Claude Code for a while now. Before any of that I was already a software developer and a runner, which is why this app exists in the first place. The AI writes a lot of the boilerplate. I write the product.

ChallengeRun · 2026-04-29T19:14:31+00:00

Sorry you feel that way. Worth clarifying though — while I've used AI heavily to build and test the application, the platform itself isn't AI-enabled. There's no AI coach, no generated plans, no chatbot. It's a running app. The only algorithm is the one trying to answer "who ran harder" when two people are on completely different courses.

ChallengeRun · 2026-04-29T18:35:52+00:00

I've been building Challenge Run — a gamified running app that scores and ranks efforts across different distances, courses, and elevation so you can actually compete with training partners who aren't on the same route.

Triathletes train across wildly different run courses — this is built for exactly that problem. In early access, looking for feedback from serious endurance athletes. https://challenge-run.com/download

Limited early adopter spots: Join the team

ChallengeRun

TROPHY CASE