2 ms·
> Stamp is in violation of Spotify’s Developer Terms, which prohibit developers from integrating Spotify Content (including metadata) with third-party services
by solarkraft 8y ago
> Stamp is in violation of Spotify’s Developer Terms, which prohibit developers from integrating Spotify Content (including metadata) with third-party services
So ... It's forbidden to use Spotify's API?
I currently stay with Spotify because of its decently good UX (despite constant, nonsensical A/B testing) and because I had the impression they were behaving well. This perception is fragile.
I'm not sure making your service less attractive to users will increase your stock price either.
- bartoszhernas 8y agoIt's was always ok to use their SDK and make money as long as you did not make money from music listening. We make money from user playlists data (which we believe should belong to user) and I don't treat our usecase as integrating with others, as we do it in 3 steps: download from Spotify, then import to somewhere else. It was all fine for 2 year, but after IPO they changed their TOS for Developers. There was either making our service less attractive or removing Spotify all together, so we had no choice. Don't really care about stock price ;), just want to keep the project going and allow others to be able to migrate between different services. I like that with email on your own domain you can easily switch providers (which I recently did with google to protonmail). But there are many other solutions which are not so easy to switch which halts competition.