Calorie Tracker Where You Type What You Ate

Some calorie trackers let you log a meal by typing it the way you would text a friend: "2 eggs, avocado toast and a large latte". The app splits that into separate foods, reads the amounts, and gives you calories, protein, carbs and fat for each. No searching a database, no scrolling through twelve near-identical entries for "toast".

We built Silent around this, so here is how it works, when it is the fastest way to log, and when it is not.

How it works in Silent

When you type a meal, Silent splits it on commas and joining words like "and" and "with", but not inside dish names such as "mac and cheese". It reads each amount (a number, or a unit like cup, slice, tablespoon, grams or ounces) and matches the food against a table of about 200 common foods built from USDA values.

Anything the table does not know goes to Apple Intelligence, running on the iPhone, for an estimate. Those items are marked as estimates, so you know which numbers to double-check. You look over the list, change anything that is off, and log it: three taps plus the typing. Nothing is sent to a server, and it works without a connection.

When typing beats scanning

• Mixed meals. A plate of chicken, rice, beans and salsa is one line of typing, or four searches in a database app.
• Home cooking and restaurants. There is no barcode on a bowl of pasta.
• Repeat meals. Once you have logged something, Silent keeps it in "Log again" and saved meals, which is faster than typing or scanning.

And when it does not: packaged food. A barcode scanner reads the exact label of a protein bar, and typing only gets you the average for that kind of food. Silent has no barcode scanner. If most of what you eat comes in a wrapper, an app with one will be faster and more precise for you.

How to word a meal so the numbers come out right

• Give amounts. "150 g chicken breast" or "1 cup rice" beats "chicken and rice". Without an amount, Silent uses a typical serving.
• Use size words. "large latte" and "small banana" change the numbers.
• Name the cooking fat. "eggs fried in 1 tbsp butter" adds about 100 calories that "eggs" alone would miss. Oil and butter are where logs most often come up short.
• Split dishes you know. If you made the stir-fry, typing its parts is more accurate than asking for an estimate of "stir-fry".
• Check anything marked as an estimate. That is the one number worth a second look.

How accurate is it?

Every method is an estimate. Label values are averages, database entries vary, and photos guess at portions. The biggest error in almost any food log is portion size, which is why a week of weighing your usual foods helps more than any logging method. After that, the weekly average is what matters, not a perfect Tuesday. More on that in how to count macros.

Which apps can do this

• Silent, iPhone. Typing, on-device, offline. Free to try for 7 days, then $9.99 once.
• MacroFactor, iPhone and Android. Describe a meal in text or voice, alongside search, barcode, label and photo logging. Subscription.
• Cloud AI trackers. Many newer apps accept typed or spoken meals and send them to a server model. Check the App Store privacy label before you trust one with your food log.

If you want to compare the bigger apps on price and privacy too, the comparison page puts them side by side, and why Silent costs $9.99 once explains the price.

Sources

• USDA FoodData Central. Butter, salted: 717 calories per 100 g, and 14.2 g per tablespoon, about 102 calories.
• Lichtman SW et al. Discrepancy between self-reported and actual caloric intake and exercise in obese subjects. New England Journal of Medicine, 1992.

Questions