Goals · Eating Regular Meals
The goal underneath most of the others — meals that actually happen
This is the least fashionable goal on the site and the one that turns out to explain the most. Across the other pages here — late-night eating, cravings, the afternoon crash, unplanned evening eating — the strongest single predictor in almost every log is whether lunch happened. Nobody tracks it, because it isn't a diet, it doesn't have a number, and skipping a meal doesn't feel like an event worth recording. It's the cheapest entry you'll ever make and it does more work than anything else in this app.
For anyone whose eating collapses into one large evening because the day got away.
Why this is hard to keep track of
- A meal that didn't happen isn't an event, so nothing anywhere records it
- The cost lands hours later, which is far too long a gap for memory to bridge
- Every tracker records what you ate, and none record what you didn't
- "I'll eat properly tomorrow" is unfalsifiable without a record
Worth recording
- Whether each meal happened. A tick is a complete entry
- Roughly when, since timing matters more than content here
- What got in the way — meetings, travel, no appetite, no time
- What the evening looked like afterwards
Cadence
Three ticks a day at most. The lowest-effort log on the site
What progress looks like
A visible record of which meals happen and which vanish, and a clear view of what a day with all of them does to the evening that follows.
In practice
Say it once, or photograph it
The entries most worth having are the ones made at the exact moment nobody wants to fill in a form. A sentence — typed, dictated, or replaced entirely by a photo of the plate — is a much lower bar, and it carries the context a calorie field would have thrown away.
Called 4 tools
log_meal(meal: "breakfast", happened: false)log_meal(meal: "lunch", happened: false, reason: "meetings")log_meal(items: ["dinner"], at: "19:00")compare_periods(metric: "evening_eating", group_by: "meals_missed")
Every figure here was counted from entries you made. The model chose which tools to call — it doesn't score the meal, estimate calories from a photo, or decide what any of it says about you.
And then ask
The question the log can answer
Months of entries hold real answers to the things you've been guessing at, and reading them properly has always meant a spreadsheet and a free evening — which is exactly what nobody has.
Ask in plain language. The answers come back with the counts behind them, including when those counts are too thin to mean anything yet — which is the more useful answer far more often than people expect.
Called 3 tools
get_history(topic: "regular-meals", window: "6m")find_pattern(group_by: "context")compare_periods(metric: "entries")
Counts and averages over your own entries, nothing more. Where the data is confounded or too thin, the answer says so instead of rounding it into a conclusion.
What it does
Set up around eating regular meals
The same mechanics as everything else here, pointed at what actually matters for this one.
A sentence or a photo per meal
No database lookup and no calorie box. The log that gets kept beats the log that was more precise for eleven days.
Trends, not days
Weight moves a couple of kilos on water alone. Everything here is read as a weekly trend, because the daily number is mostly noise and reads as failure on a perfectly good week.
What the good weeks had in common
The useful question isn't what you ate on Tuesday, it's what was different about the months that went somewhere. That's a query against your own record, and it's the one worth asking.
Your goal, not one we set
We don't calculate a target for you. Any number an app produces here is a population average wearing your name, and it will be wrong by enough to matter.
A bad week is a data point
Nothing resets and nothing is undone. A week off is information about what makes a week hard, which is considerably more useful than a broken chain.
Exportable from day one
Everything you've logged, photos included, out in a file you can take to a dietitian, a GP, or somewhere else entirely.
The reason a lot of people start
Something to actually bring to the appointment
You get fifteen minutes, and the first question is always some version of "so what does a normal week look like?" — which nobody on earth can answer accurately from memory.
What this gives you: The pattern behind most of the other things you'd raise, which is why it's usually the first thing you'll be asked about.
- Export the date range you were asked about, as a file you can print
- Photos alongside the entries, which say more than any description
- Counts and timings rather than an impression of the worst week
- Nothing shared anywhere unless you choose to share it
What it won't do
- Score a meal, or sort food into good and bad
- Estimate calories from a photo and present the guess as a number
- Set you a calorie target, a macro target, or a weight
- Run a streak you can break, or tell you that you've fallen behind
- Comment on your body. The photos here are of food
- Diagnose anything, or suggest that a pattern is a diagnosis
It's a notebook that can do arithmetic and answer questions about itself. Deciding what any of it means is a job for you and the people advising you.
Early access
Start with what you're already trying to hold in your head
Tell us what you've been trying to keep track of and we'll set it up with you — recording the thing that's actually useful, at a cadence that survives a bad week.
- Founding accounts lock their price for life
- No card, no trial clock, no notification designed to make you feel behind
- Export everything you've logged, photos included, whenever you want
Also here
The rest of the picture
These overlap constantly, which is the point — the answer to a question about one of them is very often sitting in another one's data.
Losing Weight
A line per meal when you can manage it, and a weigh-in when you want one
Keeping Weight Steady
Much lighter than you're used to. A few entries a week is plenty
Gaining Weight
A tick per meal. The detail is optional, the meal isn't
Eating More Protein
A sentence per meal. No weighing, no packets
Eating More Vegetables
Part of the meal sentence. Nothing extra to do
Cutting Ultra-Processed Food
A sentence a meal. The categorising is not your job
Steadier Energy
Meals plus one number in the afternoon
Keep the record without it becoming another job
Founding pricing is locked for accounts opened during early access.
Founding accounts lock their price for life. No card required.