WARNING: This is a beta release of the Spotify Android SDK, and can stop working at any time. This SDK release is not suitable for publicly released applications.

Welcome to Spotify Android SDK! This project is for people who wish to develop Android applications containing Spotify-related functionality, such as audio streaming, playlist manipulation, searching and more.

Usage of this SDK is bound under the Developer Terms of Use.

We're releasing this SDK early to gain feedback from the developer community about the future of our Android SDK. Please file feedback about missing issues or bugs over at our issue tracker, making sure you search for existing issues and adding your voice to those rather than duplicating.

For known issues and release notes, see the CHANGELOG.md file.

IMPORTANT: This SDK is pre-release software and is not supported, and must not be shipped to end users. It will stop working in the future.

Yes, the source code for this project is coming very soon! Although the first beta releases will only be binaries, a full source release will follow within a matter of weeks.

Please see the beginner's tutorial on the Spotify Developer Website.

You can generate your application's Client ID, Client Secret and define your callback URIs at the My Applications section of the Spotify Developer Website.

When connecting a user to your app, you must provide the scopes your application needs to operate. A scope is a permission to access a certain part of a user's account, and if you don't ask for the scopes you need you will receive permission denied errors when trying to perform various tasks.

You do not need a scope to access non-user specific information, such as to perform searches, look up metadata, etc. A full list of scopes can be found on Scopes section of the Spotify Developer Website.

If your application's scope needs change after a user is connected to your app, you will need to throw out your stored credentials and re-authenticate the user with the new scopes.

Important: Only ask for the scopes your application needs. Requesting playlist access when your app doesn't use playlists, for example, is bad form.