A question before the number is a cost you pay each time#
When you describe a meal, the app answers with a number, not a question. "Pasta with some cheese" comes back as a complete estimate with calories, protein and an item list, and it is already in your log. If the app had to assume something, such as how much cheese or whether the pasta weight means cooked or dry, the assumption is visible and one tap away from being changed. You correct the draft; you do not fill in a form to get one.
That is a deliberate trade. A clarifying question looks harmless once, but a food log is used over and over, for weeks, often by someone standing at a counter or halfway through a meal. Required clarification adds effort whenever it appears. The research on why people stop keeping food records points at exactly that repeated cost, and this post is the case for moving the effort from before the number to after it. The wider argument for keeping a light record at all is in the pillar on mindful eating with numbers.
What people say makes food entry hard#
The clearest map of the problem comes from a study that asked people directly. Cordeiro and colleagues surveyed 141 current and lapsed food journalers, 94 of whom had stopped, and analyzed 5,526 posts from the community forums of three mobile food journals1. Respondents described journaling as "too much effort" (31 people), "time-consuming" (27) and "tedious" (16). A forum post put it plainly: "I hate counting it's tedious but yet very important."
When the authors unpacked that effort, the first barrier they named was knowing what and how much to enter. Participants reported difficulty identifying ingredients, preparation methods and quantities. The counts below are respondents mentioning each theme, and the categories overlap:
| What the log needs | Respondents mentioning it | Example in their words |
|---|---|---|
| The ingredients | 76 | "Not knowing the exact ingredients and portions make the logging difficult" |
| The proportions between them | 11 | "spaghetti: How much meat? How much oil?" |
| How it was prepared | 28 | "did they use oil? Does that affect the calories?" |
| How much was eaten | 40 | "I have a hard time figuring out portions" |
The authors' conclusion is the useful part: uncertainty in any of these undermines the reliability of the entry. A design that stops and asks for them does not remove that uncertainty. It hands it back to the person least equipped to resolve it at that moment, and it does so before they have seen anything in return.
The questions a detailed food log needs answered are the same ones people say they find hard to answer.
Burden is the reason people give for leaving#
Surveys of app users outside the food-journal niche tell the same story at scale. In a national survey of 1,604 US mobile phone owners, 58.2% had downloaded a health-related app, and fitness and nutrition apps were the most common kind. About half of those users, 427 of 934 (45.7%), had stopped using some health apps. Among those who stopped, entry time was the most frequently reported reason (190 of 427), alongside loss of interest and hidden costs2. It is a cross-sectional survey, so it records the reasons people give rather than measuring what caused them to stop. Still, entry burden is one practical design target.
A later systematic review of nutrition-app use pulled together 28 publications and sorted 328 separate barriers and facilitators into a framework3. Usability of the app or its food database appears as its own category, alongside goals, motivation, routines and accuracy. The review's main message is that there is no single fix: people use and abandon these apps for many reasons. That argues for humility about any one design choice, including this one. It does not argue for adding steps.
What these studies do not show is that an estimate-first design keeps people logging longer. None of them tested that. They establish that entry effort is a leading complaint and that the details apps ask for are ones people report difficulty supplying. The design follows from those two facts; whether it changes long-term adherence is an open question. Why people stop in general, and what the ones who keep going do differently, is covered in why people quit calorie tracking.
What happens when you log a meal#
Since July 2026 the app has not asked clarifying questions at all. Here is what you see instead.
A complete estimate, already logged. You type or say the meal and the estimate appears with calories, protein and an item-by-item breakdown. The meal is logged the moment the estimate arrives. The sheet that opens is a receipt, not a confirmation step: it has an Undo if the whole thing was a mistake, and it closes on its own after about 30 seconds, so ignoring it is a valid way to finish.
Assumptions you can see. Each item shows its weight, and a quantity the app had to guess is drawn with a dashed pill, while one you stated is solid. Tap the pill to set the real amount; for foods that come in units, you can change the count ("10 egg whites" to "11") and the grams follow. For foods where cooked and raw weights differ a lot, such as rice, pasta, oats, legumes and meat, a cooked ▾ switch lets you flip the basis in one tap.
A marker when detail is missing. If a meal leaned on an unstated amount of something calorie-dense, it carries a small Missing detail marker. Opening the meal shows what was assumed, such as "guessed 40 g", with a stepper to change it and a Looks right button to accept it. The marker is passive. It never asks you anything; it waits until you look.
A labelled rough guess, not a question. Sometimes a description really is too thin, like "a snack". The app still gives a number, marked Rough guess, with a deliberately wide range. You can add a word or two with Refine… if you care, or leave it. If you prefer entering precise figures for some foods, a Quick add entry where you type the numbers yourself is still there; when each style makes sense is covered in quick-add vs detailed logging.
| An app could ask first | What you get instead |
|---|---|
| "How many grams?" | A likely weight, drawn dashed until you set it |
| "Was that cooked or raw?" | A default basis with a cooked ▾ switch |
| "What was in it?" | An item list you can edit or extend |
| "Can you be more specific?" | A Rough guess with a wider range |
Why we put corrections after the estimate#
Three reasons shaped the choice, and they are about sequence rather than accuracy.
First, a number shown first gives you something to judge. Several of the difficulties in the Cordeiro table involve amounts, and a visible default turns "how much oil?" from an open question into a yes-or-no one: does this look like my plate? Second, the effort becomes optional. Someone who is busy logs the estimate as it is; someone who weighed the rice changes one pill. The log does not wait for the careful version. Third, skipping correction saves effort, but leaves the assumptions unchecked. The displayed range signals uncertainty; it does not guarantee that the estimate covers your meal. Why that range exists at all is the subject of why calorie counts are ranges.
There is a real cost to this approach. A default you never look at can be wrong, and a question would at least have made you think about it. The dashed pills and the Missing detail marker keep that cost visible without turning it back into a question, but they only help if you look. If you know an ingredient or amount is wrong, correct it before relying on the day's total.
FAQ#
Why doesn't my calorie app ask me questions about my meal?#
Because a required question has to be answered before you see anything, and entry time is the most frequently reported reason people give for stopping health apps. The app makes a best guess, logs it, and shows its assumptions so you can change the ones that matter.
What does a dashed portion pill mean?#
The amount was assumed rather than stated. Tap it to set the real quantity; once you do, the pill turns solid and the calories and protein update.
How do I undo an automatically logged meal?#
Tap Undo on the receipt that opens after the estimate. The meal is removed. If you do nothing, the receipt closes itself and the meal stays logged.
What is a rough guess entry?#
An estimate made from a description with very little detail. It still has a number, but its range is wider, and adding a few words with Refine narrows it.
Sources#
- Cordeiro F, Epstein DA, Thomaz E, et al. Barriers and negative nudges: exploring challenges in food journaling. Proc SIGCHI Conf Hum Factor Comput Syst. 2015;2015:1159-1162.
- Krebs P, Duncan DT. Health app use among US mobile phone owners: a national survey. JMIR Mhealth Uhealth. 2015;3(4):e101.
- König LM, Attig C, Franke T, Renner B. Barriers to and facilitators for using nutrition apps: systematic review and conceptual framework. JMIR Mhealth Uhealth. 2021;9(6):e20037.
Source: BurnWeek — "Your first BurnWeek estimate: get a number, then correct it", https://burnweek.fit/blog/why-burnweek-estimates-instead-of-asking/. Licensed CC BY 4.0: free to quote or reuse with a link to this page.
