Food & delivery · US iPhone listing

ASO Audit: DoorDash

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

4/10Recognisable. Not convincing.

DoorDash opens with everything, then finally shows what is nearby. The first frame is a product collage that could promise far more than the visitor's address supports. Start with the useful local choice.

ASO Audit: DoorDash illustration: A delivery bag opens into restaurants, groceries and neighborhood routes.
Gabriel Machuret in an ASO Guru T-shirt: questioning the vague promise.

Gab’s verdict · 4/10Gabriel Machuret

Editorial illustrationA floating shopping basket is not local availability.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 · 29/30 characters

DoorDash: Food, Grocery, More

Observed subtitle · 30/30 characters

Food Delivery, Grocery, Retail

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

Why this gets 4/10

The browse and order surfaces are recognisable, and range matters to shoppers. Keep that. Make the local availability and relevant conditions as understandable as the bright orange campaign. Show one local order and its tracking. Enlarge delivery qualifications and reduce the add-on clutter. Availability should be demonstrated at the address level, not implied by floating groceries.

  1. Reason to care

    1/2

    The local ordering context offers a relevant convenience proposition. The range-led opener needs a more concrete ordering example.

  2. Product evidence

    1/2

    Browsing and confirmation appear without a focused local decision.

  3. Readable at a glance

    1/2

    Repeated orange frames and small qualifiers weaken hierarchy.

  4. A useful sequence

    1/2

    Range leads before the useful address-to-order path.

  5. A reason to choose

    0/2

    Breadth and speed assertions need clearer availability scope.

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

Everything is too broad a promise

Look at the original: A wide assortment of products appears without an app browsing interface.

Why I’m flagging it: The collage supplies no local browsing evidence.

Brief this change

Lead with a real nearby-store example and a specific benefit.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The address should drive the story

Look at the original: The interface anchors discovery to a location and presents store-specific examples.

Why I’m flagging it: Useful local cards compete with promotional decoration.

Brief this change

Enlarge one availability decision at the sample location.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The confirmation has two agendas

Look at the original: A time-led headline is qualified, while the UI presents both tracking and an additional shopping action.

Why I’m flagging it: Tracking and an add-on shop compete beneath a time claim.

Brief this change

Focus on the same order's status and keep timing qualifications readable.

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

DoorDash: Food, Grocery, More

Food Delivery, Grocery, Retail

Proposed alternative

DoorDash: Food & Groceries

Find local food and stores

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

The alternative gives the visitor a discovery action and a local context. It deliberately avoids an absolute delivery-time or price claim while preserving the two strongest categories in the captured sequence.

The tradeoff: The current name and subtitle explicitly extend into retail and more categories. The narrower wording could weaken that expansion, so compare relevant category demand before replacing the broader metadata.

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

  1. 01Make the benefit clear

    Proposed headline

    See what is nearby

    Illustrative layout · verify the real flow

    Put this in the frame: A current address-based browse screen with verified local examples.

    Why it earns the space: Make checking availability the first action instead of implying that every pictured product is everywhere.

  2. 02Show useful evidence

    Proposed headline

    Choose what you need

    Illustrative layout · verify the real flow

    Put this in the frame: A verified menu or grocery selection from the same example journey.

    Why it earns the space: Connect browsing to an actual shopping decision with accurate prices and options.

  3. 03Move the decision forward

    Proposed headline

    Follow the order

    Illustrative layout · verify the real flow

    Put this in the frame: A current tracking view with an estimated window and readable qualifications.

    Why it earns the space: Finish one journey before introducing optional add-on shopping.

The test: Does placing the existing address-and-browse frame before the product collage improve 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

Uber Eats: Food & Groceries ↗

Fresh grocery delivery & more

Uber Eats names food and groceries and highlights fresh grocery delivery.

The lesson: DoorDash’s broadening category is not unique by itself. Show how a local shopping task begins.

Observed competitor metadata

Grubhub: Food Delivery ↗

Restaurant Takeout & Grocery

Grubhub names food delivery, restaurant takeout and groceries.

