Skip to main content
Back to thoughts

Why calorie tracking apps fail most people

#health#product-design#noted

Most calorie tracking apps are built by fitness enthusiasts for fitness enthusiasts. And that's exactly why they fail everyone else.

I've watched people try MyFitnessPal. I've seen the look on their faces when they search for "chicken breast" and get 47 results. When they have to decide if their portion was 3oz or 4oz. When they give up after three days because logging a single meal took longer than cooking it.

The app didn't fail them. The app was never built for them.

The precision trap

Here's a dirty secret the fitness industry doesn't want you to know: the exact calorie count doesn't matter.

Your body isn't a calculator. It doesn't care whether you ate 1,847 calories or 1,900. The difference between those numbers is literally a few bites of food. The margin of error on any nutrition label is already 20%.

But calorie apps are obsessed with precision. They let you log 0.75 servings. They show you decimal points. They make you feel like you're doing science.

You're not doing science. You're doing busywork.

The guilt machine

Every calorie app I've used has the same dark pattern: the red number.

Go over your daily goal by 50 calories - a single apple - and the number turns red. You've failed. You're in the red. Bad user. Try again tomorrow.

This is psychologically devastating for people who already have a complicated relationship with food. Which, by the way, is most people.

The app designers know this. They keep the red number anyway. Because shame drives engagement. Shame makes you open the app more. Shame is good for metrics.

I find this genuinely disgusting.

What actually works

After years of watching people struggle, I've noticed something: the people who successfully change their eating habits don't track every gram. They track patterns.

"I had a big lunch, so I'll have a lighter dinner."

"I've been eating out a lot this week."

"I haven't had vegetables in three days."

This is how humans actually think about food. Not in grams and percentages. In rough shapes and general directions.

Why we built Noted differently

When I built Noted, I made some choices that would make a traditional product manager nervous:

The barcode trap. We have a barcode scanner, but I almost didn't build it. Why? because relying on barcodes trains you to eat packaged food. The healthiest foods - apples, spinach, steak - don't have barcodes. Use the scanner for convenience, not as a crutch.

No decimal points. You had "some chicken" or "a lot of chicken." That's precise enough.

No red numbers. Ever. Your daily view shows what you ate. Not whether you were good or bad.

No streaks. I'm not going to guilt you into opening my app. If you forget to log for a week, that's fine. Come back when you want to.

Some people will read this and think I'm leaving features on the table. They're right. I am.

Because those features don't help people. They help apps retain users. There's a difference.

The real problem

The calorie tracking industry is worth billions of dollars. It stays that way by keeping people on the hamster wheel. Log more. Track more. Obsess more.

If these apps actually solved the problem, people would stop using them. That's bad for business.

I'd rather build something that works so well you forget it exists. Something you use for a few months, build better habits, and then delete.

That's the goal. That's always been the goal.

An app that wants you to close it.

All thoughts