spotifyd VS libspotify-archive

For those unaware, it's possible to use alternative clients for Spotify using a 3rd party daemon.

https://github.com/Spotifyd/spotifyd

[Unit] Description=A spotify playing daemon Documentation=https://github.com/Spotifyd/spotifyd Wants=sound.target After=sound.target Wants=network-online.target After=network-online.target [Service] ExecStart=/usr/bin/spotifyd --no-daemon Restart=always RestartSec=12 [Install] WantedBy=default.target

you don't need another frontend. preferred client to handle streaming for spotify-tui is spotifyd.

If you're using a premium account, you could also try to use the browser to control and spotifyd to play: https://github.com/Spotifyd/spotifyd

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 there.

Spotifyd runs on Linux, can also be recognized by Spotify app as an output requires premium, not sure about touch screen compatability

The integration of Spotify, the great daddy of audio streamers with third-party apps has been difficult over the years. Years ago, in their beginning they liberated libspotify, coded in for integration with different clients. Integration with major audio players like Foobar, Clementine and MusicBee were working, but in 2015 the company decided to drop the new development on the library and decided to shut down the integration last June. The new feature called Spotify Connect that allows multiple device to act as remote controller for the device that its playing in real time made new possibilities. But the wheel was inventend with LibReSpot, a library written in Rust. More libraries ported from the original in Rust appeared later in Go and Java. This last one is special, since it allows to be controlled by HTTP requests and interacts with a potential client through WebSockets. So a good player is possible to be built through a GUI library, and so I picked the most user friendly GUI framework, PySimpleGUI, that wraps multiple and more complex GUI frameworks like Tkinter and PyQT providing easyness of development.

Others have been suggesting Libspotify still works for legacy embedded device reasons... https://github.com/mopidy/libspotify-archive seems to have Android and iOS builds.