FitLibre
Your training log, on your device.
Meals, sessions, weight and trends, stored on your phone and fully usable with the wifi off. There is no account to make, no sync you did not ask for, and no server of mine holding any of it. Libre, as in yours.
- Account
- None
- Runs on
- iPhone, iOS 26+
- Network needed
- Never
- Stored
- On your phone
- Export
- Plain files

The next design, working. Tap through it.
This is where FitLibre could go next, built as a live prototype rather than a picture. Everything in it runs in this page, on your device, the way the app does. Log a meal, finish a set, go back to yesterday.
- 01Built to read on a gym floor. Big condensed numbers on dark green, and the next set is one tap above your thumb.
- 02One bar instead of rings. The day's energy is built from its meals, with the target zone marked.
- 03A missed day is just a day. No guilt copy. Copy yesterday's meals across in two taps.
- 04What your assistant writes is marked. Entries from Claude are labelled, logged and can be undone.
What it refuses to do.
Most of the work on FitLibre has been deciding what to leave out. These three came closest to being built, and each one is on the public list with the reason it stopped.
- an account is only useful to the person collecting them
No account
Open the app and start logging. Nothing to sign up for, nothing to verify, nothing to delete later.
- parked deliberately, and not coming back
No feed
No followers, no reactions, no sessions from strangers. The log is for you to read, not to perform.
- the missed day is where most people quit
No streaks
Miss a day and nothing breaks, nothing resets, and nothing tells you off. You can also backfill yesterday in two taps.
Your assistant can plan for it. You decide what lands.
FitLibre writes a prompt from your own plan and log, and you hand it to Claude or ChatGPT: paste it, or send it in one tap with an iOS shortcut. The plan comes back into FitLibre, and nothing is applied until you have read it and said yes. The prompt is the one thing that leaves your phone, and you see every word of it first.
- 01
Build
FitLibre builds the prompt from your plan, your targets and anything you have told it about injuries. You can read it before it goes anywhere.
- 02
Send
Send it by pasting it into the assistant you already use, or add the one-tap shortcut from the Plans screen and it goes and comes back on its own.
- 03
Review
The answer arrives as a plan to review, not as changes to your log. Nothing is written until you apply it.
What this does not do
No assistant can reach into your log on its own, and there is no server of mine in the middle. The prompt goes straight from your phone to the assistant you chose.
A local MCP server, so Claude Desktop could read and write your log from your own computer, is planned and not built. If it ships, it will only ever talk to your own devices, and the app will keep a visible log of everything an assistant wrote.
Where everything lives.
The whole answer, on one screen, because this is the question the app exists to answer.
- Your log
Your phone
meals, sessions, weight, everything you type in
- A prompt you send
Claude or ChatGPT
only when you send it, and you see every word first
- Exports
A folder you pick
dated Markdown and CSV, readable without this app
- My servers
Nothing
no account system, no analytics, no crash reporter