I have lost count of the number of times I have heard a variation of this conversation.

"I tried that app for a week." "And?" "Couldn't find half the food I was eating." "What about the other half?" "The calorie counts were all over the place." "So you stopped?" "Stopped."

That is the entire arc of nutrition tracking for most people from our community. A week of enthusiastic typing, a slow build-up of frustration, a quiet uninstall. We are not lazy. We are not failing at discipline. We are using tools that were never designed for the food we eat, the way we eat it, or the bodies we have.

In this article I want to walk through, honestly, why the tracking experience has been so broken for South Asians — and what a tracking practice that actually fits our lives can look like. This is not a sales pitch. I will mention DesiPlate at the end because it is what we are building and it is the answer we found after years of frustration, but the bulk of what I want to share is portable. You can apply it whatever tool you eventually use.

The first failure: the database does not know your food

Let me start with the most basic problem.

Open any of the popular trackers and search for "biryani". You will get hundreds of entries with calorie counts that range from three hundred to twelve hundred for a single serving. Search for "dal". You will get an even wider spread. Search for "kottu roti", "puttu", "dhokla", "khichdi", "luchi", "chivda", "ghantachowk", or any of a thousand regional dishes. You will find half-broken entries submitted by random users years ago, sometimes mislabelled, sometimes wildly inaccurate.

This is not an accident of laziness. It is a structural issue. The big nutrition databases were built in the West, with Western dietary patterns in mind, and they have been extended over the years through community submissions. When the community is predominantly Western, the database that emerges reflects Western food. South Asian food enters this database through the side door, in fragmented and inconsistent ways.

The result is that even when you find an entry that looks right, you cannot trust it. You do not know who entered it, what their version of the dish actually was, or how it compares to what is on your plate. The cognitive load of evaluating each entry adds up quickly, and most people give up.

A real desi food database has to be built from the ground up, by people who understand the cuisine, with clear nutritional baselines for each dish, separated by region where it matters, and with adjustment levers for the variables that change a dish significantly — like the cooking fat used or the level of richness. Until you have that, tracking is a guessing game.

The second failure: the units are wrong

The next problem is units of measurement.

A generic app expects you to log food in grams, ounces, or sometimes cups. None of these are units you actually use. You do not weigh your roti. You do not measure your dal in cups. You serve dal in katori, roti in numbers, rice in ladles, ghee in spoons, milk in glasses. Your grandmother does not own a kitchen scale.

When an app asks you to enter your meal in grams, you do one of three things. You guess. You skip the meal. Or you stop using the app.

The fix is conceptually simple and operationally hard. You need a tracker that natively understands the units our food is served in. Katori — and not as a single unit but as a small, medium, or large katori. Roti — and ideally with options for atta roti, parantha, tandoor roti, and naan, each of which has different mass and calorie density. Rice — by katori or ladle, with a sense of whether you mean fluffy basmati or denser short-grain. Ghee — by teaspoon and tablespoon, the way you actually pour it.

This is a database problem and an interface problem. Both have to be solved together.

The third failure: the language is alienating

Here is something subtle that almost nobody talks about.

When a tracker tells you that your meal contains "440 kilocalories with 18 grams of fat, 60 grams of carbohydrates, and 12 grams of protein", that is technically accurate information. It is also, for most people, a wall of numbers that does not connect to any decision they can actually make.

Compare that to a sentence like "your biryani lunch was heavy on carbs — adding a side of raita next time will help your body handle it better." That is the same information, more or less, reframed as an actionable observation in a voice that sounds like a knowledgeable friend rather than a clinical report.

The voice matters. Tone matters. The way the app talks to you matters. Generic trackers tend to speak in the language of restriction and deficit. "You have exceeded your daily calorie limit." "You are below your protein target." This works for some users. For most desi users, in my experience, it produces low-grade shame that builds up and eventually gets uninstalled along with the app.

A tracker that is going to last in your daily life has to speak to you like a culturally fluent friend. It has to know that biryani is celebration food. It has to know that mithai during Diwali is not a moral failure. It has to know that fasting during Navratri is a thing, that Ramadan reshapes the entire daily eating pattern, that the ghee in your nani's recipe is not optional.

If the app does not get this, you will eventually feel the friction and walk away.

The fourth failure: the metrics are wrong for our bodies

This is the one that bothers me most.

Almost every generic tracker shows you the same default metrics. Calories. Protein. Carbs. Fat. Maybe fibre. Sometimes water. That is the average dashboard.

