How to count calories without scanning barcodes

Barcode scanning sounds like the fastest way to count calories. Point, beep, done. In practice it only covers the food that comes in a packet, and even then there's a serving size to pick and adjust. Most of what people eat in a day has no barcode at all: the eggs, the fruit, the takeaway, last night's leftovers. This guide covers how to count calories without scanning anything, what to write so the numbers are useful, and the trade-offs to know about.

Why barcode scanning feels slower than it should

A typical scan-and-search flow goes something like this:

Find the packet (or fish it out of the bin).
Scan it, or search when the scan fails.
Pick from several near-identical results.
Change the serving size from "1 container" to what you actually ate.
Repeat for every item in the meal.

That's fine for a protein bar. It falls apart for a home-cooked dinner, a restaurant meal, or a plate where the main ingredient came loose from a bag of rice three days ago. Many people stop logging not because they lose interest, but because the logging takes longer than the meal.

The easiest way to count calories: say what you ate

The alternative is to describe the food in plain words, one line per item, the way you'd tell a friend:

2 eggs scrambled in butter
a bowl of tonkotsu ramen
half a croissant
chicken caesar salad from the work canteen

A calorie tracker without scanning reads each line and estimates calories and macros. You skip the search results, the serving-size picker and the packet hunt. In Ramen, most answers arrive in about 2 seconds, and things you've logged before come back instantly.

What a typed calorie counter app needs to handle

Typing only works if the app understands how people actually write. Here's what to look for, and what Ramen handles:

Typos. "Brocoli" should still be broccoli.
Full sentences. "Had a couple of slices of pizza at Sam's" is a perfectly good entry.
Brands and chain items, by name.
Household amounts. "A bowl", "2 slices", "a big handful".
Other languages, for the dishes you'd never translate.
Your words left alone. Ramen never rewrites, reorders or corrects what you typed. Your journal reads the way you wrote it.

How to write lines that give useful estimates

A few habits make a big difference to the numbers you get back.

Say how much

Use whatever unit you have. Grams if you weighed it, a count if you can ("3 dumplings"), a household amount if not ("half a plate"). Leaving the amount out is the most common reason for a vague estimate.

Say how it was cooked

"Fried", "in butter", "with olive oil" and "creamy" all add calories that are easy to forget. Mentioning them is the cheapest improvement you can make to any calorie log.

Use the label when you have it

You don't need a barcode to use a nutrition label. If the packet says 210 calories, type it: protein bar 210. Ramen uses your number instead of estimating one. The same goes for menus that list calories, like latte 190.

Make repeats take one word

Barcode apps often win on repeats, because "recent foods" is one tap. A typed log can be just as quick:

same as yesterday brings back yesterday's version instantly.
Saved meals with @. Tap a meal's total to save it, or accept the offer after you've logged it three times. Type @ to bring it back.
Recipes. List the ingredients once, set the servings, and log a portion each time you eat it.
Widgets and Siri. Home and lock screen widgets, plus "Log food" with Siri, so you can add a line without opening the app.

The honest trade-offs

Counting calories from typed lines gives you estimates, and we think it's worth being clear about that.

Estimates, not lab values. Every number in Ramen is an estimate. When it's less sure, you'll see a "~" next to it.
You can check the working. Tap any number for a plain-language explanation of how it was worked out. If it assumed a smaller bowl than you had, add that to your line.
Detail helps. "Pasta" gets a looser number than "a big bowl of pasta with pesto".

For a sense of how close the estimates get: in our own test of 81 typed meals, 92% of calorie estimates landed within 20% of the reference value. They're still estimates, and the "~" is there for the lines where we're less sure.

Other things a good calorie counter app should do

Beyond logging, a few features make an app easier to live with over months:

Targets that fit you. Ramen works out calorie and macro targets from your goal, body and activity, then lets you look back with a calendar, insights and search.
Apple Health, both ways. Ramen reads weight, height and activity, and writes calories and macros back to Health.
Works offline. The journal lives on your phone. Numbers fill in when you're back online.
Private by design. A lookup sends only the food line, with no email attached.
No guilt. No red numbers, no streaks, no "you blew it" messages.
You can leave. Export everything, or delete your account and the data is erased.

Try it without the scanner

You can test the idea today. For one day, skip the barcode scanner and write every meal as a single line in your Notes app, with the amount and how it was cooked. If that's easier than scanning, Ramen does the same thing with calories and macros beside each line. It's coming soon to iPhone at $9.99 a month, or $39.99 for the first year and $59.99 a year after that. People on the waitlist get the $39.99 first year. Join the waitlist and we'll email you once when it's out.