MyNeedEcho
Home › "I made my own Spotify"
Updated 2026-11-13

"I made my own Spotify"

Why this matters: So I've had Spotify for years and I'm just used to how it looks, so I made my own self-hosted version. Did I do it by myself?... Confirmed by 1 original posts across 1 communities and 3 stated pain points below.

So I've had Spotify for years and I'm just used to how it looks, so I made my own self-hosted version. Did I do it by myself?...

🔥 Heat 5.92 1 evidence posts 3 pain points 2026-11-13
Mention 1.5 · 1 sources

Evidence (1 posts)

Reddit · r/selfhosted "I made my own Spotify" 💬 5

Pain points (3)

“So I've had Spotify for years and I'm just used to how it looks, so I made my own self-hosted version.”
→ Build a self-hosted music server that replicates the familiar Spotify UI so long-time users don't have to relearn a new interface.
“Why not Navidrome? It's great, I just wanted something as”
→ Build a self-hosted music player that matches the polish and feature set of existing tools like Navidrome while adding missing conveniences.
“It also hooks into Lidarr and MusicBrainz, so I can search for something I don't have and request it right in the app.”
→ Build in-app music discovery and request workflows that connect to Lidarr and MusicBrainz so users can find and acquire missing tracks without leaving the player.

Sub-directions

Self-hosted music streaming servers with native desktop and mobile appsAI-assisted personal software cloning of mainstream appsMusic library automation via Lidarr/MusicBrainz integration and in-app requests

Related needs

FAQ — "I made my own Spotify"

Is there real demand for "I made my own Spotify"?

Yes. This need is backed by 1 original posts from Reddit within the past week, with a mention score of 1.5 across 1 independent sources and 3 specific pain points. Every quote on this page links to its original post, so each claim can be verified directly.

Who is frustrated by this problem?

People actively discussing this include: Long-time Spotify users who self-host their music; Self-hosters evaluating existing music servers like Navidrome; Self-hosted music collectors managing large personal libraries.

What are the concrete build opportunities?

The specific sub-opportunities extracted from real discussions are: Build a self-hosted music server that replicates the familiar Spotify UI so long-time users don't have to relearn a new interface; Build a self-hosted music player that matches the polish and feature set of existing tools like Navidrome while adding missing conveniences; Build in-app music discovery and request workflows that connect to Lidarr and MusicBrainz so users can find and acquire missing tracks without leaving the player.

How is this data collected and verified?

We collect real discussions daily from Hacker News, GitHub, DEV.to, Product Hunt, Bluesky, Reddit and Stack Overflow, plus EU (TED) and US (SAM.gov) public tenders. Every trend passes a two-stage anti-fabrication check: quotes are matched character-for-character against their source post, and every link must point to the actual evidence thread. Unverifiable content is discarded before publication.

How current is this data?

The report is regenerated every day at 09:00 UTC. This page was last updated 2026-11-13, built from discussions gathered within the most recent 1-day window.

See all 20 evidence-backed needs this week — updated daily, every trend traced to original posts and exact quotes.

Subscribe $19.99/mo →

Not sure what to build first? See the ten worth a look →