The best calorie app for Indian food, assessed

Indian food places requirements on a calorie tracker that most of them were not designed for. Here are the five that matter and how to test for them.

Requirement one: Indian composition data

A roti in a Western database is a wheat flatbread analysed in another country from different flour. Indian atta differs in extraction rate, fibre and moisture. The same applies to pulses, rice varieties, paneer, ghee and every prepared dish.

An app whose entries for Indian foods trace back to IFCT 2017 is describing your food. One using the nearest American equivalent is confidently describing something else — IFCT or USDA: which numbers should you trust.

Test: search "toor dal" and "atta" and see whether the entries cite a source, and which one.

Requirement two: household measures

Nobody weighs dal at the table. An app that only accepts grams asks you to convert a katori into a weight at every meal, which is the step that ends most people's tracking by week two.

What is needed is the ability to define your own units once — "my katori = 180 g", "my roti = 42 g" — and log in them afterwards. That is the household serving principle, and it is what makes tracking calories without a food scale practical.

Test: try to log "one katori of dal" without typing a gram figure.

Requirement three: custom recipes with fat as an ingredient

This is the decisive one for home cooking.

A dal is lentils plus water plus however much oil your household uses, and the oil can change the dish by 40 per cent. No database entry can know that. What a good app can do is let you build the dish once from raw ingredients — including the oil — divide by the servings it produced, and save the result.

After that, "my dal" is one tap and the number came from your kitchen. The method is in how to calculate the calories in a recipe you cooked.

Test: create a recipe with five ingredients including two tablespoons of oil, set the number of servings, and check that the per-serving figure is available as a saved food.

Requirement four: fast entry for repeat meals

Indian households cook from a repertoire of fifteen to twenty-five dishes. Once each has a saved number, logging should be recall rather than search.

Test: log a full day in week one, then again in week two. If it has not dropped under a minute, the app is not learning what you eat.

Requirement five: honest handling of what it cannot know

An app that returns a confident figure for "chicken curry, 1 serving" is claiming knowledge of a recipe it has never seen.

A better design shows the source, distinguishes verified entries from estimates, and pushes you towards calculating your own version of dishes you cook often. That is a design philosophy rather than a feature, and it is visible within a few minutes of use.

What no app can do

Price the dal you made on Tuesday without knowing your oil.

That is not a software limitation to be solved; the information is in your kitchen and not in any database. The best an app can do is make it easy to capture once and reuse — which is exactly what the pot method in how to count calories in home-cooked food describes.

Any product claiming to have solved home-cooked calorie counting without you supplying the recipe is claiming something that is not available.

The ten-minute test

Search dal, roti and one dish you cook weekly. Look at the number of results, whether they cite a source, and whether they state a weight.

Log one katori of dal without typing grams.

Create a custom recipe with oil as an ingredient.

Try to export your data.

If an app passes those four, it will work for Indian food. If it fails the first, nothing else will save it, which is why how to judge a calorie app's food database is the first thing to read before choosing anything.