Why another food app

The log breaks before the intention does

Ask someone why they stopped keeping a food diary and you rarely hear that they stopped caring about how they eat. You hear that logging a sandwich took four decisions, that they got behind and never caught up, or that they opened it one day, saw a number in red, and quietly closed it for good.

All three are design problems, and they share a root: the app can only hold one shape of data — how many calories, yes or no against a target — and almost nothing that actually determines how someone eats fits that shape.

Three things a calorie box can't hold

The context. You ate standing in the kitchen after a difficult phone call. That fact, recorded eleven times, is the most useful thing in your entire history, and there is nowhere to put it — so it's lost every time, and six months later nobody can tell you why some evenings go the way they do.

The meal that didn't happen. A skipped lunch is not an event in any food tracker ever built, because there's nothing to add. Yet across the logs this site is built around, it's the single strongest predictor of a heavy evening, an afternoon craving and a bad night — and it's invisible, everywhere, by construction.

The estimate. When you type "medium portion of rice", an app records a number. A month later that number is indistinguishable from one you weighed, and you're reasoning about your own eating using data you made up. Precision that isn't real is worse than admitted vagueness, because you trust it.

What changed

Language models make an entry cheap enough to actually make. "Leftover curry at my desk, about two, wasn't really hungry" is one action, and it carries the food, the time, the setting and the appetite — four fields that a form would have demanded four decisions for, and that most people would have skipped.

The second thing they change is the reading. Food diaries have always been write-only: you keep one for six weeks, someone glances at it for four minutes, and that's the entire return on the effort. A log you can query is a different object. "Do the weekends actually undo the week?" is a question with a real answer sitting in entries you already made, and until recently getting at it meant a spreadsheet and an evening.

What we're deliberately not building

This is a category with a body count. Food, weight and self-worth are tangled together for an enormous number of people, and the standard mechanics of this industry — streaks, scores, red numbers, clean-eating badges, an AI that tells you your lunch was 640 calories — are not neutral features. They make some people considerably worse, and they do it while showing a chart that says everything is fine.

So: no scores, no streaks, no calorie estimates invented from a photograph, no good and bad foods, no target calculated on your behalf, and nothing that comments on your body. Several pages on this site tell the reader that tracking might be the wrong thing for them and to talk to a clinician instead. Those sentences cost us signups. They stay.

What this actually is

A notebook that can do arithmetic and answer questions about itself. It records what you tell it, counts what's there, and says when there isn't enough to draw a conclusion. Deciding what any of it means is a job for you, and for the people advising you.

It's built by one person, in the open, alongside a handful of other single-purpose apps that work the same way. If it turns out to be useful to you, the fastest way to shape it is to join the waitlist and answer the last question on the form honestly — that box is the reason it's there.