My three biggest pet peeves are:

- You can't turn your queue into a playlist (and you can't see previous queue as part of the queue, only as limited history.)

- Clicking a song or album sometimes clears your queue and starts playing that instead (I know there is a logic to it, but a mistake or mis-click is easy).

- There is no shortcut to add to queue, just long press then find the menu item.

It's possible everyone else is only listening to albums or curating playlists then playing them, but I like to pick things as I go like a jukebox and it sucks at it.

What I'm missing is multiple "currently playing" lists, each keeping its current position as I switch to play a different one. Use case: listening to a discography of the band, and if I wish to listen few songs from some other band. I can't go back to where I was with the first band. Foobar had multiple ad-hoc lists since forever. Now I balance between Spotify and Youtube music in these cases.

Yeah I really wish there was a global history of my plays that I could look at.

You could link Spotify to last.fm, it saves all your plays.

I request my Spotify data (via their gdpr site) annually and put it in a sql database so I can do my own analysis.

> - There is no shortcut to add to queue,

There is, just swipe the song to the right.

You can also tap the kebab menu and select “Add to Queue”

that's neat! totally not discoverable though

most of the views (in the iOS app at least, idk about android) are asynchronous, in that they will always prefer to load data from their servers over using locally cached stuff.

meaning that, if you have a bad internet connection and tap on eg an album, it'll open the view for that album and you just have to look at the progress indicator for in some cases up to 20+ seconds, even if you have downloaded that album and all the info is there in the local cache.

this happens annoyingly often, e.g. when leaving an area where you're connected to wifi and your phone hasn't yet switched over to celluar data.

I tried Spotify shortly after it was released. It was in a bad shape and missed essentials (e.g. basic filtering by name or in lists) to the point of being unusable. I usually am an avid writer of feedback, but here it was clear to me (sic!) that devs simply lacked resources to implement all the essentials and they were coming in short time.

But imagine my surprise when I checked Spotify a couple of years later and the situation was still the same. Ok, I thought, they must have had different internal priorities, but once they get those, they will make UI at least semi-usable.

A few years passed, but the answer was still no. Once again I didn't write because clearly they must have had thousands of actual users writing and demanding the essentials and those things MUST be on their way, no way they weren't!

Several years later and the situation was still the same... This is when I stopped making excuses for the developers. They must be technically incompetent, be dim product-management wise (not understanding features, people, customers, lacking a vision, not to know how to collect, analyze and work on feedback) or stupid/unmotivated. But probably everything of the above.

I only criticize the technical aspects, not the business side. And I don't even criticize a much more challenging podcast/video side of things. I am merely talking about the lack of essentials in the basic music player. They couldn't even do that! I can bet money that the podcast implementation is on no better level. Other people's comments support that assumption. I am not surprised in the least.