Photo logging
Log a meal by photographing it
Other trackers make you search a database three times a day.
AIM
Sunday, Sep 13
Chicken burrito bowl — about 650 kcal and 46 g of protein, same build as before.
Chicken burrito bowl
Lunch · 12:00 PM
9 more
- assumed same build as your previous bowl
- no guacamole or sour cream included
Updated that bowl to a double — 1,322 kcal, 100.8 g protein.
The part that kills food diaries
Conventional logging asks three questions per food and gets a shaky answer to each. Which chicken — the database has four hundred, and they differ by sixty calories. How much — you did not weigh it, so you guess, and the guess carries more error than the database choice did. What else is in it — a stir fry with eight ingredients is eight searches, or it is one entry called “stir fry” that is wrong.
Estimates for that loop run between one and three minutes per meal once you count the false starts. People do not abandon it because they stopped caring about their health. They abandon it because it is half an hour a week of data entry.
What you get back
A photo or a sentence returns a full breakdown in seconds. Not one lumped total — an entry per ingredient, each with its own numbers, so a correction to the rice does not require re-entering the chicken.
Underneath it, the assumptions. Assumed oatmeal cooked in water, no added sugar. Assumed the same portions as your earlier bowl. No guacamole or sour cream included. These are not a disclaimer. They are the interface for correcting the estimate: an app that says “661 kcal” and nothing else gives you no way to know whether it counted the sour cream.
If a photo is genuinely unreadable, AIM logs a blank entry and says so rather than guessing a meal. A plausible wrong answer is indistinguishable from a real one — there is a regression test pinning that behavior.
The model doing the work is a frontier one
This is the part that decides whether any of the rest is worth having. AIM runs a frontier multimodal reasoning model — the same class of system used for hard general-purpose work, not a small image classifier trained on a fixed list of dishes and not a lookup against a food database.
It matters because a plate is not a classification problem. Working out that the bowl holds roughly 180 g of rice, that the chicken was grilled rather than fried, and that the sauce is adding more sugar than it looks like, is a judgment call about a specific photograph. A classifier can tell you “burrito bowl”. Getting from there to numbers you would act on takes reasoning.
So the model is given room to think before it answers, rather than being run at the cheapest, fastest setting. That costs a few seconds per meal and buys a breakdown that separates roughly seven components of a plate instead of collapsing it into three coarse rows — which is what makes per-ingredient correction possible at all.
The response shape is generated from the same nutrient registry the app uses, so every nutrient comes back in the same units every time and a reply cannot silently drop a field. The model chooses the numbers; it does not get to choose the format.
Typing works just as well
The camera is the fast path, not the only one. “Chicken burrito bowl”, “two eggs and toast”, “large flat white” — a sentence gets the same treatment as a photograph, which matters for the meals you did not think to photograph until afterwards.
You can also log something you ate yesterday. Say when, and it goes on that day.
Questions
- How accurate is logging food from a photo?
- For calories and macronutrients it lands in the same range as a person estimating portions by hand, and it takes seconds rather than minutes. The printed assumptions tell you which input to correct, and every number is editable. Micronutrient estimates carry more uncertainty, because vitamin and mineral content varies with soil, cultivar, storage and cooking in ways no photograph contains.
- What kind of AI does AIM use to identify food?
- A frontier multimodal reasoning model — the same class of system used for hard general-purpose work — rather than a small image classifier trained on a fixed list of dishes, or a lookup against a food database. It is given room to think before answering rather than run at the cheapest setting, because estimating a portion from a photograph is a judgment call. That costs a few seconds and is what lets it separate a plate into its components instead of returning one coarse total.
- Does it work on home-cooked food?
- Yes — and it is where photo logging helps most, because a home-cooked meal is the case a food database handles worst. AIM breaks the plate into ingredients and estimates each one, rather than forcing it into a single database row.
- Do I need an account to log a meal?
- No. AIM works without an account. Signing in only matters if you want your log on more than one device.
Related features
Read more
A food diary you might actually keep
AIM is free on iPhone. Fourteen nutrients per meal, water counted from food, caps on anything you want to stay under.