The lesson: Restaurant and grocery intentions overlap, but the examples should match the audience rather than promise every category equally.

Observed competitor metadata

Instacart: Groceries & Food ↗

Shop Grocery Delivery Services

Instacart centres groceries and grocery-delivery services.

The lesson: Its narrower positioning makes the shopping job explicit. DoorDash can retain range while giving one concrete entry point.

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

Visitor’s job: Order a meal from a nearby restaurant.

Evidence: Food categories and takeout imagery appear in the opening sequence.

Decision: Check actual restaurant-intent traffic before making grocery expansion the dominant message.

grocery delivery / local groceries

Visitor’s job: Find available groceries for a delivery address.

Evidence: The second frame shows grocery-store cards beneath a location and search field.

Decision: Research local-shopping language and coverage; do not turn a specific offer example into a universal fee claim.

flowers delivery / retail delivery

Visitor’s job: Get an everyday or occasion-specific item locally.

Evidence: The collage and add-on-store examples extend beyond food.

Decision: Validate category availability and the user’s urgency; avoid guaranteed assortment or delivery-time promises.

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 historical accounts were selected for instructions, timing and service expectations. Their captured star ratings conflict with much of the text. They are not a representative sample, and the service disputes have not been independently adjudicated.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 28 April 2020–24 September 2024. No sentiment percentage is calculated.

3 January 2021 · 5/5 stars

“specific instructions”

A January 2021 reviewer described delivery-instruction and cancellation problems.

What I’d investigate: Check the current instruction and confirmation flow; this old account does not verify present service reliability.

Listing review source · Review ID 6824231072

28 April 2020 · 5/5 stars

“contact info”

An April 2020 reviewer described a delayed order and difficulty getting help.

What I’d investigate: Research how timing and support are explained today without treating the individual account as an operational fact.

Listing review source · Review ID 5873339596

24 September 2024 · 5/5 stars

“arrival time”

A September 2024 reviewer objected to changing arrival estimates and described other service disputes.

What I’d investigate: Test comprehension of estimated windows and update messages; do not turn disputed allegations into claims about current conduct.

Listing review source · Review ID 11760163860

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

Everything is too broad a promise

The collage supplies no local browsing evidence.

Deliverable: Lead with a real supported nearby-store example and a specific benefit.

Creative brief and current-product check
02

The address should drive the story

Useful local cards compete with promotional decoration.

Deliverable: Enlarge one supported availability decision at the sample location.

Creative brief and current-product check
03

The confirmation has two agendas

Tracking and an add-on shop compete beneath a time claim.

Deliverable: Focus on the same order's status and keep timing qualifications readable.

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

One test worth running

Does placing the existing address-and-browse frame before the product collage improve conversion?

Audience
Eligible US English iPhone default-page visitors, interpreted alongside restaurant, grocery and retail acquisition mix.
Control
Current product collage first, local browsing second and tracking third.
Treatment
Swap the complete first and second frames only; keep the third frame, all later creative, metadata and offers unchanged.
Method
Verify the two frames stand alone and all examples remain accurate, then use eligible App Store product page optimization for an order-only test.
Primary measure
Platform-reported download conversion within eligible randomized traffic.
Guardrails
Separately test whether viewers understand local availability, variable delivery estimates and offer conditions. Do not accept an apparent gain caused by a broader misleading promise.
Decision rule
Set the useful effect and planned sample from actual traffic before launch. Retain control if inconclusive; this does not establish completed orders, delivery satisfaction or profit.
What could muddy the result
Local merchant coverage, promotions, seasonal shopping, weather and acquisition-source mix can alter the audience and relevance of the examples.

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/10DoorDash 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 a real supported nearby-store example and a specific benefit.
  2. Enlarge one supported availability decision at the sample location.
  3. Focus on the same order's status and keep timing qualifications readable.

What would change my mind?

  • Current local availability and offer conditions for the creative examples.
  • Restaurant, grocery and retail acquisition mix.
  • Conversion baseline and recent timing-and-support 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 DoorDash. 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.