Food & lifestyle · US iPhone listing

ASO Audit: Tasty

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

4/10Recognisable. Not convincing.

Tasty shows recipes, community posts and a recipe introduction. The cooking is apparently happening elsewhere. A food app needs to sell more than an excellent scrolling session.

ASO Audit: Tasty illustration: Cooking utensils connect ingredients to a finished meal.
Gabriel Machuret wearing an ASO Guru T-shirt: checking a mobile app.

Gab’s verdict · 4/10Gabriel Machuret

Editorial illustrationThree screenshots. Nobody has started cooking.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

Tasty: Recipes, Cooking Videos

Observed subtitle · 24/30 characters

Meal Planner & Cook Book

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

Why this gets 4/10

The food looks appealing and browsing is recognisable. For a recipe app, that is useful persuasion. The missing part is helping somebody picture themselves actually cooking one of those dishes. Shorten the captions, vary the crops and show one instruction being followed. Give the community a supporting role instead of using two early frames to avoid demonstrating the cooking experience.

  1. Reason to care

    1/2

    Food discovery and recipe breadth give a relevant cooking proposition. A specific meal or cooking benefit would make the opening stronger.

  2. Product evidence

    1/2

    Browsing is visible; following a cooking step is not.

  3. Readable at a glance

    1/2

    Similar layouts and small headings flatten the visual rhythm.

  4. A useful sequence

    1/2

    Two community-led frames delay the actual cooking experience.

  5. A reason to choose

    0/2

    Catalogue size and ratings offer little distinctive cooking proof.

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

Quantity is the easy claim

Look at the original: The discovery screen supports browsing and saving recipes across several collections.

Why I’m flagging it: A grid and catalogue count leave the practical cooking advantage vague.

Brief this change

Lead with one dish and a specific, way the app helps prepare it.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

Another feed postpones the payoff

Look at the original: A community member’s post includes a warm-place dough tip and engagement controls.

Why I’m flagging it: The community post adds inspiration before any instruction has been shown.

Brief this change

Replace this position with a readable recipe step and its useful cooking context.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The video is still a thumbnail

Look at the original: The still presents the recipe introduction and video preview rather than a step in progress.

Why I’m flagging it: A play button and recipe rating do not demonstrate the instruction.

Brief this change

Show a genuine step with readable timing or quantities; keep verified ratings secondary.

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

Tasty: Recipes, Cooking Videos

Meal Planner & Cook Book

Proposed alternative

Tasty: Recipes & Cooking

Video steps & meal ideas

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

Keep recipes and cooking explicit while giving the subtitle a concrete video-instruction promise. The proposal connects discovery to the task the current third frame only previews.

The tradeoff: Meal-planner and cookbook wording lose prominence, and cooking videos moves out of the name. Research actual query coverage and verify the instruction experience before accepting that tradeoff.

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 Tasty or tested results.

  1. 01Make the benefit clear

    Proposed headline

    Choose something to cook

    Illustrative layout · verify the real flow

    Put this in the frame: A current recipe discovery view with one representative dish selected.

    Why it earns the space: Give the visitor a manageable starting point.

  2. 02Show useful evidence

    Proposed headline

    See what you will need

    Illustrative layout · verify the real flow

    Put this in the frame: The same recipe’s verified ingredients, servings and time context.

    Why it earns the space: Help the cook assess effort before starting.

  3. 03Move the decision forward

    Proposed headline

    Follow the next step

    Illustrative layout · verify the real flow

    Put this in the frame: An authentic instruction with a useful visual texture or preparation cue.

    Why it earns the space: Demonstrate the value of the video and step-by-step mode.

The test: Does an instruction-led third frame improve cooking-task comprehension and qualified acquisition? 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

Mealime Meal Plans & Recipes ↗

Meal Planner & Grocery List

Mealime combines meal plans and recipes with a grocery-list subtitle.

The lesson: Tasty can foreground cooking instruction while keeping planning and shopping as separate verified workflows.

Observed competitor metadata

Paprika Recipe Manager 3 ↗

Organize your recipes

Paprika identifies recipe management and organisation directly.

The lesson: Saved recipes overlap, but Tasty’s publisher and community discovery are a different acquisition story from organising a personal recipe collection.

Observed competitor metadata

Kitchen Stories Easy Recipes ↗

Healthy Meals & Shopping Lists

