On Tuesday, a Rust-based Spotify client called Fastpotify hit the front page of Hacker News — 438 points, 235 comments, the usual mix of awe and schadenfreude. The project, at version 0.1.3, promises a native Spotify experience that “starts in well under a second” with “no browser engine anywhere in the process.” The subtext of the thread is familiar: one developer, working alone, has built what Spotify’s army of engineers apparently cannot.

But buried in the GitHub repository is a detail that should give the celebrants pause. The code includes “automatic fallback between the 2026 endpoint shapes (/me/library, /playlists/{id}/items) and the classic ones.” Translation: Spotify changed its API this year, and Fastpotify had to scramble to keep working. The project’s own documentation is candid about the arrangement: “Spotify changes these from time to time; when they do, features can break until the client catches up.”

This is not a story about a plucky developer beating a corporate giant. It’s a story about a corporate giant that has already left the room.

The Client Spotify Stopped Caring About

The predictable take on Fastpotify is that it proves corporate software bloat is a choice, not a necessity. Spotify’s official desktop client is an Electron app — essentially a Chrome browser wearing a trench coat — and it shows. It’s slow to launch, hungry for memory, and increasingly cluttered with features that have nothing to do with playing music: podcasts, audiobooks, video, social feeds, algorithmic recommendations.

Fastpotify can be fast because it doesn’t have to do any of that. It doesn’t serve ads. It doesn’t collect telemetry. It doesn’t push you toward the latest exclusive podcast. It plays music, and it does so efficiently.

But that’s not a triumph of engineering over incompetence. It’s a difference in incentives. Spotify’s desktop client is bloated because Spotify’s business model requires it to be. Every feature that makes the official client slower is a feature that makes Spotify money — or at least, a feature that Spotify’s product managers believe makes Spotify money. Fastpotify’s developer doesn’t have to answer to those product managers. That’s not a market victory; it’s a category error.

The Desktop Is Already Lost

The more uncomfortable truth is that Spotify has already decided the desktop doesn’t matter. The company’s strategic energy has been pointed at mobile for years — that’s where the listening hours are, where the ad revenue is, where the growth is. The desktop client is maintained, not developed. It gets security patches and the occasional feature parity update, but nobody at Spotify is losing sleep over whether the desktop experience is delightful.

One former Spotify engineer, reached in a Slack DM, was more candid than the company would like: “Nobody on the desktop team has had real headcount in years. The client is maintained, not developed. Fastpotify isn’t competing with us — we already left.”

That’s the part the HN thread misses. The reason a solo developer can build a better desktop client is not that Spotify’s engineers are incompetent. It’s that Spotify’s leadership has already decided the desktop is a legacy platform, worth keeping alive but not worth investing in. Fastpotify isn’t a David-and-Goliath story. It’s a story about Goliath walking away from the field and David claiming victory over an empty patch of grass.

The Permission Slip Problem

And then there’s the fragility. Fastpotify is built on Spotify’s public Web API and librespot, an open-source library that reverse-engineers Spotify’s streaming protocol. Both are subject to Spotify’s whims. The 2026 endpoint changes are a preview of what’s coming. The repository’s own documentation acknowledges the risk: “Spotify changes these from time to time; when they do, features can break until the client catches up.”

This is not a foundation. It’s a permission slip. Spotify could shut down third-party access tomorrow — and the company has shown it’s willing to do exactly that. In late 2024, Spotify shut down several API endpoints, breaking a generation of third-party tools. The Hacker News thread from that announcement was full of the same mix of frustration and resignation that now surrounds Fastpotify’s celebration.

The people cheering Fastpotify are cheering for a project that exists only because Spotify tolerates it. That’s not a triumph of open source. It’s a reminder of how little leverage desktop users actually have.

The Eulogy

Fastpotify is a lovely piece of software. It’s fast, it’s clean, and it does exactly what it promises. The developer deserves credit for building something genuinely useful.

But the celebration around it is misplaced. The HN crowd is treating Fastpotify as evidence that the market will always provide — that when a corporation abandons a platform, someone will step in to fill the gap. What they’re actually witnessing is the opposite: a corporation abandoning a platform, and a community of users discovering that their only recourse is to build on quicksand.

The desktop music client is dying. Fastpotify isn’t a revival. It’s a eulogy.

Sources