Interaction DesignTYPENORMLabs7 minSeptember 25, 2026

DoorDash UX Teardown: Stay Tuned, in Times Square

A UX teardown of DoorDash's signed-out web order flow, from the city directory to the pickup cart: an address that returns a launching-soon message in Manhattan, a pickup map that finds the restaurants delivery couldn't, and a cart that puts Continue above the order it confirms.

DoorDash's New York page lists Silver Palace Restaurant as open now, 0.4 miles away, 23 minutes, $0 delivery fee. Type a Times Square address into the box above that card and pick one of the suggestions, and the next screen reads "STAY TUNED" in letters taller than the navigation, over one sentence: "We couldn't find any restaurants near your location that we currently deliver from. Follow along as we launch in new cities."

The capture below follows one signed-out visit from DoorDash's delivery directory to a pickup cart, then to the DashPass page. It stops before Continue.

1 / 14

Delivery city directory

DoorDash starts signed-out discovery with a country switcher and city index before asking for an exact address.

View full flow (14 screens)

A city list without states

The flow opens at /food-delivery/, under the heading "Food delivery near me", with three country pills (United States, Australia, Canada) and a grid of Popular Cities, five columns wide.

In the first eight rows, Jacksonville appears four times and Columbus four times. Washington appears three times, and Portland and Dallas twice each. None of the entries carries a state. They're presumably different places that share a name (there's a Columbus in Ohio and one in Georgia), but the list gives a visitor nothing to pick the right one by except guessing and clicking.

The New York page

Clicking New York opens "Food delivery in New York, NY". The page offers one filled red button, Sign in to order, and under it a text link, Search nearby. Below that is a four-column grid of restaurants with photos, star ratings, fees, distances, times, badges like Trending and Wallet-Friendly, and two review excerpts per card.

Search nearby swaps the two controls. An address field with a Go button takes the red button's place, and Sign in to order drops to the underlined link. The restaurant grid doesn't move.

Typing "Times Square, New York" brings up three suggestions: 6 Times Sq and 9 Times Sq, both at 10036, and International Business Times at 7 Hanover Sq, in the Financial District. The third matched on the word "Times". Each suggestion has its postal code under it, so the wrong one is easy to spot.

The Times Square address

Selecting 9 Times Sq loads /home, and the page changes shape. The restaurant grid is gone. There's now a left rail (Home, Grocery, Retail, Convenience, Browse All), a search bar, the address in a pill, a Delivery/Pickup switch, and a cart showing 0.

Unavailable delivery state
Unavailable delivery state — Unavailable delivery inventory becomes a large illustrated empty state without removing navigation or fulfillment controls.

The message says DoorDash doesn't deliver near this location and is launching in new cities. The page before it listed New York restaurants open now with delivery times.

We can't tell from the capture why this address returned no delivery results. The session was signed out and the browser was in Brazil, which also shows up later as a promotion in reais, so the location context may have played a part. The copy is written for a city DoorDash hasn't launched in. The address is in Midtown Manhattan. The message offers no next step (NN/g on empty states). The Pickup option, which turns out to work, is a small toggle in the header, and the message doesn't mention it.

Pickup

Switching the header toggle to Pickup opens a different layout at /pickup: store cards on the left, a Mapbox map on the right, densely pinned with restaurants around Times Square, and a "Search as I move the map" checkbox, ticked.

Pickup store map
Pickup store map — Pickup opens a two-pane marketplace with menu previews and fees beside geographically labeled supply.

The first store card, Carnegie Pizza, has a 1-minute walk, a closing time, three menu items with prices, and two buttons under them: Delivery, "$0 delivery fee, first order", and Pickup, "$0 fees". Empanada Mama's card, two screens later, has the same pair. So on the screen right after "we couldn't find any restaurants near your location that we currently deliver from", each restaurant offers delivery with the first fee waived. The capture didn't click one of those Delivery buttons, so it can't say what would have happened.

The filter chips work as you'd hope. DashPass narrows the list and the map together, with no page load. Adding Over 4.5 keeps DashPass on, and each active chip gets a dark outline. Empanada Mama (4.8, 2k+ ratings) tops the list under both. The chip row is too wide for its column, though. After two filters, Over 4.5 is half hidden behind a scroll arrow, so the one you just turned on is the hardest one to see.

The store page

Empanada Mama's page carries a lot. There's a banner photo, Store Info (DashPass, Open now, 4.8 stars, 0.4 mi, $$, Bakery), a Delivery/Pickup/Group Order switch, "$0 pricing & fees", "12 min ready for pickup", the pickup address with a map, and a Featured Items carousel.

Some of it doesn't agree. The breadcrumb files the store under Latin American while Store Info calls it a Bakery. The distance reads 0.4 mi, and the walk icon beside the pickup address reads 1 min. At an ordinary walking pace 0.4 miles takes about eight minutes. A health-inspection address sits in Store Info as plain text that isn't a link, wrapping across two lines and running into the next column. And a floating banner near the bottom reads "Enjoy R$0 delivery fee on your first order", in Brazilian reais, on a pickup order with dollar prices.

