Quick-Service Ordering App

A psychology-led audit that found the app was well made and the model around it was leaking, then showed what to fix first.

Role
UX audit and redesign direction
Platform
iOS and Android, customer and rider apps
Scope
46 screens, 5 flows, the design system
Domain
Food ordering, Gulf

Under NDA, so names and screens here are re-created.

  • 46screens

    Reviewed across five flows in the customer and rider apps

  • 45findings

    16 of them high severity, each tied to a behavioural principle and a fix

The brand delivers with its own riders only within 1 km of a branch, and its branches sit together in a busy central district full of hotels. For most residents, being out of range isn't an edge case; it's the normal case.

The app let people browse, build their order and choose extras, then checked the distance at Add to cart. Anyone outside the zone got four equal links to partner apps and left, taking the order, the data and the loyalty points with them.

  • Keep the brand's tokens and components; upgrade the craft, not the identity.
  • The server stays the authority on the delivery boundary.
  • Partner delivery stays visible and honest: prices and fees may differ, and points aren't earned there.

The audit's headline: the app is well crafted, the model around it leaks. Fix that first, polish the rest.

01 Decide the channel when the app opens

Check serviceability on launch and on every address change, not at Add to cart. Within 1 km the default is delivery; from 1 to 3 km it's pickup; beyond that the customer sees the honest options before they start.

02 Pickup is the most profitable order

No rider cost, the customer stays in the app and earns points, ready in about 15 minutes. It didn't exist in the product yet, so the redesign builds it end to end.

03 Turn a dead end into a guided choice

One recommended option, two alternatives, and the cart is never lost. A partner hand-off is tracked; a 'tell me when you deliver here' turns a refusal into a lead.

04 Every finding names its principle

Peak-end rule, Hick's law, loss aversion, default bias and more, each with severity and a fix, so the team can argue with the reasoning rather than the taste.

05 Keep the tokens, cut the drift

Measured across 25 screens: 14 corner radii, 12 font sizes, 8 button heights, 5 shadow recipes. Each roughly halved: one accent per screen, type for hierarchy, elevation instead of outlines.

Move the distance slider and add the item to the cart. Before, the app refuses you at the moment you want it most. After, it tells you the truth when it opens and offers the best way to still get your food.

Deliver toHome · Villa 4

Most loved Crispy chicken, 4 pcs With fries, bun and garlic sauce
SAR 26

Re-created for this page. It shows the pattern, with sample data.

The states I check on work like this, because nobody asks for them until they break.

  • Out of rangeSaid on open
  • Between 1 and 3 kmPickup by default
  • Too far for anythingA waitlist, not a refusal
  • Address changedRe-checked without clearing the cart
  • Partner hand-offDisclosed honestly and tracked
  • Scores by flow, weighted by business impact: rider sign-up 8.0, account and rewards 7.5, browse and order 7.0, rider deliveries 6.5, cart and checkout 6.0.
  • Eight redesigned screens that put the strategy into the product, built on the existing tokens.
  • A roadmap in three columns, now, next and later, plus three partner options for the owner to decide on.

These results weren't tracked on this project. With access, these are the numbers I'd watch.

  • Share of 1 to 3 km sessions that convert to pickup
  • Orders lost at the range check
  • Partner taps that turn into orders

Next: Review the delivery strategy with the owner, then start the first column of the roadmap.

Next case isTyme Local Work Marketplace