revamped profile

edit profile

block list

pronoun selecter

brilliant basics

establishing a strong foundation for identity-expression on profile

Problem

Until recently, social has not played a central role on Spotify, and thus the profile (visited by <7% of users/month), has been kept lean. However, as priorities shift and connection becomes more integral to Spotify’s strategy, there’s a need to re-establish the profile as a meaningful surface for expression and connection.

Solution

‘Brilliant Basics’ is the first step towards breathing life into the Spotify profile, introducing a set of essential details & privacy controls to establish a foundation for connection.

With this first phase of redesign, we hoped to make the profile feel more personal, but also more secure.

inexpressive

uncustomizeable

unclear actionables

Users perceive the current profile content as a poor representation of their identity, featuring few details & hardly any expressive content. As a result, users find little relevance in engaging with or sharing the surface.

The content on profile is auto-populated from recent activity (creating playlists, following artists). Given the lack of control, users feel worried that their profile could misrepresent their tastes & interests to their followers.

If a user is uninterested in blindly exploring another's playlists, disrupting their current listening session, there is no real value or opportunity in visiting another's user profile.

We worked with UXR to set up a study exploring user expectations of the profile. Users were given a blank profile, alongside a set of potential features & asked to rank the top 10 features they believed the profile should include. While there was a range of reactions to our more exploratory features, consistent amongst our testers was an perception of basic descriptive features as essential.

* demo is representative, displaying methods, not data

+

pronouns

+

location

+

user biographies

+

deprioritized follow count

+

improved privacy controls

When it came to pronouns, we wanted to make sure that our solution accounted for the range of ways folks use pronouns to express their identity + languages they might hope to represent such. Consequently, we worked through a number of iterations before landing at our final solution: the multi-select edit sheet, a component I contributed to Spotify's design system.
As a company, we have an inclusive & affirming culture around gender & identity expression. While we hold our values strong, we recognize that forcing such upon others in certain spaces would actually put our users in danger. Given such, we worked closely with our localization team to ensure that our introduction of pronouns to Spotify is done in a sensitive and responsible manner. Critical questions to our roll-out strategy included the following...

language

values

safety

law

Does the language have gendered pronouns?

Does this community value pronouns as a meaningful expression of identity?

Would publicly displayed pronouns excessively endanger users who opt in?

How do we navigate in countries where displaying pronouns may result in a violation of the law?

Following a localization team deep dive & much XFN deliberation, we arrived at a solution of staggered release of pronouns to ensure that we enter each communities with intention, care, & respect. The phases we established were as follows...

phase 1

Launch pronouns in countries where pronouns usage is culturally accepted, legal, & relatively safe

phase 2

Research how we might release pronouns in languages where declaration is safe, but the conventions of pronouns aren't widely agreed upon (example: in spanish, there's deliberation as to whether non-binary pronouns should be 'elle/elles' or 'ellx/ellxs'

phase 3

Further research to explore how we might support gender affirmation in spaces where alternative pronoun usage may not be conventional or safe
An enormous hurdle to emerge during our conversations around pronouns was the fine line of supporting gender affirmation while maintaining user-safety. While a particularly salient challenge in places where queer identity is either outlawed or considered taboo, such also reflects a concern that queer folks may feel worldwide. While the addition of pronouns to the profile will always be optional, I also personally believe there would be value in releasing pronouns in a manner that enables users to choose who they feel comfortable displaying such to, whether it be close friends, followers only, or the general public.

now

privacy changes

The privacy changes were implemented in our very first wave of development, prioritizing security of the user profile before venturing into introducing additional identifying information

Next

+ pronouns

The next priority is pronouns, recognizing such as a meaningful expression of identity that’s lightweight to implement and important to support

Next

children's account

Spotify hopes to reduce the impact of child listeners on parental taste profiles by introducing same-device children’s accounts

Such calls for the generation of a profile for account management, which will be kept private & omit identifying details to preserve safety

later

+ all details

My team is currently working with trust & safety to ensure location complies with safety standards prior to releasing the feature

Bios are scheduled for development late 2024, once the moderation team is stood up for UGC

about (project)

I was responsible for the UX/UI of this project, collaborating with localization, trust & safety, and UXW to ensure that our designs:

1. Appropriately capture & communicate the nuance of gender identity

2. Maintain the safety and privacy of our users

3. Comply with legislation across countries of operation

I shipped production-ready designs to the engineering team, and supported the continual design needs throughout the implementation process.

The privacy phase of this work (remove follower, block list, etc.) is live within the current version of Spotify.

The other features (pronouns, details, bio) are phased to be released throughout 2024.

Isabelle Pereira • Product Manager

Chris Doyle • Engineering Manager

Mercedes Krimm • Localization

Mine Miralay • UX Writing

Gonzalo Campos • SWE

Jessica Arruda • SWE

UX/UI in Figma

Prototyping in Figma

Design thinking

User research

XFN collaboration

by aniea, with love ♥