Food & delivery · US iPhone listing

ASO Audit: Uber Eats

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

3/10The app deserves better.

Uber Eats opens like a supermarket shelf has fallen onto the design file. The second frame adds more range. The useful nearby restaurant view arrives third. A hungry visitor should not need a category tour first.

ASO Audit: Uber Eats illustration: A wall of food choices narrows to one clear meal through an opening.
Gabriel Machuret in an ASO Guru T-shirt: questioning the vague promise.

Gab’s verdict · 3/10Gabriel Machuret

Editorial illustrationAlmost anything. Except a clear first food 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 · 27/30 characters

Uber Eats: Food & Groceries

Observed subtitle · 29/30 characters

Fresh grocery delivery & more

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

Why this gets 3/10

The local options show a recognisable ordering product. Keep that. The retail collage and range message use the strongest positions before the visitor gets a useful food decision. Lead with one local food decision, make availability and relevant costs readable, then show tracking. Retail expansion can move later. A burger floating beside headphones is not a practical reason to install.

  1. Reason to care

    1/2

    The food and retail ordering context provides a relevant convenience proposition, but the breadth-led collage weakens the specific local-food benefit.

  2. Product evidence

    1/2

    Local options appear only after a connected collage.

  3. Readable at a glance

    1/2

    Tilted devices and dense product imagery reduce focus.

  4. A useful sequence

    0/2

    Two opening frames repeat breadth before a useful food decision.

  5. A reason to choose

    0/2

    Brand and assortment do not establish local availability or an advantage.

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 opener is a category collision

Look at the original: A dense home view combines several delivery categories and a grocery-focused message.

Why I’m flagging it: Retail, groceries and restaurant cues compete in one dense view.

Brief this change

Lead with a focused order scenario for the intended audience.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

More range repeats the problem

Look at the original: The second image extends the phone edge and product collage from the opening.

Why I’m flagging it: The connected collage spends another frame saying almost anything.

Brief this change

Replace it with a readable menu or checkout decision from the same example.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The useful browse screen arrives late

Look at the original: The interface shows nearby options and several decision cues before ordering.

Why I’m flagging it: Local cues and prices finally support an actual choice.

Brief this change

Move this forward and enlarge the relevant availability, cost and timing qualifications.

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

Uber Eats: Food & Groceries

Fresh grocery delivery & more

Proposed alternative

Uber Eats: Food & Groceries

Order meals and everyday needs

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

Keep the observed descriptive name and propose a task-led subtitle that spans meals and everyday items without claiming universal selection, speed or price.

The tradeoff: The alternative removes the explicit fresh-grocery emphasis. That may be important to acquisition strategy, so compare the actual restaurant/grocery/retail intent mix before making the change.

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

  1. 01Make the benefit clear

    Proposed headline

    See what is available nearby

    Illustrative layout · verify the real flow

    Put this in the frame: A current location-aware restaurant list with accurate illustrative decision information.

    Why it earns the space: Start with a recognisable meal-selection job.

  2. 02Show useful evidence

    Proposed headline

    Groceries and more, when available

    Illustrative layout · verify the real flow

    Put this in the frame: A verified grocery/retail view for the same example area, with availability context.

    Why it earns the space: Explain breadth as an additional use case rather than a universal promise.

  3. 03Move the decision forward

    Proposed headline

    Review the order before you place it

    Illustrative layout · verify the real flow

    Put this in the frame: A verified checkout review with delivery address, applicable charges and key conditions.

    Why it earns the space: Show an informed first transaction; do not invent cancellation rights or a fee guarantee.

The test: Does a simpler restaurant-first opening pair work better than the current connected assortment montage? 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

DoorDash: Food, Grocery, More ↗

Food Delivery, Grocery, Retail

DoorDash explicitly lists food, grocery and retail delivery in its metadata.

The lesson: Breadth is common in this market; showing a clear first transaction can be more useful than claiming the widest range.

Observed competitor metadata

Grubhub: Food Delivery ↗

Restaurant Takeout & Grocery

Grubhub centres food delivery with restaurant takeout and grocery language.

The lesson: Restaurant intent and grocery intent overlap, but they can require different opening examples.

Observed competitor metadata

