Scribd
Upload
1K views4 pages

Spotify Project: Problem Statement

The document proposes building an app to help Spotify users discover new music within their community by accessing and analyzing users' Spotify data. It would aggregate Spotify listening data from users and generate insights like most popular songs, artists, and genres among the community. This would help users find music that resonates with their network and potentially make new friends. The app would use Spotify's APIs to store users' music preferences after they log in. It would then apply algorithms to the aggregated data to provide personalized recommendations and community charts to users.

Uploaded by

Anujain Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1K views4 pages

Spotify Project: Problem Statement

The document proposes building an app to help Spotify users discover new music within their community by accessing and analyzing users' Spotify data. It would aggregate Spotify listening data from users and generate insights like most popular songs, artists, and genres among the community. This would help users find music that resonates with their network and potentially make new friends. The app would use Spotify's APIs to store users' music preferences after they log in. It would then apply algorithms to the aggregated data to provide personalized recommendations and community charts to users.

Uploaded by

Anujain Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Spotify Project

Problem Statement
- For existing users
o Help discover and share new music within the community by attributes like artists,
genres etc
o Get period specific insights on which music is popular amongst the community by
attributes like artists, genres etc
- New user acquisition (Network Effect)
o Help bring new users to the platform who want to be a part of the community and
explore others music preferences.

User Personas (Subject to validation post Primary Research)


Gayathri, 25 years old
Background: At a new job, she is from a different country and speaks a non-native mother tongue.
Goals: Music being a universal language, she wants to know what her community is listening to. So that,
whenever she attends the next social gathering, she can feel at home and have music in common as an
icebreaker to help her network.
Karan, 23 years old
Background: Karan has recently been admitted to one of the top MBA colleges of India.
Goals: He is looking for one common thread across the batch to build a feeling of camaraderie as they
begin their B school journey. He is looking for a way to know what music or song resonates well with
everyone and declare that as the cohort song to bring them closer.
Sahana, 27 years old
Background: Sahana has been an avid Spotify user and likes to explore new music.
Goals: Having used discover weekly exhaustively, she still feels she is not able to completely discover the
new music that people in her network play and find the ones she likes. She tried the collaborative playlist
feature, but the playlist always ended up being skewed by the music taste of that one person who is super
excited to add hundreds of songs.

Primary Research (Survey)


Design a survey to understand Spotify usage within the community broadly covering listening habits and
preferences. Understand whether the concept of providing the login token to use the service is accepted
by the audience, and gauge the need of the service in the ISB Cohort.

Secondary Research (Survey)


Probable competitor analysis
• Explore the Follow Friends feature on Spotify Premium, which basically gives us a list of what
our friends is listening to (but this is granular as opposed to community level)

Proposed Approach
Build an app/web-interface for people to share their Spotify data access. We extract the relevant data
and publish multiple data cuts and use them as an input for other features

A glimpse of the proposed outcome


- Multiple data cuts for the cohort (Similar to what Spotify shares for India and individual user): Monthly
charts, most played songs, most played artist, most played genre, people who played songs similar to
you and more.

- Discover people in the cohort with similar music interest as yours and maybe send a Hi5 and attend
concerts together.

- A discussion on potential ways to monetize: Eg - As Spotify sell this service to corporates/orgs (How
Slack reaches and resonates with all kinds of companies)

Some Metrics that can be used


- User Engagement for existing users
o Increase in daily active users
o Increase in playtime/user
o Increase in taps on suggested category songs
- For new users
o Number of new signups

Potential benefits to Spotify (If you were to pitch as a PM)


- Build higher user and community engagement. (People will use Spotify more over other services to
ensure their music taste reflects on their community: human psychology. You can draw parallels with
how people want to look and project their best on IG to build a perception in their network and
community)

- Bring new users to discover what their community is listening to. (People will join in to see what their
community is listening to, allowing the new user to explore your product - the network effect is one of
the strongest)

- For existing users, the charts will show what others are listening to. [Extension to Discover Weekly]
(like what Netflix does with Trending and Top 10, to replicate this in songs for Spotify it is very difficult
given the sheer # of songs that exists. The product will potentially offer the same effect but at their
community level rather than India level)

-Potential to make more friends through similar Music choices and come up with a Social Media
platform for Music interests in future
Possible Roles and Tasks Breakdown
Developers
- React + Django (Web development)
- Deployment
- Experience in Postman

Data analytics
- R/Python/SQL (Preferred)

PM
- User research
- PRD

People with limited or no experience in PM or coding


- Ideas on new features
- User experience
- A/B Testing

Implementation details (As per current understanding)


Spotify provides APIs where we can get the relevant information of a particular user who has logged in
but not any random user (using his publicly available user id). Another issue is that the sign in
mechanism is in such a way that the authentication will be timed out after some time. So, we cannot
persist the authentication details and query for the user at a later date. Since we are trying to aggregate
the information of the cohort, we need a way where we can store the user information once someone
logs in and aggregate them in a database. This way we can get the details of all the users and apply our
custom logic on them whenever required. It is to be noted that the user info in the database will be
refreshed only when someone logs in again.

Link to Spotify API documentation: https://developer.spotify.com/documentation/web-


api/reference/#category-users-profile

UI Framework: React JS

Backend framework: Django (python based)

DB: Anything that is easily supported by Django as the data is going to be lightweight at low scale

Backend rest APIs needed:


1. Store user info – The server is supposed use the APIs related to user info and store them in a
database.
2. Fetch cohort data – Get the data stored in the database and apply the custom aggregation
algorithm and send them in a json format.

Steps:

1. User logs in
2. Perform a call to server to store user related information (as it won’t be available once the log-in
times out
3. Then fetch data from server
4. Populate the data in the UI templates

=====================================================================================

Meeting Notes 23/06:

• We can view our personal user info – interests, songs listened to


o Explore Facebook/google login
o Drawback – temp login – expires after a while, user data anonymity
▪ Can be possibly solved by getting location level data
o Product requirement – we need dynamic real time data flowing in

• 2 sides to this
o Web UI – log in, fetch user info, store in database
o Deploy server – have database in backend server, have two apis – one for fetching user
info and fetching info of other users to show to user in UI

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy