Why this exists
The habit came first. The app is just the part that remembers it.
This did not start as a product idea. It started on 22 August 2026, in the bath, after an upper-body session and a 10K walk, on the fourteenth consecutive gym day. The thing worth noting was not the fourteen. It was that for the first time going felt good rather than forced.
That is a new state, and new states are worth instrumenting before they fade. There is no job at the moment and the runway is tight, and this still reads as the more important thing happening right now.
So Keel is not being built to start a habit. The habit already exists. The data is already being produced every single day. It is just landing in four different apps and in nobody's memory, which means none of it compounds.
One way in.
Many ways out.
Every wellness app dies in the same place: the form. Twelve fields, four dropdowns and a date picker, on a phone, sweaty, at 11pm. Nobody sustains that.
So Keel inverts it. Input is conversation. Say the day the way you would tell a friend, out loud if that is easier, and the app does the structuring. Output is structure. Tabs, charts, streaks, summaries, every one of them a read-only view built from the same log.
The test for every feature that ever gets added: does it give you another thing to fill in, or another thing to see? Filling in needs a very good reason. Seeing does not.
How it actually works
This is the whole product. One paragraph of ordinary speech at the end of a day, resolved into records. Press the button.
I woke up today at 6am. I went to the gym, did upper. Before going to the gym I took creatine and a banana, then came back home, did 10K steps, then took a warm shower, and I had a protein before the walk.
Extracted
Six records are waiting in that paragraph.
Every extracted number keeps the sentence it came from. Tap any record in the real app and the original words light up, exactly like above. Nothing is saved until it has been confirmed on screen. Silent wrong parsing is the one thing that would end the trust, and trust is the entire product.
What goes in
Eleven data types. Each one has a home, a history and a chart.
The screens
What it says back
A summary every night, every week, every month, and every year from the day it starts. What is going right, what is going wrong, in plain words.
Three rules make it worth reading. It has to be specific, so "protein landed at 52g, third day under 80" instead of "try to eat more protein". It gets a maximum of two things to fix, because a list of nine is a list of zero. And it reads the journal first, so a day that was written up as a low day gets a different answer than a day that was not.
Tone is a setting, from gentle to blunt, changeable mid-week. Some weeks need you missed two sessions, go tomorrow. Some weeks need you held the streak through a job hunt, that counts. Same data. The app should not have to guess which one is wanted.
Correlations, sleep against lift performance, protein against mood, stay switched off until there are sixty days of data. Correlations on three weeks are noise wearing the costume of insight, and one confident wrong claim early would poison every true one after it.
The hard part, told straight
Pulling data out of fitness trackers is the part most likely to disappoint, so here it is without optimism. Every line below needs testing before anything is built on it.
| Source | Web app today | Needs a native app | Fallback |
|---|---|---|---|
| Hevy | CSV export, imported by hand | No | Speak it |
| Apple Health | Export zip only, no server API exists | Yes, for live sync | Speak it |
| Health Connect | No. On-device only | Yes | Speak it |
| Weight scale | Manual | Depends on the scale | Type it |
| DEXA | Upload the PDF | No | Type the numbers |
Apple and Google both keep health data on the device on purpose. No website can read it, at any price, which is the real reason a native app eventually exists. Notice that the fallback column is identical on every row. That is not a backup plan, it is the plan, and it is exactly why the talking has to be excellent.
Build order
Each phase has to be usable on its own, and nothing starts until the one before it has been used for real for a week.
Open questions
Parked, not blocking. Answer them whenever.
- Which DEXA clinic, what does it cost, when is it booked? The baseline waits on it.
- Is Hevy Pro worth paying for automatic sync, or is a manual CSV export fine?
- One user forever, or others eventually? It changes auth, schema and legal, and it is far cheaper to decide now than to retrofit.
- Browser speech-to-text, or a paid transcription API? Needs a real test at real speed.
- How blunt should the coach be by default, before the setting gets touched?
- Progress photos daily, weekly, or monthly?
- What is the actual goal? A weight, a lift, a body fat percentage, or just continuing? The summaries need something to measure against, and "keep going" is a legitimate answer if it is the true one.
- Does the streak survive a rest day? Define what breaks it before one breaks by accident.
- Does the app itself appear in the public content, or only the results?
- Run a proper trademark search on the name before anything commercial.