Instacart: Groceries & Food ↗

Shop Grocery Delivery Services

Instacart puts groceries first and reinforces delivery services.

The lesson: A grocery-led visitor should see the right selection journey rather than a restaurant story with a grocery label added.

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 delivery / restaurant delivery

Visitor’s job: Find a nearby meal and understand the ordering options.

Evidence: Restaurant browsing is visible in frame three and food remains in the observed name.

Decision: Research local meal intent and the information needed before ordering; never infer universal delivery coverage.

grocery delivery

Visitor’s job: Refill household food without a store visit.

Evidence: The subtitle and first-frame banner emphasise groceries.

Decision: Validate local assortment and the grocery workflow before giving this intent a dedicated page.

convenience delivery / local retail

Visitor’s job: Get an item from a nearby participating store.

Evidence: The opening includes retail logos, convenience navigation and non-food products.

Decision: Keep this separate from restaurant assumptions; verify availability and applicable transaction conditions.

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

These three 2024–2025 complaints were chosen for address, rating/text mismatch and retail-versus-restaurant expectations. They deliberately overrepresent problems and do not establish prevalence, current policies or the truth of disputed charges.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 23 March 2024–24 February 2025. No sentiment percentage is calculated.

24 February 2025 · 5/5 stars

“Work address”

A February 2025 reviewer described ordering to the wrong address and disputing a cancellation charge.

What I’d investigate: Research address confirmation and current pre-order comprehension; this account does not establish the platform’s present policy or resolve the dispute.

Listing review source · Review ID 12351052878

8 April 2024 · 5/5 stars

“5 stars”

An April 2024 reviewer explicitly said the five-star rating was intended to increase visibility of a complaint.

What I’d investigate: Code the text separately from the star value. Do not classify this as a satisfied customer or calculate sentiment from stars alone.

Listing review source · Review ID 11133773817

23 March 2024 · 5/5 stars

“a store, not a restaurant”

A March 2024 reviewer expected a retail order to work differently from a prepared-food order.

What I’d investigate: Examine whether breadth-led acquisition explains the correct transaction context, without claiming that all retail and restaurant policies differ in a particular way.

Listing review source · Review ID 11077826465

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 opener is a category collision

Retail, groceries and restaurant cues compete in one dense view.

Deliverable: Lead with a focused supported order scenario for the intended audience.

Creative brief and current-product check
02

More range repeats the problem

The connected collage spends another frame saying almost anything.

Deliverable: Replace it with a readable menu or checkout decision from the same example.

Creative brief and current-product check
03

The useful browse screen arrives late

Local cues and prices finally support an actual choice.

Deliverable: Move this forward and enlarge the relevant availability, cost and timing qualifications.

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

One test worth running

Does a simpler restaurant-first opening pair work better than the current connected assortment montage?

Audience
Eligible US English iPhone default-page visitors. Record acquisition mix where available without pretending the default test targets only hungry restaurant customers.
Control
The current connected first and second screenshots, with the remaining sequence unchanged.
Treatment
Replace the first pair with two approved self-contained frames: local restaurant browsing, then grocery/retail breadth. Preserve metadata, offers and later assets.
Method
Run an eligible App Store product page optimization creative-concept test. This compares a two-frame treatment as a whole; it cannot identify which individual headline, crop or image caused a difference.
Primary measure
Platform-reported download conversion for eligible randomized visitors.
Guardrails
Use separate comprehension research to check expected local availability, delivery charges and the need to confirm the address before ordering.
Decision rule
Predefine a useful lift, sample requirement and review point from actual traffic. Keep control if the result is inconclusive or the treatment creates unsupported availability expectations.
What could muddy the result
Merchant promotions, grocery expansion, local availability, membership campaigns and seasonal meal demand can change acquisition intent.

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

    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/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 a focused supported order scenario for the intended audience.
  2. Replace it with a readable menu or checkout decision from the same example.
  3. Move this forward and enlarge the relevant availability, cost and timing qualifications.

What would change my mind?

  • Current local browsing, checkout and order-condition verification.
  • Restaurant/grocery/retail acquisition mix and actual conversion baseline.
  • Recent representative review research and newcomer comprehension tests.
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 Uber Eats. 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.