Kitchen Stories names easy recipes, healthy meals and shopping lists.

The lesson: The cooking-help intent overlaps. Demonstrate a specific instruction rather than copying ease or health claims without 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.

recipes / cooking videos

Visitor’s job: Find a dish and see how to make it.

Evidence: The current name explicitly names recipes and cooking videos; the third still includes a play control.

Decision: Retain this core intent and demonstrate a real cooking action.

meal planner / dinner ideas

Visitor’s job: Choose meals for a day or week.

Evidence: The subtitle names a meal planner and the interface includes a Meal Plans tab.

Decision: Verify the current planning flow and access before making it the main creative promise.

save recipes / cookbook

Visitor’s job: Collect dishes to return to later.

Evidence: Heart controls, a save button and cookbook wording support collection intent.

Decision: Check account and saved-content behaviour; a save control does not establish offline access or permanent recovery.

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 2021–2023 accounts were selected for instruction clarity, recipe search and access to saved recipes. They are historical research leads, not current defect claims. Allegations about comment deletion and a young reviewer’s contact request were excluded from the published evidence.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 5 February 2021–11 February 2023. No sentiment percentage is calculated.

1 October 2022 · 1/5 stars

“what each part of the process would look like”

An October 2022 reviewer valued detailed cooking-process videos but disliked what they described as faster, less instructional replacements.

What I’d investigate: Treat this as a clarity research lead. It does not establish the format of every current video or a universal decline in quality.

Listing review source · Review ID 9140949807

5 February 2021 · 4/5 stars

“more relevant results”

A February 2021 reviewer praised ingredients, instructions and visuals while asking for more relevant search and personalised suggestions.

What I’d investigate: Preserve the generally positive assessment and minor heat-instruction concern. Test current retrieval with real cooking needs rather than infer search failure rates.

Listing review source · Review ID 6955510259

11 February 2023 · 4/5 stars

“recipes saved on my account”

A February 2023 returning user described login errors that prevented access to saved recipes after reinstalling.

What I’d investigate: Verify current account recovery and saved-content continuity. Do not recommend using another person’s phone number, reproduce the reviewer’s diagnosis or claim the issue persists.

Listing review source · Review ID 9607379969

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

Quantity is the easy claim

A grid and catalogue count leave the practical cooking advantage vague.

Deliverable: Lead with one dish and a specific, supported way the app helps prepare it.

Creative brief and current-product check
02

Another feed postpones the payoff

The community post adds inspiration before any instruction has been shown.

Deliverable: Replace this position with a readable recipe step and its useful cooking context.

Creative brief and current-product check
03

The video is still a thumbnail

A play button and recipe rating do not demonstrate the instruction.

Deliverable: Show a genuine step with readable timing or quantities; keep verified ratings secondary.

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

One test worth running

Does an instruction-led third frame improve cooking-task comprehension and qualified acquisition?

Audience
Eligible US English iPhone default-page visitors, with research among novice and experienced home cooks looking for recipe help.
Control
The captured discovery, community and cookie-preview sequence after verifying retained counts and example claims.
Treatment
Replace only frame three with an authentic instruction for the same cookie recipe. Keep the dish, first two stills, metadata and offers fixed.
Method
Validate the recipe step and its current app presentation, then run comprehension research and eligible randomized App Store product page optimization.
Primary measure
Platform-reported download conversion for eligible randomized visitors.
Guardrails
Visitors should understand the instruction and effort without assuming a guaranteed result, diet suitability or universal shopping availability. Assess recipe starts separately where attribution permits.
Decision rule
Predefine useful effect, sample requirement and analysis date using actual baseline traffic. Keep control if inconclusive or if increased interest accompanies worse understanding of the cooking task.
What could muddy the result
Seasonal dishes, social-video campaigns, recipe availability, subscription changes and home-cooking experience can affect response.

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/10Tasty is here

    Recognisable. Not convincing.

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

  5. 5/10

    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. Lead with one dish and a specific, supported way the app helps prepare it.
  2. Replace this position with a readable recipe step and its useful cooking context.
  3. Show a genuine step with readable timing or quantities; keep verified ratings secondary.

What would change my mind?

  • Current cooking-mode presentation and video controls.
  • Recipe-count provenance, recipe access and saved-content recovery.
  • Baseline acquisition and instruction comprehension by cooking experience.
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 Tasty. 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.