For this screen, our goal is to restrict access to the rest of the app until users log in. This simple screen serves as an introduction to our app while also prompting users to log in using their Spotify credentials. By addressing User Story #1, this screen provides users with the essential functionality to access their personal Spotify account.
In this screen, our focus is on addressing User Story #2. In this scenario, users are eager to access their past Spotify Wrapped summaries. Each summary from previous years is interactive, allowing users to click on them to delve into more detailed descriptions of their listening statistics.
In this screen, simplicity was our priority once again. We provided users with the option to customize the time frame for generating their wrapped summary (user story 8). This straightforward approach empowers users to tailor their experience according to their preferences.
In this screen, users can explore their Top Songs, Top Artists, and Top Genres. Each category showcases up to 20 entries, allowing users to delve into their musical preferences. As premium users navigate through the content, a loop of their top songs plays in the background, enhancing the immersive experience (user story 5).
In this screen, we once again address User Story #2 by making it our aim to provide users with a straightforward method of accessing their account information. The 'Name' corresponds to the user's display name on Spotify, while the 'Username' is automatically generated by Spotify and is unique to each user. The Spotify Account refers to the user's email linked with their Spotify account.
When users log in to Spotify through the app, their 'Name' and 'Username' are automatically generated. However, users have the flexibility to edit this information exclusively for the app, and they also retain the option to delete their account if they wish to erase all previous wrapped history. Additionally, users can choose to log out without their data being deleted.
We use Firebase to store user data on a cloud platforming allowing for account information to persist across devices (user story 12).
We used GitHub actions to check branches compatibility before allowing merges (user story 5). We also included templates for issues and pull requests (user story 1).