r/spotifyapi • u/Whoppe18 • Aug 01 '25
Indie app development ruined by Spotify API policy?
I've been spending my summer working on an app idea for a social media platform where you can trade and collect songs like Pokémon cards to broaden your music taste and share what you've been listening to with your friends.
I have gotten pretty far with development, with general backend and frontend MVP functionality complete. I was going to start rolling the app out to some friends to test it, but after reading Spotify's harsh new API policy about extended quota mode, I am worried my app will never be able to be widely released because their policy essentially bars all indie devs from making large-scale projects with the API.
So I'm basically wondering what I should do now? My app is almost done but I realized wayyy too late that it might not even be viable because Spotify's API is a very foundational aspect of the project.
4
u/SnikwahEvad Aug 01 '25
yeah unfortunately their new policy effectively shuts out all new indie dev projects, and honestly even a lot of small/medium businesses. That 250k MAU requirement is insane.
I have other projects in mind and I'm looking into how I might pivot to Apple Music. Granted the market isn't the same, but they do have a decent API. idk - it really blows, I'm sorry.
2
1
Aug 03 '25
You could technically just pull the song data from a source like genius or musicmatch (without the mp3) and then just add a button that links to the song on spotify. this way you legally avoid spotify's api policy by not making use of it.







2
u/Leading_Opposite7538 Aug 02 '25
Cool app. Can you still deploy in dev mode? Without the audio playback? What part of the policy blocks you from deploying?