Work Flow Option

After reading some Spotify API document, I want to share my idea about the Hype.
### Work flow OR Running logic
##### Explaining
* `Host >login page > Hype Backend > Spotify Server`
1. Login our entry page(localhost:3000/login) to grant our app permission to connect Spotify Server
2. Host tell Hype server the playlist name, then Hype server will get the music list.
* `Spotify Server > Hype Backend Server`
1. After connect successfully, we can get the host’s info (playlist and play state)
2. Store the playlist and play state in our server
* `Guest > Guest Page > Hype Backend Server > Guest Page`
1. When guest open Guest page[get()], server response back the playlist and play state.
* `Hype Backend Server > Spotify Server`
1. When server detect the playlist is changed, then update the playlist through Spotify API
* Every route listing above is doable(Codeable???). They are supported by Spotify API.
### User Interface
This is done by Figma. It is just a sketch. Bear with my poor designing :)
### Problem
* Do we need database?
* Shall we use the starter file ?