Nobody Measures Idli From a Bowl

Schachter sees the same pattern clinically: "Culturally familiar measurements can make logging more intuitive and potentially more accurate. People are much more likely to accurately describe something using the dish or utensil they actually use at home than to mentally convert it into an unfamiliar standardized measurement. A katori or ladle can provide a meaningful visual reference. That said, the most accurate approach is still to provide a consistent reference for the approximate volume or weight associated with that unit" — which is exactly the mapping work behind every unit in Caddy.

That gap between "what people say when given one option" and "what people actually pick when given the real one" is the entire argument for why quantity accuracy matters. It's not a small rounding error. It's the difference between logging what you think you ate and logging what you actually ate.

Five Things a Food-Quantity System Has to Get Right

Human relatability. Nobody thinks in grams while eating. They think in katori, bowl, ladle, spoon, handful. A tracker that only speaks in grams is asking people to translate their own meal in real time, and most people either give up or guess.

Context. The same unit word can mean genuinely different things depending on what's in it and how someone actually uses that word day to day.

Density: volume vs. weight. A container holds a volume. Food has a density. Multiply those together and you get weight — and if you skip that step, every measurement is wrong by however much the food's density differs from whatever the system assumed.

Multiple measure options. Some people think in pieces. Others think in standard servings. A single piece of chicken tikka is a real, common way to log a meal — so is the more typical restaurant serving of 3 pieces at roughly 180g. Offering both isn't redundant, it's meeting two different mental models with the same underlying accuracy.

A precise option for people who want it. Some users genuinely want to enter exact grams — a kitchen scale, a specific recipe, real precision. That option needs to exist alongside the human-relatable ones, not instead of them.

The Same Word Doesn't Mean the Same Amount

This is where most tracking systems quietly break, because they treat units as fixed conversions instead of context-dependent ones.

A cup of tea is roughly 150ml. A cup of milk is roughly 250ml. Same word, same mental image of "a cup," genuinely different amount — because the vessel people actually use for tea isn't the vessel they use for milk, and a system that applies one blanket "cup = X ml" conversion gets one of the two wrong every time.

Density complicates it further. A katori of dal is roughly 120g. The exact same katori filled with bhujiya is closer to 60-80g — because namkeen is largely air and crunch, while dal is dense liquid and lentils. A bowl of curry runs about 180g. A bowl of popcorn is closer to 30g. Same container. Wildly different weight. If a system doesn't separately account for what food is actually sitting in the container, it's applying a single container-to-gram conversion across foods with completely different densities, and the resulting number is wrong by design, not by accident.

You're Not Supposed to Notice Any of This

Here's the part that actually matters to you as someone using the app, not building it: none of the above should ever cross your mind while you're logging a meal.

That's the entire point of doing this work up front. We mapped density, context, and real Indian measurement units — bowl, katori, ladle, the actual spoon that's in your kitchen drawer (not a chef's precise teaspoon or tablespoon, the everyday one somewhere in between), a handful of nuts — so that when you tap "1 katori of dal," the correct number is already sitting behind that tap. You get the option to log a single chicken tikka piece or the standard 3-piece serving, whichever matches how you actually ate, and if you want to skip all of it and enter exact grams, that's there too. The complexity is our job. Your job is just to log what's actually on your plate, in the words you'd naturally use to describe it.

Why This Is the Actual Foundation

A calorie deficit is the mechanism behind weight loss. But a calorie deficit only works if the calories you're counting are close to the calories you actually consumed. Get the quantity wrong consistently — even by "just" choosing bowl instead of katori — and every calculation built on top of that number inherits the error.

Schachter describes exactly how that plays out over time: "A small error repeated consistently can become meaningful. If someone consistently underestimates a portion by 10–15%, that difference is minor on any individual meal but can add up across multiple meals and days. Over several weeks, this can create a substantial gap between someone's logged intake and their actual intake — which can make it harder to understand why their weight, energy levels, or other nutrition goals aren't changing as expected."

Precise data is what makes the number trustworthy. A trustworthy number is what makes someone actually stick to the plan, day after day, instead of quietly losing faith in an app that never quite matched what they felt like they ate. And the plan, in the end, is simple: hit Score 8, and weight loss follows.

About Caddy

Caddy's food database was built from scratch around Indian recipes, ingredients, and the way Indians actually describe their meals — not translated from a generic international template. Bowl, katori, ladle, spoon, handful, piece-or-serving, or exact grams if you want them: whichever way you naturally think about your food, that's the way you can log it, and the accuracy behind it is already handled.

Visit GetCaddy.ai