Cross-app screen study · Reviewed September 23, 2026
Starbucks and Deliveroo: when to ask for an account or location
Six July 2026 iOS stills show two different ways to justify setup: Starbucks presents membership benefits before a long form; Deliveroo explains location value and offers a way past account entry.
How can a product ask for account or location information without obscuring the first useful action?
In these exported stills, Starbucks ties registration to Rewards and visibly separates optional email and faster-sign-in choices from required terms. Deliveroo states why it wants location, says the setting can change, and shows a Skip option on the account invitation. The design recommendation is to explain each request at the point of decision and preserve a path to the product where possible; the stills do not demonstrate what happens after every tap.
Evidence and limits
Six selected July 2026 exported iOS screens from two apps, shown in each archive’s order. These are static captures, not a tested journey or a recording. We cannot verify permission prompts, skip behavior, form validation, account creation, conversion, or how the home location was determined.
Read the decisions

01 / Starbucks · Jul 2026 · Still image
Present the membership promise
What is visible
A Rewards panel states a benefit proposition and offers Join now and Sign in.
Design interpretation
Explain why someone would register before asking for personal details.

02 / Starbucks · Jul 2026 · Still image
Group account fields and choices
What is visible
The sign-up sheet groups personal info, security and terms, including optional email and faster-sign-in choices.
Design interpretation
Separate optional preferences from required agreement, and ensure defaults are deliberate.

03 / Starbucks · Jul 2026 · Still image
Expose policy links near consent
What is visible
The lower form shows optional choices, an unchecked terms box and links to terms and privacy documents.
Design interpretation
Keep required consent distinct from marketing preferences and link the actual policies.

04 / Deliveroo · Jul 2026 · Still image
Explain the location request
What is visible
A location screen says nearby places, offers and discounts depend on location and notes the setting can change.
Design interpretation
State the value of location and its reversibility before asking for access.

05 / Deliveroo · Jul 2026 · Still image
Offer account setup with a skip
What is visible
The next screen invites login, offers Continue with Email and includes Skip at the top.
Design interpretation
Give people a way to defer account setup when browsing can be useful first.

06 / Deliveroo · Jul 2026 · Still image
Arrive at a local browsing home
What is visible
The home screen has a location selector, category links, offers and restaurant cards.
Design interpretation
Make the selected area and nearby browsing entry points visible after setup; the still does not prove how location was chosen.
What to question
- Starbucks makes the membership value visible before sign-up, but its form combines identity, security and multiple preferences. Grouping and explicit optional labels help the form remain understandable; a still cannot show completion effort.
- Deliveroo puts location value before the account invitation and visibly offers Skip on that invitation. This can lower the immediate commitment, but the exported screens do not establish what Skip opens or whether location can be entered manually.
- A signed-in or populated home is a useful endpoint for analysis, yet the screenshots cannot prove which earlier decision produced that state. Avoid presenting archive order as a verified interaction path.
Try an original implementation
Explore a three-step web onboarding pattern: choose a goal, set a pace, and optionally request a reminder. Go back to revise answers without losing them.
This React example uses native form controls, keyboard navigation and focus management. It is a separate prototype with original copy and styling, not a reproduction of the source apps.
Download React sourceRequires React and Tailwind CSS. Web only; not React Native. MIT license.
Import the named OnboardingExample component into a page. Replace the final preview with your application logic; this example makes no network requests.
Practice studio · Original web demo
Step 1 of 3
What would you like to practice?
Before you ship
- Explain the immediate benefit of account creation or location sharing beside the request.
- Label marketing, convenience and legal choices separately; do not preselect consent without a reason.
- Offer a clear defer or manual-entry path when the core task permits it.
- Show the selected location or membership state on the destination screen, and let people revise it.
- Test actual transition, keyboard and screen-reader behavior before claiming the flow works as the stills suggest.
Validate these recommendations with your own users. No conversion uplift is claimed.
