The problem is real, but the product framing is too weak to pull users on its own.
Getting only 4 users in 5 days does not mean people do not care about sugar. It more likely means a standalone "scan sugar in food" app is too narrow, too easy to substitute, and too trust-sensitive to spread without a sharper wedge or much stronger distribution.
CDC data shows the underlying health problem is large: adult men average 19 teaspoons of added sugar per day, adult women 15, and 3 in 5 Americans over age 2 consume more than the recommended amount. So the market does have awareness and need.
The catch is that consumers usually do not shop for a sugar-only answer. They shop for a broader decision: "is this product good for me?" Yuka's positioning captures that broader job. Its site says it analyzes overall product health impact, has more than 83.6 million users, a 4.8 out of 5 rating from 500,000 reviews, and says 95% of users report eating healthier. That is a strong signal that the winning product is not a sugar scanner but a trusted general scanner with sugar as one dimension.
Open Food Facts points to the second structural problem: data depth. It reports 100,000+ contributors, 4,000,000+ products, and coverage across 150 countries. That means users already have access to a giant barcode-and-nutrition substrate. A new entrant has to beat not just incumbents' UI, but their product database, barcode coverage, and comparison workflows.
There is also a trust problem. Yuka does not just sell convenience; it sells credibility. Its independence page emphasizes no ads, no brand influence, no sale of user data, and publicly visible funding from users rather than brands. In food scoring, trust is part of the product. If your app only says "this has X grams of sugar" without a clearly credible framework, users can get that from the nutrition label or from existing apps. If it gives stronger judgments, users will ask why they should believe you.
Finally, the existence of How Much Sugar? is revealing. It is a sugar-focused experience, but it is framed as an educational game built on top of Open Food Facts data, not as a dominant standalone consumer business. That suggests sugar can be a good hook for education, content, or acquisition, but not necessarily a complete app category by itself.
The value proposition is too narrow. People worry about sugar, but at the moment of purchase they usually want an overall recommendation, a healthier substitute, or a broader diet tool. "Sugar only" is often not enough to justify another app.
Users do not yet trust the verdict. Nutrition products need authority. Without obvious data depth, methodology, and credibility signals, a new scanner feels interchangeable or risky.
The category is already crowded at the broad layer. Users can already get barcode scanning, nutrition labels, and healthier-product recommendations from better-known apps and open databases.
This is a habit product, so distribution matters more than launch day novelty. Scan apps win when users repeatedly encounter them while shopping. Four users in five days often means the acquisition loop is not there yet, not that the code is broken.
The target user may be too generic. "People who want less sugar" is a broad concern, but not a sharp buyer segment. The app likely needs a more acute user: parents buying kids' snacks, prediabetics, diabetics, weight-loss users, or people managing cravings.
Do not sell "scan sugar." Sell a sharper outcome:
Sugar should probably be the hook, not the whole product. Add:
You likely need to be explicit about:
Before rebuilding features, test whether anyone will actually pull this into a shopping habit:
Do not interpret the first 5 days as proof that sugar is unimportant. Interpret it as proof that "standalone sugar scanner" is a weak package.
The strongest next move is to narrow the audience and broaden the outcome: pick one high-pain segment, keep sugar as the entry point, and turn the app into a trusted recommendation tool rather than a single-metric scanner. If you cannot find a segment that urgently wants repeated in-store help, this is more likely to work as a content-led or educational feature than as a standalone consumer app.
Auto-scored: SKIP recommendation based on keyword analysis (avg: 3.2/10)