Lifestyle · US iPhone listing
My take: Getting there. Keep going.
Yuka’s opening makes its scan-and-rate model very clear: a food score, a cosmetic ingredient list and alternative products. The colours and labels are decisive. The important next step is helping a visitor understand what those ratings mean and how to inspect their basis. I would test explanation-led wording while keeping product ratings distinct from individual health advice.
Actual listing creative · App Store source ↗
One storefront, one language and a dated capture. This is an independent editorial audit, not a client case study.
Open the source listing ↗. Public text cannot reveal the private keyword field, search volumes, rankings or conversion rates. The recommendations below are proposals to validate.
What I saw. The first frame shows a named cereal, a low numerical score and a breakdown of additives and nutrients.
My read. A crisp score is easy to scan but can be mistaken for a complete judgement of a person’s diet or suitability.
What I’d do. Verify the current scoring explanation and test wording that invites inspection of the breakdown.
What I saw. The second frame lists ingredients with risk labels and information icons beneath a harmful-ingredients headline.
My read. The information controls are useful, but the headline foregrounds avoidance before the visitor sees how the classifications are derived.
What I’d do. Verify the method and source path, and make clear that the audit is reporting app classifications rather than independently assessing ingredients.
What I saw. The third frame pairs products with crosses, ticks and contrasting rating labels.
My read. The visual makes substitution feel simple, while formulation, preferences, availability and personal suitability remain outside the still.
What I’d do. Check current comparison criteria and avoid treating a higher app score as a universal recommendation for every person.
The original creative is preserved. Numbered notes sit beside each frame so observations and recommendations stay separate.
It demonstrates a result format, not independent evidence that the displayed product data or health interpretation is current or individually appropriate.
Test idea: Verify the current record and scoring explanation before reuse and show where the user can inspect the basis.
Original image source ↗
These are publisher classifications. The image alone cannot validate the evidence, exposure assumptions or suitability for a particular person.
Test idea: Check the current explanation and sources and compare wording centred on reviewing ingredients.
Original image source ↗
A visual swap can imply broader certainty than a score comparison supports. No independent recommendation of these products is made here.
Test idea: Verify product records and comparison scope, and distinguish app rating from personalised suitability.
Original image source ↗Observed competitor metadata
Food, Cosmetics & much more
Open Food Facts names product scanning across food, cosmetics and more.
The lesson: The scan-and-information job overlaps. Compare what the listing explains about product data without assuming identical scoring methods or database quality.
Observed competitor metadata
Scan labels, find healthy food
Bobby Approved names food scanning and finding healthy food.
The lesson: This is direct food-scanner intent, but the health wording is a publisher claim, not an independently validated comparison with Yuka.
Observed competitor metadata
Scan & Eat Healthy Ingredients
Olive names food and cosmetic scanning with healthy-ingredient language.
The lesson: The scope overlaps both product types. A useful distinction is how clearly Yuka explains its own rating basis; shared vocabulary does not establish equivalent evidence.
Intent candidates grounded in the listing—not fabricated search-volume or difficulty scores.
Visitor’s job: Identify a product and inspect its listed information.
Evidence: The name names scanning and the first frame shows a food result with a breakdown.
Decision: Keep the concrete information task and verify barcode matching, formulation and correction processes.
Visitor’s job: Look up a personal-care product and inspect ingredient information.
Evidence: The second screenshot shows a cosmetic result and ingredient information controls.
Decision: Use accurate product-information language without equating a score with diagnosis, allergy safety or a personalised skincare recommendation.
Visitor’s job: Understand why products receive different app ratings.
Evidence: The third frame explicitly compares alternatives with contrasting labels.
Decision: Research comprehension of the rating method and comparison scope; do not infer search demand or individual health benefit.
The unseen keyword field may already cover some of these terms. Build an evidence-backed keyword shortlist before making a metadata change.
Proposed copy for discussion. These are not current listing fields or tested winners.
Observed listing
Check What's in Your Products
Proposed alternative
Scan products. Explore details
Name 30/30 · Subtitle 30/30 charactersKeep the observed category-rich name and describe the information workflow. The proposed subtitle encourages the user to inspect details rather than treating the first score as the whole decision.
The tradeoff: It replaces the broader check-what-is-in-your-products promise and does not advertise alternatives. Its usefulness depends on the current detail flow and audience understanding, not on a presumed ranking advantage.
Show: A verified current barcode match with the exact product and formulation context.
Start with identification before interpretation.
Show: The actual supported breakdown and source or method information, reviewed for accuracy.
Make the basis of the app’s judgement visible.
Show: A supported comparison with accurate product records and clear rating scope.
Enable an informed comparison without a blanket health or suitability guarantee.
Three 2022–2025 accounts were selected for information access, search and correction expectations. They are not a health-outcome study or database-accuracy sample. The corrected record remains explicit; individual ingredient conclusions, allergy assumptions and historical subscription details are not adopted as current verified facts.
Sample: 3 selected accounts from 8 displayed reviews. Dates: 12 December 2022–28 September 2025. No sentiment percentage is calculated.
12 December 2022 · 5/5 stars
“list out the ingredients”
A December 2022 reviewer valued accessing ingredient explanations while shopping.
What I’d investigate: Use the information-access motivation, not the account’s personal health or safety conclusions, as research evidence.
Listing review source · Review ID 938878549528 September 2025 · 5/5 stars
“scan and search”
A September 2025 reviewer liked scanning, searching and finding alternatives, and described submitting missing-product information.
What I’d investigate: Verify current access and review procedures; the account does not establish current pricing, database completeness or comparison quality.
Listing review source · Review ID 131975144888 March 2025 · 4/5 stars
“they fixed it”
A March 2025 reviewer described a product-data concern that they reported and said was corrected, alongside concerns about gluten-related feature access.
What I’d investigate: Preserve the correction. Do not treat a product score as an allergy or cross-contact guarantee, or adopt the reviewer’s ingredient allegations as verified facts.
Listing review source · Review ID 12395111802A displayed review can be old, unusually positive or internally inconsistent with its star rating. These accounts suggest questions; they do not establish current defects or typical customer experience. Use the Review Research Desk to keep evidence and interpretation separate.
The strongest creative signals are numerical and categorical verdicts.
Deliverable: A verified method-and-source walkthrough for the pictured examples.
Required editorial and product reviewInformation controls are present but secondary to avoidance language.
Deliverable: An explanation-led second-frame wording variant.
Low creative effortSelected accounts describe missing records and corrections.
Deliverable: A current barcode, formulation and correction-process source sheet.
Product researchDoes explanation-led ingredient wording improve understanding of the app’s ratings while preserving qualified conversion?
Check Apple’s current product page optimization guidance and custom product page guidance before configuring a test. Write your experiment brief.
Getting there. The category and first action are immediately understandable. The opportunity is to give the scoring method and its limits the same prominence as the red and green verdicts. This audit describes the publisher’s displayed ratings; it does not independently validate the pictured ingredient classifications, recommend the alternatives or establish health outcomes.
The basics need a serious rethink.
Too many obvious things have been left unfinished.
There is a useful product here. The listing needs to show it.
The essentials are there, but there is little to get excited about.
Good ideas, with a few important gaps still to close.
A strong foundation. Look for specific improvements, not a complete restart.
Clear positioning, thoughtful choices and very few loose ends.
An unusually clear, convincing storefront worth learning from.
An editorial verdict on the captured storefront, not a measured ASO score or an assessment of an agency’s private work.
No private analytics, search-rank dataset or internal keyword field was supplied. Review quotations are short excerpts; explanations are our summaries. App names and screenshots belong to their respective owners. We are not affiliated with Yuka. Read our editorial methodology.
Bring your listing and the evidence behind it. We can turn a public critique into a prioritized plan for your actual audience.
See what an ASO audit includes →
