spotifyd VS com.spotify.Client

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

There is nothing "unsafe" about flatpak. In fact for every package on flathub you can see exactly what the "unofficial" packagers do in the corresponding github repository. For example here is the repository for Spotify, if you look at the json manifest file you can see they are repackaging the "official" Snap with the necessary libraries and scripts to support it running as a flatpak. Everything there is open source and able to be examined.

If you click on the "Manifest" link for the package on flathub, it will take you to where the code that packages the app resides. There you can review exactly what the packager does in the json manifest. Here's the one for the Spotify client, for example, which shows where it pulls in dependencies and where it downloads the proprietary code from (in this case they base it on the snap) and what commands it executes while packaging the flatpak.

Try installing it via Flatpak

Flatpaks builds are made to be reproducible. Everything is done openly and you can check how the apps like for example Spotify where made.

Why not just use the flatpak?

Judging by the manifest, the Spotify Flatpak is built from the Spotify Snap.