A while ago, I shared here MusicStonks.com, a browser-based game I'm working on where users track the “stock value” of musical artists over time, based on actual popularity metrics. Think of it as a simulation game where fans can build portfolios of artists they believe will grow.
The core of the game is already live:
✅ You can register, buy “shares” in artists, and see how your portfolio evolves
✅ Artist popularity is tied to real data
✅ The UI tracks performance over time with charts and rankings
What I wanted to build next was a personalized dashboard powered by Spotify:
Let users log in with their Spotify account
Pull their most-listened artists
Show how those artists are performing in MusicStonks
Make onboarding feel tailored and instant: “Here’s how your music taste would perform in the market.”
Technically, I got everything working: OAuth flow, tokens, top artists, integration with the backend.
It looked promising — and very usable.
But then I ran into Spotify’s new policy wall.
---
The Spotify Limit You Might Not Know About
Since May 15th, 2025, Spotify only allows apps to go into production mode if:
You’re a registered business
Your app has 250,000 monthly active users
You apply via corporate email
Otherwise, your app is stuck in development mode with a strict limit:
→ Only 25 Spotify users total, and each one must be manually allowlisted.
Even if other users complete the login flow, Spotify will block API calls for their tokens with a 403 error.
So despite having the integration working, I can't ship it.
And I won’t bother rolling it out for just a handful of testers.
---
What This Means for MusicStonks
I’m shelving the Spotify integration. It’s not viable unless I turn this into a company and reach serious scale — which is not where I am right now.
Instead, I’m moving forward with features that are fully under my control:
🏅 Achievement system (badges, milestones, progress)
📲 Push notifications to help users follow artist trends and events
🎧 Manual favorite artist selection to seed a personal dashboard
📱 Native app version — I’m building for Android/iOS to reach music fans outside the browser
---
Takeaways for Other Indie Makers
APIs are not guaranteed infrastructure — always check for usage limits and production requirements
Development mode ≠ production-ready — test the policies, not just the code
Don’t assume “just plug in Spotify” is a weekend feature
If your feature depends on a platform, be sure you can scale it before investing too much time
---
If you’re building something similar or had to rethink a big feature because of an external dependency, I’d love to hear how you handled it.
And if you want to try out MusicStonks as it is today (Spotify or not), you can check it out here: https://musicstonks.com