Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Remote playback SDK and commercial SDA question

Remote playback SDK and commercial SDA question

So our app is a commercial app that has a free and paid subscription tier, and our use case was to play videos in our app, and if the user selected spotify as a music source, we muted our audio and provided an in-app player to control spotify playback. 

 

It was rejected understandably as we didn't know at the time of applying. We are now going to remove using the in-app player that uses "app-remote-control", which means we are no longer using the remote playback SDK. Based on my understanding, this means we are no longer considered a streaming SDA.

 

For this new use case, this means we don't even need an integration since users can just play Spotify independently and our app would just provide a link to spotify and direct them to play music there and return to our app.

 

However, when reading a similar post in the forums (https://community.spotify.com/t5/Spotify-for-Developers/Questions-regarding-quota-extension-rejectio...), they have a similar use case of being able to read and modify playlists, and have playback controls. They said they were going to remove playback controls and the response states that they would be fine after removing it for their remaining use case of reading/modifying playlists.

 

So my question is whether only "app-remote-control" is considered as remote playback that is not allowed for commercial apps. If we only used "user-read-playback-state" and "user-read-currently-playing", would we be fine to request for a quota extension and be approved?

Reply
0 Replies

Suggested posts