What does a food logging app with no data entry screen mean?

What is missing when there is no data entry screen?

The form. In a tracker, a meal is a screen: a search box, a list of entries to pick from, a portion field, a save button, four times a day. In a food logging app with no data entry screen, none of that exists. A meal is a sentence you say to the assistant you already talk to, and the assistant records it through a connection to the app.

That is not a smaller form or a faster one. The search box is gone because there is no database to search: a packaged food is a label you photograph or read out, a plain food you weighed is valued from a reference table by the assistant, and a dish nobody weighed is an estimate that says so. The portion field is gone because the portion is in your words, and when it is not, the assistant asks.

The reason is a cost the trials measured, set out in the 23 minutes article: 23.2 minutes a day in the first month of a 2019 trial, measured from the diary's own logs, and fewer than half still recording after ten weeks in two others. Where those minutes go is what journalers in other studies name: finding the food, picking the entry, setting the portion. That entry is what this design removes.

Where does the meal go if there is no screen?

Into a conversation, and from there into IZeat through a connection. You say the meal to ChatGPT, Claude or any other assistant that can connect to an outside server. The assistant follows IZeat's protocol, asks what your words leave open, and calls IZeat once with the whole meal: each item with its grams, calories, macros and source. IZeat stores it and returns a receipt.

The receipt is the part that makes a conversation trustworthy as a record. It begins with "IZeat ·" and states what was recorded, the meal total, where its figures came from, and, once you have set a target, what is left. Each item keeps its own source in the record, and the assistant can read it back when you ask what a meal contains. The assistant is asked to relay the receipt rather than answer from what it believes it sent, and to keep the "IZeat ·" prefix when it does. The prefix is that convention and not a seal: a reply can lose it and still be IZeat's, and a doubt about the connection is settled by asking "Who am I in IZeat?" rather than by inspecting the wording.

IZeat · Recorded for Friday 11 September 2026 (today): lunch — grilled chicken breast 180 g, steamed sweet potato 80 g, homemade sauce 40 g — 455 kcal · P 58g · C 20g · F 15g (estimated). Total: 455 kcal · P 58g · C 20g · F 15g. Against the target: 1545 kcal remaining · 92g protein remaining.

That is the receipt as the documentation shows it: the meal is marked estimated because the sauce is, and the chicken and the potato are reference values for the grams you gave.

Then the web app. It is read-only: the day as a list with a total, every meal with its numbers, the target and what is left, the week and the history. There is no form for a meal on it, and there will not be one; the only things you change there are your account and your connected assistants: plan, export, deletion, and which assistant may write.

What do you give up, and what do you gain?

You give up two things a tracker has: a database to search and a scanner to aim. You gain a record that costs a description, with a source on each item, kept where you already talk. Whether that trade is right for you depends on what you eat and how you left the last tracker; the table says what changes hands.

The setup is real and worth saying: one connection to your assistant, with one address and one sign-in; then, in the first conversation, your city if IZeat does not know your time zone, your name, and a target if you want one, or "later". None of it blocks a meal. What is gone is the second job; what remains is a sentence per meal and an answer when the assistant asks.

Who does what: the assistant, IZeat, and you?

You say what you ate and answer what a plate cannot show. The assistant understands the sentence, follows IZeat's protocol, asks the questions that protocol names, and reasons the figures. IZeat holds the record, the profile, the targets and the calculations, defines that protocol, and returns the facts the assistant relies on. IZeat proposes no meal; when you ask what to eat, the assistant reads your day from IZeat and answers in its own voice.

That division is what "no data entry screen" costs and buys. It costs a scanner and a database: IZeat has neither, and what replaces them is the assistant reading a label you show, and quoting reference values for a plain food you weighed. It buys a record that says where each item's numbers came from, a label, a reference table, your own figure or an estimate, because the assistant is asked to declare the source of each item and IZeat stores it as declared.

It also buys an assistant that knows your day. Because the record is readable through the same connection, in a new conversation the assistant can read the day or the period from IZeat and answer from it, what is left, what would fit tonight, what the week averaged, rather than reconstruct the totals from messages. The idea is the assistant's; the figures are the record's.

What does a day look like when nothing is typed into a form?

IZeat is the calorie tracker inside ChatGPT, Claude or any other assistant. Tell the assistant you already use what you ate instead of searching for foods and entering them one by one. It is designed so the diary is easier to keep, with nothing to type, while you work toward your goal, and this is what a Tuesday looks like once it is connected.

07:40, in the chat: "Breakfast: 40 g of oats, 200 ml of whole milk, a banana." The assistant records it through IZeat, and the receipt shows the items, the meal total, reference values for the oats and the milk, an estimate for the banana since nobody weighed it, and the day so far. 13:00: "Lunch was 180 g of chicken breast, no oil, 150 g of cooked rice and a 125 g plain yoghurt." Weights for everything, and still a question or two possible: whether the chicken was weighed raw or cooked, and which yoghurt, since a plain one ranges from skimmed to whole; answer, and the receipt shows the three items, the meal total, their sources, and what is left. 18:30, a photo of the dinner plate: the assistant is asked to name the dish and get the portion and the cooking fat before any number; you answer; IZeat records an estimate that says so. 21:00, on the phone, the web app: the day as a list with a total, and nothing to type.

• You never open a form to record a meal. The chat you already have open is the way in; the web app is the way to look.
• You can tell the record from the assistant's opinion. A receipt is written to begin with "IZeat ·" and says what was written; the prefix is a convention rather than a seal, so it settles nothing on its own. A suggestion for dinner records nothing until you say what you ate, and when it follows a signed read of your day, the receipt comes first and the suggestion is set apart from it.
• You know where each item's numbers came from. A label read back to you, a reference table, your own figure or an estimate marked as one, on each item, so a week later the day still says how sure it was.

The limit, plainly: with no entry screen there is also no database and no scanner, today; a packaged food is a label you show, and a dish is described. And the assistant follows a protocol rather than a rule it cannot break: the questions are asked because IZeat's instructions name them, and the record shows what was declared, not what was certified.