The R$ is almost certainly the Brazil browser context, as the capture notes say. It's still what a visitor would see.

Adding an item

Arroz Con Pollo opens in a modal with a photo, a one-line description, an optional Modifications section ("Select up to 1": *No Maduros), Preferences, a quantity stepper, and a red "Add to cart - $23.50". Ticking No Maduros fills the checkbox and changes nothing else, which is correct, since it's free.

After Add to cart the modal closes, and there are two signs the item went in: a small "1×" badge on the dish's card, and the header cart count going from 0 to 1. There's no toast or drawer. Both signs are small and sit at opposite ends of the screen, and someone watching the button they just pressed could miss both (NN/g on visibility of system status).

The cart drawer

The cart opens as a drawer from the right.

Pickup cart review
Pickup cart review — The cart summarizes restaurant, fulfillment, pickup map, address, configuration, quantity, and price before Continue.

Top to bottom: "Your cart from Empanada Mama", a red Continue button, "This is a Pickup order", "You'll need to go to Empanada Mama to pick up this order", a map with the pickup address, and last, the item. That's Arroz Con Pollo, *No Maduros, $23.50, with a trash icon and a quantity control.

The primary action sits above everything it commits you to. Someone who reads top-down meets Continue before they learn this is a pickup order, and before they see what's in the cart. The pickup warning is the most important line in the drawer, because the person ordering has to go and collect the food, and it comes after the button. There's also no subtotal, fees line or total yet, so the drawer never says what Continue will cost. The flow stopped here.

DashPass

The last screen is /dashpass/, a single card: "Get $0 delivery fees plus exclusive benefits", four benefits ($0 delivery fees, member-exclusive deals, 5–10% off Lyft rides, 5% back on eligible pickup orders), and one button, Sign in. The card shows no price and no trial length, and doesn't say how often you'd be billed. A signed-out visitor learns what the subscription includes and nothing about its cost until they sign in. The first benefit on the card is $0 delivery fees.

What to fix first

The empty state. It's the one screen in the flow that can end the visit, and it gives a wrong reason with no way forward. If no restaurant is delivering to an address right now, say that. "Nothing's delivering to 9 Times Sq right now" is true, and it doesn't claim the city is unlaunched. Then put the working option in the message itself: a Pickup button, since the next screen pins dozens of pickup stores around the address.

After that, the cart order. Put the item, the pickup warning and a price above Continue, so the button comes after the things it confirms.

Take it further

We read DoorDash through the UX Clarity framework, the lens behind our Full UX Audit. The question it asks here: at each step, does the screen tell you what just happened and what you can do next? For how that scoring becomes a ranked fix list, read what a real UX audit looks like.

Capture notes: fourteen screens from one signed-out session on 24 September 2026, at 1440×900, in US English, on DoorDash's United States site, viewed from a browser in Brazil. Menu prices were in US dollars; one promotion showed R$. The Times Square address is a public landmark, not a personal address. Restaurant availability, ratings, fees, prices, times and DashPass benefits were true that day and will have changed. The session stopped before Continue, sign-in, checkout or payment, and the DoorDash homepage was outside the capture's scope.

Sources: NN/g — Designing Empty States in Complex Applications · NN/g — Visibility of System Status.

Want to know which of your empty states gives a reason that doesn't fit? Apply for a Full UX Audit →

Free UX Snapshot for 50 Product Teams

Apply now and get a complimentary UX Snapshot — our rapid clarity audit delivered in 48 hours. Limited to the first 50 products.

Apply for Free UX Snapshot

Related

Design Principles & Laws

Gestalt Principles in UI Design: Which One Wins When Two Disagree

The gestalt principles describe how people group what they see: proximity, similarity, common region, closure, continuity, figure-ground, common fate. On a real screen several apply at once, and the layout bugs come from two of them giving different answers.

TYPENORMLabs · 10 min · September 30, 2026

Design Principles & Laws
Visual Hierarchy
Web

Accessibility

WCAG 2.2: What Changed and What It Means

WCAG 2.2 added nine success criteria and removed one. What each new criterion asks for, which ones count toward AA, what stayed the same on contrast, and how to update a 2.1 audit.

TYPENORMLabs · 9 min · September 23, 2026

Accessibility
Web

Visual Hierarchy

Visual Design Principles for Product Teams: A Check for Each One

Visual design principles are hierarchy, contrast, proximity, alignment, repetition, scale, and whitespace. For a product team they are most useful as checks you can run on a screenshot in a review, so a disagreement about a screen ends with a measurement instead of a vote.

TYPENORMLabs · 9 min · September 29, 2026

Visual Hierarchy
Design Principles & Laws
Web