Spotify put the final nail in the coffin for our two-year vision.
Yesterday, Spotify published changes regarding Developer Access and extended quotas for their API.
These changes completely shut down operations based on the Spotify API if you have more than five users, literally.
So they've left only a small space for experimentation, while giving full-fledged access to big businesses with "commercial liability" and >> 250k MAU.
We've been using the Spotify API for different parts of #SFScoop , and honestly, it was held together with duct tape due to previous restrictions and complications with dev mode and extended quotas.
We started thinking about getting rid of Spotify a while ago, and it seems Spotify was thinking the same way.
Well, it's about time.
In February, we will deploy planned major changes aimed at making SFScoop self-sustaining.
February will be another major milestone on the SFScoop roadmap.
Yesterday, Spotify published changes regarding Developer Access and extended quotas for their API.
These changes completely shut down operations based on the Spotify API if you have more than five users, literally.
So they've left only a small space for experimentation, while giving full-fledged access to big businesses with "commercial liability" and >> 250k MAU.
We've been using the Spotify API for different parts of #SFScoop , and honestly, it was held together with duct tape due to previous restrictions and complications with dev mode and extended quotas.
We started thinking about getting rid of Spotify a while ago, and it seems Spotify was thinking the same way.
Well, it's about time.
In February, we will deploy planned major changes aimed at making SFScoop self-sustaining.
February will be another major milestone on the SFScoop roadmap.