psst VS minivorbis

On the other hand, this Rust-based one called Psst looks awesome and works: https://github.com/jpochyla/psst

Psst but currently very limited in features and have to build yourself.

psst, https://github.com/jpochyla/psst

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

You can also take a look at Psst. I use Symphonia for decoding and CPAL or CubeB for output. CubeB is a bit nicer.

There‘s a Spotify client, psst, which has an Async widget (with a Promise state struct) that works very well for loading states etc. That project has a bunch of other tidbits and interesting patterns for Druid, I learned a ton from the code.

Not that I'm in any way suggesting that you have to have to pursue this, but I'd suggest that not having this as a goal is why it hasn't happened. I've seen apps built with Druid (like https://github.com/jpochyla/psst) and they look great. But when I looked into the documentation, I was really struggling to get started. In contrast, libraries like Iced are quite limited in what they can do and are not as architecturally sound as Druid, but seem to have put more effort into the onboarding experience and documentation for beginners (see also: the effort that Rust itself puts into being beginner friendly, and how that has enabled it jump into the mainstream where other similar languages have remained niche).

The Psst spotify player is just awesome.

I love the idea and want to try it but run into a minivorbis dependency problem. I found a repository minivorbis and it suggests copying minivorbis.h into ones source directory after generating it. I copied it into your minivorbis-sys/src directory but it is not expected there. Can we get a hint? Thanks!