We have chosen Music Organization Service as our project domain.
Use cases include the following:
- sign-up
- login
- create playlist
- delete playlist
- search for track
- like track
- add track to playlist
- unlike track
- remove track from playlist
- search for artist
- follow artist (a playlist of their top tracks will be added to your library)
- unfollow artist
- search for friend
- add friend (you will be able to view their playlists in your library)
- remove friend (their playlists will then be removed)
All code follows SOLID design principles and CLEAN architecture (use cases have individual controllers, boundaries, interactors, and presentors)
We use the following Spotify API endpoints in our project
/token Credentials Documentation
- retrieve access token using environment variables SPOTIFY_CLIENT_ID and SPOTIFY_CLIENT_SECRET
/search Endpoint Documentation
- display results from searching (tracks and artists)
/tracks Endpoint Documentation
- save track on like/add to play list
/artists Endpoint Documentation
- save artist on follow
/artists/{id}/top-tracks Endpoint Documentation
- generate "best of" playlist on artist follow
Signup View (no errors displayed)
Signup View (username taken error)
Signup View (password mismatch error)
Login View (no errors displayed)
Login View (account does not exist error)
Login View (wrong password error)
Playlist View (viewing "Liked Tracks")











