Spotify-qt VS PSST

If you want to run Spotify on a Raspberry (or PinePhone or some other device), there’s Spot, which is great, but kinda heavy and slow. There’s Spotify-qt which is faster, requires messing with Spotify developer dashboard, and UI doesn’t fit on small screens. Spotify-qt is itself based on Spotify-tui which runs in the terminal (pretty cool IMO). And a bare client/daemon is spotifyd. So you have quite a few choices... Source: over 1 year ago

Would like to add that you can also use clients such as spotify-qt and Spotify TUI to control said "device". There's also Spot and psst that are standalone (librespot not required but no Connect functionality). Source: over 1 year ago

I have been using spotify-qt[1] lately. It's quite close to the original client from more than 10 years ago. 1. https://github.com/kraxarn/spotify-qt. - Source: Hacker News / almost 2 years ago

You could use an an unofficial client, for example: - Spot (GTK, can stream directly) - spotify-qt (QT, just a Spotify connect frontend, so you need something like spotifyd running) - spotify-tui (terminal, again just a Spotify connect frontend) - spotifyd (daemon that is controlled via Spotify connect). Source: over 2 years ago

On the other hand, this Rust-based one called Psst looks awesome and works: https://github.com/jpochyla/psst. - Source: Hacker News / about 1 year ago

Psst but currently very limited in features and have to build yourself. Source: about 1 year ago

I don't know how can I install this open source software from github. Source: about 1 year ago

Would like to add that you can also use clients such as spotify-qt and Spotify TUI to control said "device". There's also Spot and psst that are standalone (librespot not required but no Connect functionality). Source: over 1 year ago

You can also take a look at Psst. I use Symphonia for decoding and CPAL or CubeB for output. CubeB is a bit nicer. Source: over 1 year ago