← All case studies
SpotifyMusic

Spotify search: browsing, history, mixed results and format filters

This captured iOS journey moves from Spotify’s search landing page and browse categories into recent history, typed suggestions, mixed results and separate Artist, Album, Playlist and Audiobook filters. The query remains visible, content types are named, recent items can be removed, filter chips show their selected state and result rows provide actions such as Follow or Add.

The screenshots show interface structure, not whether search is fast, personalised, trustworthy or engaging. A familiar image does not demonstrate the Recognition Heuristic, a verification badge does not prove authority or quality and an Add button is not a default. The query “ice” also produces artists, events, music videos, playlists, songs and audiobooks, so the practical questions are how ranking is explained, how formats are distinguished and whether people can narrow, understand and correct the result set.

Captured
Capture date not recorded
10
Screens
4
Ingredients
5
Applications
Spotify product journey

Common contexts

Search

Business goals

EngagementSearch Success

What works

What the captured flow does well.

  • The landing page provides a direct search field, camera control and labelled starting categories for browsing.
  • Recent searches include artwork, a content-type label and an individual removal control.
  • Typed suggestions preserve the entered query and combine query completions with named result types.
  • Result pages keep the query visible and provide horizontally scrollable format filters with a clear selected state.
  • Artist, event, song, playlist, video and audiobook results use distinct metadata and relevant Follow or Add actions.
  • Audiobook results show Premium availability, rating, duration, author and a description excerpt.

What could improve

What deserves closer review.

  • The landing page does not explain how browse categories and “Discover something new” recommendations are ordered or personalised, or what the camera search will capture.
  • Recent-history management is limited to removing one row at a time; no clear-all, retention or history-setting route is visible.
  • Query suggestions and direct content results share one list without explaining which are completions, which are personalised and why they are ranked.
  • The mixed result page spans many formats while filter chips extend beyond the viewport, making the full set easy to miss.
  • Verification badges and Spotify-authored or “Made for you” labels are visible but their meaning and role in ranking are not explained.
  • “Included in Premium” is repeated without clarifying separate purchase, listening-limit or entitlement conditions, and audiobook descriptions create a dense list with mixed languages.

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.

01
Spotify: Search landing

Screen 01

Search landing

Categories & FiltersContent BrowsingSearch
Opportunity

Keep the search field and category labels prominent, but explain what camera search captures before requesting permission. Describe how “Discover something new” is selected and let people correct or reduce unwanted personalisation.

02
Spotify: Search landing categories

Screen 02

Search landing categories

Categories & FiltersContent Browsing
Chunking

Spotify presents browsing categories as labelled visual blocks. The grouping may support scanning when the labels match how people think about the content; the screenshot does not show improved recognition, recall or decision speed.

Opportunity

Group a long category list under plain, meaningful headings and test whether people can find a known category. Only prioritise listening-history categories when the reason is clear and the person can change that personalisation.

03
Spotify: Search active (recent)

Screen 03

Search active (recent)

Content BrowsingRecently Viewed / HistoryRecommendationsSearch
Default Effect

Activating search places focus in the field and opens the keyboard. This is the default input state for text entry; the screenshot does not show whether it improves task speed or excludes another preferred input method.

Salience Effect

A “Recent searches” heading sits above large rows with artwork, content-type labels and repeated removal controls. This is an observable hierarchy for history; the screenshot cannot show what attracts attention or whether reuse improves search success.

Opportunity

Keep the visible content-type labels and individual removal controls. Add clear-all and history-setting routes, explain how long searches are retained and preserve keyboard and screen-reader focus after a row is removed.

04
Spotify: Search active (suggested searches)

Screen 04

Search active (suggested searches)

Content BrowsingRecommendationsSearch
Opportunity

Distinguish query completions from direct artist, song, album or playlist results. Explain suggestion inputs in accessible help and only use labels such as “Frequently played” when they are accurate, useful and privacy-appropriate.

05
Spotify: Search results (scrolled)

Screen 05

Search results (scrolled)

Categories & FiltersContent BrowsingRecommendationsSearch
Framing Effect

“Included in Premium” appears in green above an audiobook result within the mixed list. This frames access as part of the paid tier; the screenshot does not show entitlement details, perceived value or conversion.

Opportunity

Explain verification badges and ranking without equating them with quality. Keep events, artist results, Spotify playlists and individual tracks distinguishable, and make every filter chip discoverable beyond the viewport.

06
Spotify: Search results

Screen 06

Search results

Categories & FiltersContent BrowsingPlayer controlsSearch
Opportunity

Use descriptive section headings for each visible format, show language and access conditions where relevant and preserve the query and active filters while scrolling. Do not add headings merely to imply organisation that the ranking does not support.

07
Spotify: Search results (filter: artist)

Screen 07

Search results (filter: artist)

Categories & FiltersContent BrowsingSearch
Opportunity

Explain what the verification badge confirms and keep Follow separate from result selection. Add genre, location or other metadata only when research shows it helps distinguish similarly named artists; follower counts are not a quality measure.

08
Spotify: Search results (filter: albums)

Screen 08

Search results (filter: albums)

Categories & FiltersContent BrowsingSearch
Opportunity

Clarify that the Albums filter also returns singles, or rename the filter to match its contents. Keep release type, artist, explicit status and release date easy to compare without relying on artwork recognition.

09
Spotify: Search results (filter: playlists)

Screen 09

Search results (filter: playlists)

Categories & FiltersContent BrowsingSearch
Opportunity

Distinguish Spotify-authored, personalised and user-created playlists and explain why each ranks for the query. Give Add controls accessible names that include the playlist title and preserve position after the action.

10
Spotify: Search results (filter: audiobooks & podcasts)

Screen 10

Search results (filter: audiobooks & podcasts)

Categories & FiltersContent BrowsingSearch
Framing Effect

Each audiobook row begins with the green label “Included in Premium”. The repeated label frames access as a subscription benefit; the screenshot does not establish purchase intent or explain listening limits and other conditions.

Opportunity

Offer language and format controls, keep description expansion optional and explain Premium inclusion, listening limits or separate purchase before Add. Identify the rating source and keep essential title, author and duration information easy to scan.

Keep exploring

See how another product shapes behaviour.

Browse all case studies