Fastpotify: Rust Spotify Client Uses 75% Less RAM

Fastpotify sat on the top of Hacker News today — 791 points, 523 comments — and crossed 1,500 GitHub stars in five days. The pitch fits in one line: a native Spotify client written in Rust with egui that uses 100–250 MB of RAM while Spotify's desktop app burns 600 MB to over 1 GB. It starts in under a second and has no browser engine.

What shipped: a full Spotify client in Rust

Fastpotify is not a wrapper — it is a full client. Playback runs through librespot, the open-source Spotify Connect implementation, so the app works as a Connect device: pick it from your phone, or cast to speakers on your network. It supports gapless playback up to 320 kbps, an on-disk audio cache, playlist editing, search, artist pages, and a queue. MIT-licensed, cross-platform (Linux, macOS, Windows), and it even ships a Winamp mini-player with classic .wsz skins.

Why it matters: the bloat backlash gets a target

The number that matters is the 523-comment thread on HN. Users are not debating features — they are complaining about RAM, and Fastpotify's 100–250 MB headline number is the rebuttal to every Electron rebuild of Spotify's 1 GB footprint. Native Rust clients were hobby projects; this one shipped a store-grade feature set with real adoption in five days. It is the pattern that ends blob apps: one motivated rewrite, one number people can feel, and the incumbents stop being forgiven for it.

The verdict

Fastpotify is the strongest signal this week that desktop bloat is breaking open. Worth your 2 minutes: install it, watch the RAM delta, then see whether Spotify's lawyers and Electron apps start moving. Native speed as a feature, not a constraint.