Why we built a diary instead of a feed

Runflect started as a single HTML file, written for one runner who kept losing track of why a training block had gone the way it did. The splits were all there — every run, every rep, going back years. What was missing was everything around them: the broken night before the session that fell apart, the week the legs came back, the reason a Thursday kept going badly.

Every platform records the run well. None of them record the runner. So you end up with a perfect account of what happened and no account at all of why, and six months later you are guessing.

The splits are the record. How it felt is the story.

So the diary asks one question the watch can’t: how did that feel? One scale, from wrecked to effortless, and room for your own words while it’s still fresh. It lands next to the numbers rather than instead of them, because both halves are needed to read a block properly.

The rest follows from that. There is no feed, because a diary you might be read on is a diary you write differently. There are no kudos and no leaderboard, and there is no score — the product describes the session and lets you judge it. Struggle is never marked in red.

Today it doesn’t leave your own account at all.

Runflect is built in the North East of England. It is in closed beta — accounts are invite-only while we build it out. If you want in, start here.