Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Spotify with Team Groove #18

Open
stiffneckjim opened this issue Feb 23, 2021 · 0 comments
Open

Use Spotify with Team Groove #18

stiffneckjim opened this issue Feb 23, 2021 · 0 comments
Labels

Comments

@stiffneckjim
Copy link
Contributor

stiffneckjim commented Feb 23, 2021

For Team Groove to be able to independently drive a play list it needs access to music. This means it either needs to be integrated with at least one music streaming service or have access to music files some other way. The plan is to start with Spotify because it has a convenient Web API, an extensive catalogue and a free tier for membership.

The steps to integrating with Spotify include:

  1. Authenticate Team Groove with Spotify - this is authenticating the application itself but will require an active account on Spotify that will need to linked by the person setting up Team Groove
  2. Populate a play list with a play list from Spotify
  3. Add tracks by searching Spotify and adding them to Team Groove play list
  4. Play tracks in Spotify according to the votes they have received from Team Groove

Assumptions

Team Groove will store play lists locally but these can be populated from Spotify.
There is no synchronisation between Team Groove and Spotify.
When a play list is pushed from Spotify to Team Groove, Team Groove will check all the tracks in the play list are valid, including discarding duplicate tracks.

@stiffneckjim stiffneckjim changed the title Play tracks in Spotify according to the votes they have received Use Spotify with Team Groove Mar 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant