Yuka Alternative: Why I Stopped Scanning and Started Eating

I used Yuka for nearly a year. I scanned everything. I read the ingredient breakdowns. I stood in supermarket aisles holding two near-identical jars of pasta sauce trying to decide whether 62 out of 100 was acceptable or whether I should put it back.

By the end of that year I knew a lot about additives. I knew which sweeteners were flagged. I knew what dipotassium phosphate was. What I didn't know was what to eat for dinner.

This isn't a Yuka hit piece. The app does something genuinely useful. It taught me and 80 million other people that ingredient labels actually matter. But somewhere in that year I realised I'd built a scanning habit that wasn't helping me eat better. It was helping me avoid worse. Those are different things.

What Yuka does well

Credit where it's due. Yuka has 80 million users for a reason.

The app does one thing better than almost any other consumer tool — it makes ingredient lists legible. Before Yuka, reading a packaging label required either chemistry knowledge or a willingness to Google every preservative on the side of a yoghurt tub. Yuka collapses that into a colour-coded score in three seconds.

For supermarket shopping focused on packaged food, that's genuinely useful. Comparing two breakfast cereals, Yuka tells you which one has more added sugar and which has more concerning additives. That's not nothing. For millions of people Yuka was the first time they actually understood what was in their food.

Where it stops working

The trouble started when I noticed how much of my actual eating happened outside the scenarios Yuka was built for.

Cafes and restaurants. No barcode on a chicken parma. No score for a flat white with oat milk. Most of the meals I actually ate didn't come with a label to scan. Yuka had nothing to say about them.

Home cooking with fresh ingredients. When I made a stir fry from chicken, rice and vegetables, there was nothing to scan. The healthiest meals were invisible to the app. Only packaged shortcuts got rated.

Takeaway. A burrito from the place down the road, a sushi roll from the train station, a kebab on a Friday night. None of it scannable. Yuka couldn't help me make sense of how those meals fit into my day.

Snacks not in the database. Local bakery items, store-brand products, anything that wasn't in their 5-million-product database. The flashlight would beep and tell me "product not found" and I'd be back to squinting at the label myself.

The "bad" rating problem. When something scored poorly, Yuka would tell me to avoid it. Sometimes the alternatives it suggested were impractical — veggie jerky instead of beef jerky, or a brand that wasn't sold near me. The advice was avoidance-flavoured, not actionable.

The deeper realisation

About six months in I started noticing a pattern in my own behaviour. I'd scan something, see a poor rating, feel a small spike of guilt, and either buy it anyway with a worse feeling or put it back and feel virtuous. Either way I was using the app as a judgment tool, not a learning tool.

Industry experts have written about this — the way scanner apps can capitalise on fear to drive engagement, often without the nuance the science actually requires. A product can get a poor score because it contains 138mg of sodium per serving. That doesn't make it bad food. It makes it food with sodium in it, which is most food.

Reducing complex nutritional and cosmetic science into a single score can be misleading. Some users report unnecessary worry over ingredients they don't fully understand. That worry isn't healthy in itself.

I wasn't eating better. I was eating more anxiously.

From scanning to eating

The shift I needed was from product judgment to eating guidance. From "is this okay" to "what should I eat."

Those are different problems and they need different tools. A barcode scanner can answer the first question for packaged foods with a label. But the second question — the one that actually shapes whether you eat well — requires something that knows your whole day, your patterns, your goals, and can talk back to you.

That's why I started building Rekkon.

What a different kind of food app looks like

Rekkon doesn't scan anything. You don't point your phone at a barcode. You just talk to it.

"Had eggs on toast for breakfast." It logs that, works out the rough numbers, remembers it.

Lunchtime, you say "had a chicken wrap and a flat white from the cafe." Same thing. No barcode, no database search, no menu of options to scroll through. Just spoken description, captured in five seconds.

Then you can ask it questions. "I'm going out for drinks tonight, how much room do I have?" It answers based on what you've actually eaten today. "What should I have for dinner that's high in protein?" It gives you a real suggestion, not just a list of brands to avoid.

The coaching is conversational. Some days that means "you're a bit short on protein today, prioritise that at dinner." Other days it means "the weekday eating is solid, the weekends are where the calories are hiding." The kind of thing a knowledgeable friend would say. Not the kind of thing a scanner can say, because a scanner only sees one product at a time.

It even has personality modes. Bogan mode talks to you like a mate at the pub. Posh mode reads back like a maître d'. The voice variety is a small thing but it makes the app feel like a coach rather than a database.

This isn't either-or

You can use Yuka and Rekkon for different things. I still occasionally open Yuka when I'm trying to choose between two packaged products at the supermarket — that's where it's strongest. But the daily question of what to eat, what to log, what to adjust based on how my week is going — that's not a scanning problem.

Yuka taught me that ingredients matter. The next step was learning that ingredients aren't the whole picture, and that the most important food question isn't "what's in this product" but "what should I eat given everything else about today."

That's the question Rekkon was built to answer.

The honest summary

If you spend most of your eating life shopping for packaged products and want to make better choices in the supermarket aisle, Yuka is excellent and you should keep using it.

If you eat at cafes, restaurants, and friends' houses, cook with fresh ingredients, or want guidance about your overall eating rather than verdicts on individual products — that's a different tool. Voice-first nutrition apps like Rekkon are built for exactly that gap.

It's not that scanning is wrong. It's that scanning is one layer of food awareness, and most of us need more than that to actually eat well.

Common questions

What is the best alternative to Yuka?

It depends on what you actually need. Yuka tells you whether a packaged product is healthy or not. If you want a tool that tells you what to eat — not just what to avoid — voice-first nutrition apps like Rekkon work differently. You describe a meal, ask questions, and get coaching based on your specific day. No barcode required.

Is Yuka accurate?

Yuka relies on a combination of manufacturer data and user-submitted information, which means accuracy varies. Multiple reviews note inconsistencies including products getting different scores at different times, missing ingredients, and reformulated products that haven't been updated. Yuka is best used as a directional guide rather than a definitive verdict on any single product.

Why don't food scanner apps tell you what to eat?

Scanner apps are built around packaged products with barcodes. They evaluate items one at a time but cannot assess your overall daily intake, recommend specific meals, or coach you toward better choices in the moment. They answer 'is this product okay' but not the more useful question of 'what should I eat right now given what I've already had today.'