Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
As many of you know, we released the new version of Spotify for Android to the Google Play Store yesterday complete with the following features:
As a result, my first inclination is to change the status of this idea to "not planned". Our logic is this: The wording of the idea suggests that in order for one version of the Spotify app to remain "functionally equivalent", Spotify would actually have to hold back the release of another version of the app.
However, I shy away from changing the status to "not planned" for fear that the status could be misinterpreted as an initiative on the part of Spotify to refrain from updating the Android app in the future, which is certainly not the plan.
I'm going to go ahead and and change the status of this idea to "implemented" in light of the recent release, but I would like to remind folks of the inherent nature of app development and circumstances which could arise which leads asymmetrical development of applications.
Happy listening 🙂