Product

Why we built one app instead of ten

17 July 2026

Open your phone and count. A workout tracker. A calorie counter. Something for running. A sleep or recovery app. Maybe a body-scan gimmick you tried once. A notes app where the real plan actually lives. Somewhere in there, a coach you message on WhatsApp.

Seven apps. None of them are talking to each other.

The gap is the problem

Here’s the thing about that stack: every app is individually fine and collectively useless.

Your workout tracker doesn’t know you slept 6 hours. Your food app doesn’t know you just set a bench PR and need the protein. Your running app doesn’t know your knee has been complaining for two weeks. Each one sees a slice of you and confidently gives advice as if it sees all of it.

So the integration work lands on you. You’re the one who remembers that yesterday was heavy, that you’re under-eating this week, that the “easy” run should actually be easy this time. You become the API between seven apps — and you do that job while tired, busy, and three days behind on logging.

Most people don’t fail at training. They fail at being the integration layer.

One graph of you

We built FableVita the other way around: one log, and everything reads from it.

The set you just finished, the photo of your lunch, the route you ran, last night’s sleep, your cycle, that tweaky knee, your mood on a bad Tuesday — all of it lands in one place. Not seven databases with seven opinions. One graph of you.

That changes what’s possible. When you ask “what should I train tomorrow?”, the answer can actually account for the PR you set yesterday, the fact that recovery looks strong, and the protein you’re short on — because all of those live in the same place. The advice isn’t generic because the context isn’t partial.

Every vertical compounds the next. Nutrition data makes training advice sharper. Sleep data makes both sharper. Route history tells you something food logs can’t. Ten apps can’t do that no matter how good each one is — the value was never in the slices. It was in the connections between them.

What this actually looks like

It means depth, not a dashboard of averages:

• Training with PR tracking, supersets, RPE and rest timers — logged offline, straight from the watch if you want.
• Food by pointing your camera at the plate, against a catalogue of 3 million foods, with targets that adapt to your real metabolism.
• Routes with segments, personal records and your own heatmap — and privacy zones so your home stays off the map.
• Recovery from the wearables you already own, plus the human context (cycle, injuries, mood) that no wrist device can see.
• An AI coach reading all of it, end to end, every day.

None of it is a separate subscription. It’s one app because it’s one you.

The long game

The reason this matters isn’t tidiness. It’s time.

A workout tracker optimises for this session. A one-app graph optimises for the decade — because it can finally see the decade. Training age, not beach season. Not next week’s PR, the years after it.

That’s the bet: consolidation isn’t a feature, it’s the thing that makes everything else possible.

Start training free — no card, no ten-app tax.

← All notes