If you are South Asian, these are not the most important metrics on your dashboard. Your most important metrics are probably:

Glycemic load across the day, because of how our bodies handle carbohydrate spikes. Vitamin D intake, because deficiency is endemic in the diaspora. Iron intake, particularly if you are a menstruating woman or a vegetarian. B12 intake, particularly if you are vegetarian. The pattern of when your largest carbohydrate meal lands, because late heavy dinners hit us harder than they hit other populations. Cooking fat quantity, because this is the single largest source of calorie misestimation in our cuisine.

A tracker that does not surface these metrics is showing you the wrong dashboard. It is like driving a car with only a fuel gauge and a speedometer, with no warning lights for anything else. You can drive that car for a long time before you find out what was wrong.

The metrics that matter for our bodies have to be visible. Not buried in an advanced menu. On the home screen, where you check them daily.

The fifth failure: tracking feels like punishment

This is the deepest of the failures and the hardest to fix.

Most tracking experiences are organised around the idea of restriction. You have a daily calorie budget. You spend it. When you spend it, you have to stop. This framing treats food as currency, and your relationship with food as essentially financial.

For many cultures, including ours, food is not currency. Food is family. Food is celebration. Food is grief. Food is identity. The plate of dal-chawal at the end of a hard week is not just fuel — it is a moment of return to something familiar. The plate of biryani at a wedding is not a budget item — it is a participation in a community ritual.

When a tracker reduces all of that to numbers and budgets and limits, it strips out the meaning that makes desi food what it is. People feel the loss without being able to articulate it, and the tracker becomes another thing that asks them to leave a piece of themselves at the door.

A tracker that works for our community has to do the opposite. It has to honour the food. It has to treat your nani's kheer as data, yes, but also as kheer. It has to give you visibility without taking away your identity. It has to coach you toward small, gentle improvements rather than dictating from the top down.

This is more of a philosophical commitment than a technical feature, but it shows up in dozens of small choices. The vocabulary the app uses. Whether it ever uses the word "cheat day". Whether it celebrates birthdays and festivals or flags them as setbacks. Whether it lets you save your mum's recipe by name or forces you to call it "Aloo Gobi Variant 4". These details add up to a feeling of being seen or unseen.

What actually works

So what does a tracking practice that survives the first month and turns into a sustainable habit look like?

Here is what I have seen, in our community, work over and over again.

Start with a single meal a day.* Not all of them. One meal. Pick the meal you eat most consistently — for most people, this is lunch or dinner. Log that meal honestly, including portions and cooking fat, for two weeks. Do not even try to track the rest of your day at the start.

Get the cooking fat right.* This is the single biggest variable in our cuisine, and almost everyone underestimates it. If you do nothing else, learn what a teaspoon of ghee actually looks like in a hot pan. Build a sense of how much your household uses in a dal tadka, in a paratha, in a sabzi. Track that variable accurately and the rest of your calorie estimate becomes meaningful.

Use the units your kitchen uses.* Katori. Roti. Tablespoon. Cup. Not grams. Not ounces. Pick consistent reference sizes for your default katori and your default roti, and stick with them.

Pay attention to one micronutrient at a time.* If you are a vegetarian, start with B12. If you live somewhere with limited sun, start with vitamin D. If you are a menstruating woman, watch your iron. Pick one to begin. Add others later.

Track patterns, not single days.* No single day matters very much. A single splurge on Diwali is not a problem. What matters is what your average week looks like over a month. Look at trends, not individual entries.

Use tracking to learn, not to restrict.* The goal is to understand what your food is actually doing. Not to lose weight by Friday. Not to hit a number on the scale. Once you start to genuinely understand how different foods affect your energy, your sleep, your gut, your skin, your moods — the changes you make become self-motivating. You do not need willpower to do something your own body has told you feels better.

Forgive yourself often.* You will miss days. You will forget meals. You will eat things at family gatherings that you cannot log. That is fine. A tracking practice is not a courtroom. Pick it back up the next day. The goal is patterns over months, not perfection over weeks.

What I have learned over the years

I will close with a few personal observations from years of tracking my own food and watching friends and family attempt the same.

The people I have seen succeed long term are not the ones with the most discipline. They are the ones with the most curiosity. They treat tracking as a way to learn about themselves rather than as a way to control themselves. They get genuinely interested in why a particular meal makes them sleepy, why their energy crashes on certain days, why their gut feels different after certain foods. That curiosity sustains them past the initial novelty.

