No shame
A missed day is a missed day, not a failure. The app does not paint it red and does not tell you that you slipped.
A diary that does not lecture
Most food apps either reduce everything to a calorie count or leave you feeling guilty. We are building the third option.
Every number has an origin
Each figure can say where it came from: the packaging, a reference, or an estimate. An estimate calls itself an estimate.
Your kitchen, not someone else database
A home-cooked dish should not be an oddity you have to type in by hand. The reference grows from what people actually eat, not from the shelves of one supermarket.
Faster than eating it
If logging takes more than twenty seconds, the diary is dead. All of the work goes against those seconds.
Where this came from
Calvi began with a plain annoyance: to log an ordinary home-cooked lunch you had to find it in a database where it was either missing or named in someone else words, and then weigh it too. A week of that and everyone gives up.
So we made logging a single sentence and kept the numbers honest: our own layer of home-cooked dishes, an open barcode database for packaged food, and an assistant that only calculates what it is allowed to calculate. The daily target, the allergens and the tokens are worked out by ordinary code covered with tests, and that is not an implementation detail but a promise.