Make Spotify truely optional espacially on first start

[asperling]

Is your feature request related to a problem? Please describe.
The Readme as well as the website mentions that Spotify is optional. But even though I couldn't get Spotatui to play local files or music from my navidrome server. On startup I was presented with two options to connect to Spotify, both resulting in me having to login to Spotify. When canceling via CTRL-C and starting Spotatui up again the inital setup process wasn't presented again, instead an empty player was shown.

Then I went and configured both the path to my local music library as well as the connection information to my navidrome server. Starting up spotatui again didn't change anything - showing me nothing and stating nothing was configured.

This is when I abandonded my test as there are alternatives that are way easier to setup and use. But I wanted to give some feedback why. (I was initially intrigued because of the premise of mixing sources in playlists)

Describe the solution you'd like
A clear way on first setup to configure any (or at least one) source of music that does not necessarily has to be Spotify. Additionally include those providers in the settings screen and show the state as not setup/connected or available/connection failed or none found with information on why if the state is failed.

Describe alternatives you've considered
I am using NaviTui and CliAmp for now.

Additional context
Installed via cargo install --locked spotatui on CachyOS/Ghostty/fish.

[spotatui]

🎧 spotatui triage

Auto-triaged with DeepSeek V4-Flash.

Label: enhancement
Likely area: first-run setup flow for non-Spotify sources (local files / Navidrome)

Summary

The reporter says that although the README and website describe Spotify as optional, they could not get spotatui to play local files or music from their Navidrome server. On first start they were only offered two Spotify login options, cancelling with CTRL-C and restarting skipped the setup and showed an empty player instead, and configuring a local library path and Navidrome connection produced no visible change. They abandoned the test and are asking for a first-run flow that lets users configure a non-Spotify source, with those providers exposed in settings and clear connection state reporting.

Key points

• Feature request: make Spotify truly optional, especially during first-run setup
• First start presented two options that both required logging in to Spotify
• Cancelling via CTRL-C and restarting did not re-show initial setup; an empty player appeared
• After configuring local music library path and Navidrome connection, startup showed nothing and reported nothing configured
• Installed via cargo install --locked spotatui on CachyOS / Ghostty / fish

What would help

• spotatui version installed
• Exact steps and syntax used to configure the local library path and Navidrome connection
• Any log, console output, or error messages produced at startup or connect time
• Whether a config file was actually written and where

Possible duplicates

• Injectable filesystem roots for core::paths to unit-test first-run flows #461 (low) — Also concerns first-run flows (unit-testing them), but is a distinct testing-related request, not the same onboarding/source-configuration complaint

_{Compared against the 31 most recently updated open issues.}

[LargeModGames]

This is something I have been working on for a while already but it will still need more time. When i forked spotify-tui spotify was integrated into almost everything. I didnt think about adding other sources until later so it will take some more time to make spotify completely optional, but I am definitely working on it.

[asperling]

Even though I will not use it for now I'm sincerely happy about your effort. This was not meant as a rant, really, only to give some feedback. Since you have already plans to improve on this I will close this and will come back later to give it a try again. Thanks!