How much more do I need to eat today.
One number, answered before you have finished looking at your phone.
Calories2,348 / 3,200
Protein123g / 162g
You never open an app to log a meal
Photograph your food the way you already do, and drop it in an album called Food. That is the entire act of logging. A shortcut on your phone reads that album a few times a day and the rows are waiting when you look.
No searching a database for “chicken breast, raw, boneless”. No weighing scale. No barcodes. No streaks, no badges, nothing asking you to come back.
Your photos are never kept
A photo passes through on its way to the model and is gone when the request ends. It is never written to disk, never put in a database, never kept in a log. What remains is one line of text — a dish name, four numbers and a time.
A few hundred bytes a meal. That is the whole of what this knows about you.
Wrong numbers are crossed out, not confirmed
Everything that arrives counts immediately. When something is wrong — a photo of a menu, a plate that was not yours, a portion read too generously — you cross it out and every total recomputes from scratch. You are never asked to confirm something in order to make it correct.
It does not assume you are cutting
Gain, maintain and lose are three equal choices with nothing pre-selected. Being over target is shown the same neutral way whichever direction you are going: good news on a bulk, information on a cut, and never a warning in red.
Protein gets equal billing with calories, because it is the number that actually goes unmet.
What it costs
About a fifth of a cent per photo, paid to the model provider — roughly a quarter a month if you eat five times a day. There is no subscription, because there is nobody to pay.
iPhone only for now — the shortcut that reads your album is an Apple thing.