Lifestyle · US iPhone listing

ASO Audit: Yuka

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

5/10Fine. A dangerous place to stop.

Yuka knows how to make a red score look alarming. It spends considerably less effort explaining what produced it. The sequence has a sensible scan-to-alternative structure, but colour-coded certainty is carrying too much of the persuasion. The method deserves some screen time.

ASO Audit: Yuka illustration: Food and cosmetic products are split open beside assessment symbols.
Gabriel Machuret in an ASO Guru T-shirt: inspecting the conditions.

Gab’s verdict · 5/10Gabriel Machuret

Editorial illustrationA confident verdict. A remarkably quiet explanation.See the actual listing screenshots ↓
Listing snapshot · what I checked

What I actually checked

One storefront, one language and a dated capture. This is an independent editorial audit, not a client case study.

Store & market
Apple App Store · United States
Language & device
en-US · iPhone
Captured
30 September 2026
Creative reviewed
First 3 still screenshots; video and other devices excluded
Observed app name · 30/30 characters

Yuka - Food & Cosmetic Scanner

Observed subtitle · 29/30 characters

Check What's in Your Products

Gab’s take · Five criteria. Two points each.

Why this gets 5/10

Scanning, inspecting ingredients and exploring alternatives make sense together. The useful sequence earns credit. The explanation behind the rating needs to catch up with the confidence of the rating itself. Repeated green frames and small breakdowns make the score easier to notice than its explanation. I would spend less space declaring products good or bad and more showing how a user inspects the rating. A health-adjacent product needs stronger explanation than a traffic light with excellent confidence.

  1. Reason to care

    1/2

    Scan and compare are understandable; broad health language outruns the explanation.

  2. Product evidence

    1/2

    Scores are shown clearly, but their basis stays outside the main story.

  3. Readable at a glance

    1/2

    Repeated green layouts and dense ingredient details need stronger selective zooms.

  4. A useful sequence

    2/2

    Analysis, ingredient inspection and alternatives form a logical progression.

  5. A reason to choose

    0/2

    Red and green verdicts substitute for visible reasoning behind the recommendation.

0: not earned · 1: useful but incomplete · 2: clearly demonstrated. Judged on the dated opening creative; public metadata provides context. These points assess creative execution, not private conversion or ranking performance. Read the scoring criteria · See all ten verdict levels

Three things worth your attention

The screenshot teardown

Inspect the numbered original, read the problem, then compare the proposed fix. The publisher’s creative stays unchanged.

What the visitor sees → what I’d change

The number wins; the reasoning loses

Look at the original: The captured creative presents the app’s score alongside per-serving values and coloured labels.

Why I’m flagging it: The large verdict is persuasive while the underlying factors shrink into a dense product panel.

Brief this change

Enlarge one rating breakdown and explain its scope in a short, readable headline.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

Fear is doing the heavy lifting

Look at the original: The headline promotes avoiding harmful ingredients, while the interface assigns several risk levels.

Why I’m flagging it: Avoid harmful ingredients is stronger than the explanation supplied by the small risk labels.

Brief this change

Zoom into the ingredient explanation and its information control; review the claim against the actual method.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

A tick is not an argument

Look at the original: The sequence ends by presenting higher-rated alternatives according to the app.

Why I’m flagging it: The alternative grid makes the decision look simple without showing the basis for comparing the pictured records.

Brief this change

Use one accurately matched comparison with its key rating factors visible instead of several miniature verdicts.

See how the proposed sequence fits together ↓
Figure 1. First three still screenshots from the US iPhone listing, captured 30 September 2026. Creative belongs to the app publisher and is reproduced for analysis. Publisher claims inside screenshots are not independently verified.

What I’d put on the table

Proposed copy for discussion. These are not current listing fields or tested winners.

Observed listing

Yuka - Food & Cosmetic Scanner

Check What's in Your Products

Proposed alternative

Yuka - Food & Cosmetic Scanner

Scan products. Explore details

Name 30/30 · Subtitle 30/30 characters
Metadata comparison. A proposed alternative to review against the current listing.

Keep 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.

Gab’s proposed direction

Give each screenshot a job.

Read the sequence from top to bottom on mobile, left to right on desktop. These are message-layout sketches, not screens from Yuka or tested results.

  1. 01Make the benefit clear

    Proposed headline

    Scan a product to see its record

    Illustrative layout · verify the real flow

    Put this in the frame: A verified current barcode match with the exact product and formulation context.

    Why it earns the space: Start with identification before interpretation.

  2. 02Show useful evidence

    Proposed headline

    See how the rating is explained

    Illustrative layout · verify the real flow

    Put this in the frame: The actual breakdown and source or method information, reviewed for accuracy.

    Why it earns the space: Make the basis of the app’s judgement visible.

  3. 03Move the decision forward

    Proposed headline

    Compare the available information

    Illustrative layout · verify the real flow

    Put this in the frame: A comparison with accurate product records and clear rating scope.

    Why it earns the space: Enable an informed comparison without a blanket health or suitability guarantee.

The test: Does explanation-led ingredient wording improve understanding of the app’s ratings while preserving qualified conversion? The sketch gives the designer a direction; the actual product and access conditions decide what can ship.

