Spotify Wrapped.
All. Year. Long.
Let Unwrappd Create Spotify Wrappeds For You On-Demand!
01
Create a custom Spotify Wrapped
Choose the length of your Wrapped, whether it's 1 month, 6 months, or a year.
02
Check out your faves
Rewind and listen to your favorite artists, top genres, and most listened songs!
Save all your Wrappeds, in one place
Every Wrapped you create with Unwrappd is saved directly onto your mobile device. Check it out whenever you're feeling a little nostalgic!
03
Meet the Team
Together, we make up Team 1 of CS 2340 Section C. We worked together to make Unwrappd a possibility for music lovers around the world.
A Quick Overview of Our Process
Key Points
-
The team is comprised of product owner, Zain; scrum master, Akash; a technical support team led by Vignesh; scribe Dhairya; with the rest of the team as main developers, all following Agile methodology.
-
In Sprint One, they focused on base stories 1 and 2, and user stories 10 and 13, establishing the application's foundation and setting up Git and PR templates.
-
Sprint Two involved tackling user stories 8, 5, and 12, allowing them to store user information in Firebase and create a top songs and clips feature.
-
Trello boards were used for ticketing and responsibility allocation, later transitioning to Discord for efficient client communication.
-
Weekly meetings with the client were held, and Slack was utilized for planning and goal setting.
How We Built Unwrappd
Sprint 1:
In the initial two to three weeks post-launch, Sprint 1 focused on establishing a solid project foundation. Core user stories were prioritized, including integrating essential features like git and GitHub for version control and efficient collaboration. Daily standups via Slack and Discord facilitated progress tracking and team communication. A comprehensive sprint review and retrospective concluded Sprint 1, identifying areas for development process improvement.
Sprint 2:
Transitioning into Sprint 2, spanning another two to three weeks, emphasis shifted to completing critical user stories and seamlessly merging frontend and backend components. User Stories 5, 8, and 12 were prioritized, advancing the project toward completion. Significant effort was dedicated to integrating frontend and backend systems, culminating in successful achievement of user story objectives and completion of system integration midway through the sprint.
Design Decisions:
Strategic planning during Sprint 1 laid the groundwork for design decisions. Tools like Trello facilitated task organization and communication. Division into backend and frontend teams streamlined development efforts, while prototyping tools like Figma aided in refining the user interface. Detailed class outlines and adherence to GRASP principles guided system architecture, enhancing code maintainability and facilitating integration with external APIs like the Spotify API.