Food & lifestyle · US iPhone listing

ASO Audit: Mealime

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

5/10Fine. A dangerous place to stop.

Mealime has the ingredients for a useful story and serves them in the wrong order. Recipe, groceries, then meal plan. The visitor has to cook the explanation themselves.

ASO Audit: Mealime illustration: A chosen meal connects recipe cards to fresh groceries.
Gabriel Machuret wearing an ASO Guru T-shirt, presenting a three-screen app screenshot storyboard.

Gab’s verdict · 5/10Gabriel Machuret

Editorial illustrationDinner is attractive. The planning argument is out of order.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 · 28/30 characters

Mealime Meal Plans & Recipes

Observed subtitle · 27/30 characters

Meal Planner & Grocery List

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

Why this gets 5/10

The recipe and grouped grocery detail are useful. This is more than attractive food photography. The strongest selling point is the connection between the meals and the shopping, so make that connection obvious. Rebuild around choosing meals and producing the resulting shopping list. Use bigger selective crops and an outcome-led opening. The meal photography should attract attention while the workflow explains why to install.

  1. Reason to care

    1/2

    Healthy recipes establish a relevant meal-choice benefit. The planning and grocery convenience are more specific advantages that should appear sooner.

  2. Product evidence

    2/2

    Recipe detail and grouped groceries provide concrete utility.

  3. Readable at a glance

    1/2

    Similar green frames and dense lists weaken visual variety.

  4. A useful sequence

    1/2

    Recipe, groceries, then planning reverses the useful workflow.

  5. A reason to choose

    0/2

    Food imagery and meal planning are not differentiated convincingly.

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

Healthy is the generic option

Look at the original: The recipe card exposes timing, servings and cookware beside the finished dish.

Why I’m flagging it: The finished meal dominates while the planning advantage stays implicit.

Brief this change

Pair the dish with a specific meal-planning benefit and useful recipe detail.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The list appears before its cause

Look at the original: The list groups ingredients and presents a shopping action.

Why I’m flagging it: Grouped groceries are useful, but their connection to chosen meals is missing.

Brief this change

Show selected meals feeding the grocery list with readable quantities.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The starting point arrives third

Look at the original: The interface shows meal selection with visible access distinctions.

Why I’m flagging it: Planning is introduced after its shopping output.

Brief this change

Move meal selection earlier and make Pro-labelled access distinctions legible.

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

Mealime Meal Plans & Recipes

Meal Planner & Grocery List

Proposed alternative

Mealime Meal Plans & Recipes

Pick meals. Build your list.

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

Keep the current descriptive name and make the subtitle explain the sequence from meal choice to shopping preparation.

The tradeoff: The proposed subtitle removes the explicit grocery-list phrase and may be less precise for shopping-related queries. Validate that discoverability trade before adopting action-led wording.

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

  1. 01Make the benefit clear

    Proposed headline

    Choose a meal you want to cook

    Illustrative layout · verify the real flow

    Put this in the frame: A current recipe with its real servings, estimated time and access context.

    Why it earns the space: Make the choice concrete.

  2. 02Show useful evidence

    Proposed headline

    Add it to your plan

    Illustrative layout · verify the real flow

    Put this in the frame: The verified selection step using that same recipe and serving controls.

    Why it earns the space: Show the input that shapes the shopping task.

  3. 03Move the decision forward

    Proposed headline

    Check the list before shopping

    Illustrative layout · verify the real flow

    Put this in the frame: The resulting ingredient list with adjustments for items already owned.

    Why it earns the space: Connect planning to groceries without implying the pictured recipe generates unrelated sample ingredients.

The test: Does showing meal selection before groceries improve understanding of the planning workflow 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

Paprika Recipe Manager 3 ↗

Organize your recipes

Paprika names recipe management and recipe organisation.

The lesson: Its metadata foregrounds keeping recipes. Mealime can clarify selection-to-shopping without assuming that all competing planners recommend meals in the same way.

Observed competitor metadata

eMeals - Healthy Meal Plans ↗

Meal Planner & Grocery List

eMeals names healthy meal plans with the same meal-planner and grocery-list subtitle roles.

The lesson: The overlap is direct. Demonstrating the actual handoff is more useful than another generic planning promise.

Observed competitor metadata

Eat This Much - Meal Planner ↗

Recipes, Macros & Grocery List

