spotifyd VS nvim-spotify

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

I'm using astronvim and was having trouble setting up the nvim-spotify for the Heirline status bar. Could someone help me?

Now the [nvim-spotify](https://github.com/KadoBOT/nvim-spotify) plugin is a wrapper for `spotify-tui`. In other words, it doesn't implement Spotify client logic anymore. While this creates a dependency and blocks the plugin in terms of new features, it also gives me less code to maintain (and fewer bugs) while using a tool that is already battle-tested and used by many users.

Like most of us (devs), I listen to music while coding. And like most of us (neovim users), we value our productivity. So, as a hobby, I've built a Spotify plugin, so I can control it without leaving nvim. While displaying the results with Telescope.