A lot has changed on the Spotify Web API in the past year: deprecated features, increased security, and steep new criteria for extended access, which alienates indie apps. Rather than complain about it, I've put together a report to understand these new restrictions and find practical alternatives. If you have developed with the Web API in the past or are considering building with it in the future, this is a must read.
as someone who worked on a lot of the first and second generation apis at Spotify while i worked there, i'm a bit saddened by where it ended up in the recent years, and the fact that there's still no supported public playback libraries. so much great potential but too many legal issues blocking the availability of streaming music on the internet...
A lot has changed on the Spotify Web API in the past year: deprecated features, increased security, and steep new criteria for extended access, which alienates indie apps. Rather than complain about it, I've put together a report to understand these new restrictions and find practical alternatives. If you have developed with the Web API in the past or are considering building with it in the future, this is a must read.
as someone who worked on a lot of the first and second generation apis at Spotify while i worked there, i'm a bit saddened by where it ended up in the recent years, and the fact that there's still no supported public playback libraries. so much great potential but too many legal issues blocking the availability of streaming music on the internet...