Want this level of detail for your app?

Bring the listing. I’ll help you decide what to keep, what to fix and what to test.

Talk to Gabriel →
Compare three alternatives

Three alternatives—and what they make clearer

Observed competitor metadata

Open Food Facts - Product Scan ↗

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

Bobby Approved - Food Scanner ↗

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

Olive: Food & Cosmetic Scanner ↗

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.

Competitor comparison. US listing names and subtitles captured 30 September 2026. These are positioning comparisons, not ranking or revenue comparisons.
Keyword ideas and their evidence

The keyword questions I’d investigate

Intent candidates grounded in the listing—not fabricated search-volume or difficulty scores.

food barcode scanner / ingredient checker

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.

cosmetic scanner / skincare ingredients

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.

product ratings / compare alternatives

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.

What the selected reviews tell us

What three reviewers can teach us

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 9388785495

28 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 13197514488

8 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 12395111802

A 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.

What I’d do first

01

The number wins; the reasoning loses

The large verdict is persuasive while the underlying factors shrink into a dense product panel.

Deliverable: Enlarge one rating breakdown and explain its scope in a short, readable headline.

Creative brief and current-product check
02

Fear is doing the heavy lifting

Avoid harmful ingredients is stronger than the explanation supplied by the small risk labels.

Deliverable: Zoom into the supported ingredient explanation and its information control; review the claim against the actual method.

Creative brief and current-product check
03

A tick is not an argument

The alternative grid makes the decision look simple without showing the basis for comparing the pictured records.

Deliverable: Use one accurately matched comparison with its key rating factors visible instead of several miniature verdicts.

Creative brief and current-product check
Open the full test plan

One test worth running

Does explanation-led ingredient wording improve understanding of the app’s ratings while preserving qualified conversion?

Audience
Eligible US English iPhone default-page visitors, with separate research among food-information and cosmetic-information prospects.
Control
The current second-frame headline only after appropriate review substantiates its scope; correct any unsupported claim across variants before establishing a baseline.
Treatment
Change only the second-frame headline to verified ingredient-information wording, keeping the result view, sequence, metadata and other assets fixed after checking accuracy.
Method
Verify the current method and explanation path, then use comprehension research and eligible App Store product page optimization. This tests wording, not nutritional science, ingredient safety or health outcomes.
Primary measure
Platform-reported download conversion for eligible randomized traffic.
Guardrails
Participants should distinguish an app rating from individual medical or allergy advice and know that product details need checking. No conversion result establishes safety or health benefit.
Decision rule
Predefine useful effect, sample requirement and analysis timing from baseline traffic. Keep control if inconclusive; reject a lift caused by stronger mistaken certainty about product suitability.
What could muddy the result
Database updates, product reformulations, method changes, media coverage and the food-versus-cosmetic audience mix may affect results.

Check Apple’s current product page optimization guidance and custom product page guidance before configuring a test. Write your experiment brief.

How the ten-point scale works

So, does their ASO suck?

1–3: thumbs down · 4–6: thumbs up and down · 7–10: thumbs up

  1. 1/10

    Yeah. It really does!

    The basics need a serious rethink.

  2. 2/10

    I hope no agency is getting paid for this.

    Too many obvious things have been left unfinished.

  3. 3/10

    The app deserves better.

    There is a useful product here. The listing needs to show it.

  4. 4/10

    Recognisable. Not convincing.

    Some basics work, but the opening wastes attention and under-explains the benefit.

  5. 5/10Yuka is here

    Fine. A dangerous place to stop.

    There is usable creative here, but too much of the sales argument is left to the visitor.

  6. 6/10

    Useful. Still leaving too much unsaid.

    Real strengths, undermined by meaningful gaps in the opening story or execution.

  7. 7/10

    Good. The product proof earns it.

    A clear, useful demonstration with specific refinements still needed.

  8. 8/10

    Good. Now sweat the details.

    The main promise is clear and supported. Refinement matters more than reinvention.

  9. 9/10

    Whoever did this knows their stuff.

    Clear positioning, thoughtful choices and very few loose ends.

  10. 10/10

    Okay, now you’re showing off.

    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.

Try this on your app · worksheet and assignment

Your ASO assignment

  1. Enlarge one rating breakdown and explain its scope in a short, readable headline.
  2. Zoom into the supported ingredient explanation and its information control; review the claim against the actual method.
  3. Use one accurately matched comparison with its key rating factors visible instead of several miniature verdicts.

What would change my mind?

  • Current food and cosmetic methods, source access and scope limitations.
  • Product identity, formulation updates, missing-record and correction workflows.
  • Baseline conversion and rating-comprehension research.
Sources and capture dates

Sources and scope

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.

Your app. Your priorities.

Get an audit you can actually use.

Send your listing, market and the problem you want to solve. I’ll explain the scope and fee before work starts. Your budget should buy decisions, not a longer PDF.

Apply the method to your app

Build a relevant keyword shortlist, plan your screenshot sequence or get help with the creative decisions.

More app teardowns

Browse the complete app teardown library →

Enough theory. Your app next.

Let’s fix what’s holding your listing back.

Send your app link, target market and the problem. We’ll start there.