The people I have seen fail are mostly the ones who tried to track everything, in detail, from day one. They burned out within ten days. Tracking is a habit, and habits build slowly. Start small.

The people who succeeded also tended to have a healthier relationship with food in general. They did not punish themselves for missed days. They did not frame any food as moral or immoral. They built a relationship with the practice that they could carry through holidays, illnesses, busy weeks, and travel without breaking it permanently.

And almost without exception, the ones who stuck with it eventually told me the same thing, in different words. They said that tracking, done right, made them love their food more, not less. Because they finally understood what they were eating. They finally felt in their own body, instead of guessing what was going on inside it.

That is the version of tracking worth pursuing. Not the disciplinarian one. The curious one.

Where we come in

I have spent enough of this article being measured. Let me be direct for a moment.

DesiPlate exists because none of the existing tools did what I have described above for the South Asian body and the South Asian plate. We built a real desi food database, separated by region. We built a katori-and-roti measurement system. We added a ghee adjuster because we know how much it matters. We surface glycemic load, vitamin D, iron, and B12 as default metrics, because those are the metrics our community needs to see. We write in a voice that sounds like a desi friend, not a Western clinic. We celebrate your mum's recipes and your festival meals rather than flagging them.

We are still in beta. We are still building. But everything in this article is what we have tried to bake into the product from the foundation up, and we would rather have a small group of users who feel genuinely understood than a million who feel half-served.

If any of what I have written here resonates with you, come and try the app. Tell us where we are still falling short. We are listening.

Final thought

You deserve a tool that fits your plate, your body, and your life. The fact that the popular trackers do not do this for you is not your failure. It is theirs.

Find the right tool. Build the right habit. Start small. Be curious. Be patient with yourself.

Your nutrition is one of the longest projects you will ever work on. Forty years from now, you will still be eating. The relationship you build with your food in the next twelve months will set the tone for everything that follows.

Begin tonight, with one meal. See what you find.

Frequently Asked Questions

Why do most people quit food tracking within two weeks?

The most common reasons are frustration with the database (cannot find the food you eat), friction with units of measurement (grams and ounces for food you serve in katori), the time cost of logging, and an emotional sense that the app is judging or punishing rather than helping. South Asians experience all of these at higher rates because their cuisine is poorly represented in mainstream trackers.

Is it possible to track South Asian food accurately?

Yes, but you need a tracker built for the cuisine. A real desi tracker has to use katori, roti, and tablespoon as native units, have a database that distinguishes between regional variations, allow you to adjust for cooking fat, and surface the micronutrients that matter most for our bodies.

How long should I track for before I see results?

You will start seeing useful patterns within two weeks. Genuine behavioural change takes longer — typically two to three months of consistent tracking before new habits become stable. The goal early on is not weight loss or any specific outcome. The goal is observation.

Do I have to track every single meal?

No. Start with one meal a day and expand from there. Many people find that tracking lunch and dinner is enough to surface most of their patterns. Snacks and chai are worth adding in once the main meals are habituated, because they are surprisingly significant calorie contributors.

Does tracking lead to eating disorders?

For most people, mindful tracking improves their relationship with food rather than damaging it. However, people with a history of disordered eating, or with current symptoms of an eating disorder, should approach any tracking practice carefully, ideally with the support of a qualified professional. Tracking is not appropriate for everyone, and a healthy relationship with food does not require an app.

What if I cannot find a dish in the database?

A good desi-specific tracker should let you submit missing dishes for review, build custom recipes from ingredients, and save your home recipes to a personal vault for one-tap logging in the future. If your current tracker has none of these options, it is not built for our cuisine.

Should I track calories or other metrics?

Calories are one metric, not the most important one for our community. Glycemic load, fibre, protein, vitamin D, iron, B12, and the timing of your meals are at least as important. A good tracker shows you several of these on the same dashboard so you can see how your day is shaping up across multiple dimensions.

How does DesiPlate compare to generic apps for South Asians?

DesiPlate is built specifically for South Asian cuisine and South Asian bodies. The database is built from the ground up to cover Indian, Pakistani, Sri Lankan, and Bangladeshi dishes. Portions are in katori, roti, and tablespoon. The dashboard surfaces the metrics that matter for our community — including the Diabetes Risk Score, vitamin D, iron, and B12 — rather than burying them. The voice is culturally fluent. Beta users get an extra month of premium access in addition to the standard trial.

Thank you for reading. If this article was useful to you, consider joining the DesiPlate beta. We are building this product with our community, for our community, and we would love to have you with us.