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

Is this use case a non streaming SDA?

Is this use case a non streaming SDA?

Hi, 

 

My app is a commercial app (has subscription tier or free app with ads). The use case is to connect oAuth with spotify, and the only thing it will do is display the currently playing song from the spotify in our app. There is only one button that brings the user back to the spotify app if they wish to tap on it. 

 

There is no playback controls or usage of the remote playback API within our app at all. Is our app considered a non streaming SDA and would this be allowed to get a quota extension for?

Reply
4 Replies

Hello! It appears that your application may be in violation of Spotify’s Developer Policy, which states: You must not create products or services that mimic, replicate, or attempt to replace a core user experience of Spotify or its affiliated companies without prior written permission. Your product or service must add independent value or functionality that improves users’ interactions with Spotify.

 

I think, this means that if your app displays the currently playing song from Spotify in real-time, it may be considered a replication of Spotify's content. (but I am not 100% sure)

 

Additionally, please note that the SDA cannot be used for commercial purposes, as outlined in the Developer Terms and Privacy Policy.

 

Hope this helps!

"Limited commercial use permitted for Non-Streaming SDAs. The following are the only permitted commercial uses of Non-Streaming SDAs:

  1. the sale of advertising, sponsorships, or promotions on the Non-Streaming SDA;
  2. the sale of, or sale of access to, a Non-Streaming SDA (including any e-commerce initiated via the Non-Streaming SDA)."


My assumption is that commercial apps are fine if they are considered Non streaming SDAs. As we are not using the remote playback API, or pretty much all the scopes other than reading the user's current playback, the question is whether that individual scope would deem it to be streaming SDA or non-streaming SDA. It seems really difficult to find answers, I've searched through all the existing posts 😕

 

Based on the definition of streaming from https://developer.spotify.com/terms

Streaming” means using the Spotify Platform to enable playback of sound recordings available through the Spotify Service, including using the Spotify Platform to control a background Spotify application. Please note that the use of (i) Widgets or (ii) Audio Preview Clips, are not included in the definition of Streaming for purposes of these Developer Terms."

 

So my uncertainty is whether simply displaying just the song being played is considered streaming, since the definition refers to playback and controls.

 

Hey @Adr182 

Thanks for your question! Based on your description and the Spotify Developer documentation, here are a few insights:

  • Non-Streaming SDA: Your app likely qualifies as a Non-Streaming SDA since it only displays the currently playing song without initiating, altering, or enabling playback. The definition of "Streaming" in the Developer Terms focuses on enabling playback or controlling a background Spotify app, which doesn't seem to apply here.

  • Displaying Song Information vs. Streaming: If your app purely displays song info without affecting playback, it doesn't fall under "Streaming" as defined in the terms.

  • OAuth Scopes: Ensure that your app requests only the OAuth scopes it truly needs. Reviewing the authorization scopes being used can help minimize unnecessary permissions.

  • Commercial Use for Non-Streaming SDAs: Commercial apps can be Non-Streaming SDAs, but their monetization options are limited. Allowed activities include:

    • Selling advertising, sponsorships, or promotions on the Non-Streaming SDA.
    • Selling access to the Non-Streaming SDA (including e-commerce transactions within it).
  • Replication of Core User Experience: Your app should add independent value and not replicate Spotify’s core experience. For instance, integrating the currently playing song into a unique context or supporting accessibility features can align with this guideline.

  • Quota Extension: If your app reaches its quota limit, you can apply for an extension via the provided forms.

  • Compliance with Spotify's Developer Policy & Terms: Full compliance is crucial for eligibility in quota extensions. Spotify’s Developer team reviews applications based on specific criteria, so adhering to the policies increases the chances of approval.

I’d recommend reviewing the Developer Terms & Policy, particularly sections on Non-Streaming SDAs and commercial use. Also, reading through the Design & Branding Guidelines might also be useful.

 

Hope this helps! Let me know if you have any questions

XimzendSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

Thanks for the insights, it's very much appreciated. 

 

Have already submitted my quota extension so fingers crossed we get it approved this time. Thanks!

Suggested posts