[Toreno96]

> you can only have playlist of songs. There's no way to collapse songs of a single album to one entry.

You could add the whole albums to the playlist, one by one, and then play the playlist w/ shuffle disabled. This last bit makes it a limited workaround, however.

On the other hand, Spotify API could allow to implement the custom solution to shuffle these, similar to https://spotifyshuffler.com/, if you have enough skills, time, and determination to do that.

[cropcirclbureau]

I'm not using the playlists as a list of songs to listen to in one session. These are issues that come to the fore when you start using them as an organizational primitive. It's more limited than you think in that sense. For example, let's say I have a 20 album playlist. A very usual affair for me as I compile a single playlist for one month or a season. 20 albums comes around at 200 files. That's an ungodly amount of scrolling right there. (my seasonal/monthly actually average around 50 albums). Now imagine how painful it'd be for my long running playlists with hundreds or even that one playlist of mine with thousands of albums?

One workaround that I and other users make use of is to just add the first track of albums as links to the albums themselves. It's whatever. It's a bit stupid this is something I have to fucking deal with in the biggest music interface that the planet makes use of. Anyways, I mainly mentioned that as example of the ethos of Spotify UI/UX and what kinds of user they're primarily catering to. I guess I'm in the excluded group in this implementation of "worse-is-better" or something. (Is there a term for that group? Power user can't cover it because people with disabilities are usually in it.)