Spotify first-time setup: preference collection before playback
This captured iOS flow moves from account creation to date of birth, artist preferences, an optional Alexa link and a confirmation of selected artists. It offers email, Google and Apple sign-up, presents artist search alongside a visual grid, shows a selected state and gives the external-account request a “Maybe later” route.
The sequence collects several pieces of data before the capture shows any playback or recommendation outcome. Date of birth is requested without an explanation on the screen, the initial artist set may shape what is easiest to choose, and the Alexa request introduces another service before first value is visible. The screenshots do not establish reduced cognitive load, momentum, trust, retention or increased product value.
- Captured
- Capture date not recorded
- 7
- Screens
- 5
- Ingredients
- 5
- Applications
Common contexts
Business goals
What works
What the captured flow does well.
- Sign-up and log-in are clearly separated, with email, Google and Apple routes visible.
- Artist selection states a minimum, provides search and uses a visible check mark for a selected artist.
- The expanded artist screen appears to respond to an earlier selection while preserving search and a close action.
- The Alexa request explains its intended use and includes a prominent “Maybe later” route.
- The final captured screen repeats the selected artists, confirming what the person supplied.
What could improve
What deserves closer review.
- Date of birth is requested without explaining why Spotify needs it, how it will be used or how long it will be retained.
- The flow does not show its total length, whether artist selection is optional or what happens if the person cannot find three suitable artists.
- The initial artist grid gives a small visible set an advantage; genre browsing and a clear “not here” route would make the starting point less restrictive.
- The Alexa request introduces account linking before the capture demonstrates the value of the selected preferences or explains data exchanged with Amazon.
- The capture ends with praise rather than a visible next action, so it cannot show how quickly the person reaches music chosen from their input.
Screen-by-screen breakdown
Follow the journey.
Each annotation distinguishes what is visible from our interpretation or hypothesis, then identifies a practical opportunity to investigate.
Screen 01
Welcome screen
The headline pairs “Millions of songs” with “Free on Spotify”, framing catalog scale and price together. The screenshot does not show how people interpret “free” or whether the wording changes sign-up.
A filled green “Sign up for free” button receives more visual emphasis than the outlined “Log in” button. This is an observable hierarchy choice, not evidence that people were nudged or that one route improved outcomes.
Keep the free offer prominent, but explain material limits such as advertising, playback restrictions or eligibility before sign-up. Do not add popularity statistics unless they are current, sourced and useful to the decision.
Screen 02
Sign-up options
Keep all sign-up methods and log-in visible. Explain what data Google or Apple shares and whether using email changes recovery, privacy or account features rather than calling one route quicker without evidence.
Screen 03
Personal details
Spotify asks for date of birth on a dedicated account-creation step. This is staged disclosure because the flow presents one decision at a time; the screenshot does not show the total number of steps or why the data is needed.
Explain why date of birth is required, how it will be used and retained, and what age restrictions apply. Show accurate progress or an overview when the remaining sequence is stable.
Screen 04
Artist selection
Explain how the choices affect recommendations, provide genre browsing and search, and offer a clear route when suitable artists are missing. Make any minimum and the consequence of skipping explicit.
Screen 05
Artist selection expanded
Keep the selected state visible and explain why new suggestions appeared. Let people undo, reset or edit choices without restarting and avoid presenting inferred taste as a fixed identity.
Screen 06
Alexa prompt
After music-preference setup, Spotify asks to link an external Alexa account. This is a new-scope request involving another service, so it needs a fresh informed decision. “Maybe later” provides a decline route; the screenshot does not show that earlier choices increased agreement.
Treat Alexa linking as a fresh, optional decision. Explain which accounts and data will be connected, keep “Maybe later” equivalent in clarity and consider asking after the person has used playback unless research supports this timing.
Screen 07
Final feedback
The final captured screen repeats selected artists with “Great picks!”. It creates a distinct ending cue that could be tested as a peak-end hypothesis, but the screenshot does not show later memory, satisfaction or retention.
Confirm how the selected artists will affect the experience, provide an edit route and lead directly to a useful first listening action. Treat the praise as feedback, not evidence of satisfaction or retention.
Keep exploring