05 / PROJECT CAPABLE
PRIVATE TESTING
Train wherever.
Keep progressing.
A personal training tracker for a programme that moves between the gym, the van and a park. Follow the rotation, see what happened last time and record what I actually did.
Built with Lovable. Tested between sets. Not just between browser tabs.
THE PROGRAMME
The rotation, programme versions and training environments.
01 / WHY I BUILT IT
The programme came first. Then I built it a home.
Project CAPABLE started as the way I organised my own training. The app is the next experiment: a place to follow the programme and keep the record of what actually happens.
I train while travelling. The location changes. The equipment changes. I wanted the app to make room for that, rather than asking every week to look identical.
THE ROTATION
A sequence, not a timetable.
01 · FORGE
02 · SUMMIT
03 · RECOVERY
04 · HORIZON
05 · POWER
Work through the sessions in order, independently of weekdays. Monday does not get a veto.
01 / GYM
The equipment is here.
The gym version of the session, with the movements prescribed for that setting.
02 / PETAL
Home has a training mode.
The van version, for days when I’m working with the equipment I travel with.
03 / PARK
Outside is part of the plan.
A park version too. Different surroundings, without starting the whole programme again.
02 / INSIDE THE APP
Less remembering. More recording.
What am I doing next? What did I do last time? What did I actually do today? Those are the questions the app is built around.
01 / TRAIN
This session.
See what is prescribed, refer to earlier performance and log the sets as they happen. Add a movement when the session needs one.
02 / LOGBOOK
What actually happened.
The saved workout, including what I really logged. Not a tidier version of what the programme hoped I would do.
03 / PROGRESS
Something to look back at.
Follow recorded performance over time, rather than relying on a vague feeling that I lifted this before.
03 / THE FIRST REAL-WORLD TEST
Added dead hangs.
Skipped calves.
The first real FORGE workout gave the app something more useful than a perfect demo: an actual person doing an actual session.
Logging worked. I added dead hangs. I skipped calves. The programme and the workout were not identical, which is rather the point.
One useful lesson: an optional extra should stay optional. Leaving it out should not make a completed workout look unfinished.
BEHIND THE INTERFACE
Change the programme.
Not the past.
Programme edits create a new version. Workouts keep the version and prescribed plan they started with.
Adding an exercise during a workout is an extra for that session. It does not quietly rewrite the programme.
The plan can evolve. The record of what happened should remain the record of what happened.
04 / WHAT I’M LEARNING
The gym is a very useful place to find a bad button.
This is also a software-building experiment. A screen can look perfectly sensible on a laptop and feel unnecessarily complicated when I’m trying to use it between sets.
The test is whether it helps me train and keep a useful record—not how many features I can fit into it.
Make logging easier.
Notice where a normal session needs too many taps, too much scrolling or too much explanation.
Keep flexibility predictable.
Adding, skipping or changing something should have a clear effect on the workout and its history.
Let real use choose what’s next.
Record what gets in the way. Improve that before inventing another feature.
CURRENTLY / PRIVATE TESTING
One user. Plenty of feedback.
I’m using CAPABLE for my own training and refining it as I go. This page shares the project; the app itself is not a public service.