Eat This Much names meal planning with recipes, macros and groceries.

The lesson: Macro-led intent is more explicit there. Do not stretch Mealime’s generic healthy wording into a verified nutrition-prescription claim.

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.

meal planner / weekly meals

Visitor’s job: Choose meals before deciding what to buy.

Evidence: The name and third screenshot identify planning and selection.

Decision: Make the plan-to-list mechanism explicit; research frequency without assuming every user plans a full week.

grocery list / ingredients

Visitor’s job: Turn selected dishes into a practical shopping checklist.

Evidence: The subtitle and second still directly show groceries and quantities.

Decision: Verify quantity combination, serving changes and owned ingredients before describing automation in detail.

dinner recipes / meal ideas

Visitor’s job: Find an appealing dish with usable cooking instructions.

Evidence: The opening shows a named meal and cooking tabs.

Decision: Use recipe-fit language rather than guaranteed health, allergy safety, cost or cooking-time outcomes.

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–2026 accounts were selected for plan-to-list value, changing a plan and the distinction between built-in and imported recipes. They are not a representative savings, nutrition or satisfaction sample. Personal health outcomes, old prices and allergy-related expectations are not adopted as product guarantees.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 5 April 2021–9 January 2026. No sentiment percentage is calculated.

11 August 2025 · 5/5 stars

“grocery list”

An August 2025 reviewer valued choosing meals and getting a grocery list, including adding household items.

What I’d investigate: Use the described workflow as a research lead; personal weight, variety and convenience claims are not typical outcome evidence.

Listing review source · Review ID 13004109949

5 April 2021 · 5/5 stars

“grocery list reset”

An April 2021 reviewer liked planning but wanted to add meals without resetting the list and found some recipes more involved than expected.

What I’d investigate: Verify current plan-edit behaviour. The historical request and a friend’s allergy experience do not establish current limitations or dietary safety.

Listing review source · Review ID 7187003086

9 January 2026 · 5/5 stars

“imported a recipe”

A January 2026 Pro user praised shopping and cooking steps but said website recipe import had not worked for them.

What I’d investigate: Retain the failure alongside the praise, and verify import separately. Their stated price, paid access and substitution observations do not define today’s free plan.

Listing review source · Review ID 13611610966

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

Healthy is the generic option

The finished meal dominates while the planning advantage stays implicit.

Deliverable: Pair the dish with a specific meal-planning benefit and useful recipe detail.

Creative brief and current-product check
02

The list appears before its cause

Grouped groceries are useful, but their connection to chosen meals is missing.

Deliverable: Show selected meals feeding the supported grocery list with readable quantities.

Creative brief and current-product check
03

The starting point arrives third

Planning is introduced after its shopping output.

Deliverable: Move meal selection earlier and make Pro-labelled access distinctions legible.

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

One test worth running

Does showing meal selection before groceries improve understanding of the planning workflow and qualified acquisition?

Audience
Eligible US English iPhone default-page visitors; recruit busy home cooks with different household sizes for comprehension research.
Control
The captured recipe-groceries-plan order, after checking the scope of retained health and timing wording.
Treatment
Keep frame one and swap the existing second and third stills. Leave metadata, recipes, access labels and offers unchanged.
Method
Use order-only product page optimization where eligible, preceded by a task asking participants to explain how the three screens connect. Test a same-recipe redesign separately rather than confounding both changes.
Primary measure
Platform-reported download conversion for eligible randomized traffic.
Guardrails
Visitors should recognise a planning tool rather than a meal-kit purchase, guaranteed delivery service or personalised dietary prescription. Check access expectations and shopping-list comprehension.
Decision rule
Predefine the smallest useful effect, required sample and analysis point using actual traffic. Retain control if inconclusive or if stronger conversion comes with mistaken delivery, health or savings expectations.
What could muddy the result
Seasonal eating goals, grocery promotions, recipe additions, household mix and paid-plan changes can 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/10Mealime 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. Pair the dish with a specific meal-planning benefit and useful recipe detail.
  2. Show selected meals feeding the supported grocery list with readable quantities.
  3. Move meal selection earlier and make Pro-labelled access distinctions legible.

What would change my mind?

  • Current plan editing, serving changes and list-generation behaviour.
  • Recipe entitlement, retailer coverage and import support for the examples used.
  • Baseline conversion and planning-task comprehension among relevant households.
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 Mealime. 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.