3 ms·
> Worse, for which usecase? For most use cases. > I as a musician like to listen to full albums [...] How does Spotify prohibits you as a musician from liste
by jstummbillig 4y ago
> Worse, for which usecase?
For most use cases.
> I as a musician like to listen to full albums [...]
How does Spotify prohibits you as a musician from listening to an album or reading up on music or looking at music from eras? I detect nothing in any of these tasks that Spotify would make harder than any of the alternativ ways I know of. If anything it should be easier, considering the considerable amount of meta information that resides in Spotify (for example finding music from a specific era or displaying lyrics) and that you don't have to gather yourself.
> How would you do that on spotify?
I wouldn't. I would use foobar for that, because that's the right tool for the job. I also try no get confused about what the job is, what the available tools are and which tool can replace which for a specific job.
- cropcirclbureau 4y agoHere's one reason: you can only have playlist of songs. There's no way to collapse songs of a single album to one entry. You might think it's a little change but it completely devastates the experience if you're someone who listens to whole albums. That's not the only UX hurdle if you're someone who curates a library of things to listen to instead of engorging from an algorithm. Sure, you can follow albums and artists but since you can't organize them, these features gets useless if you have anything more than 100 items. The UI is in general is way too simple, with very sparse information density compared to your traditional music player. Was it because of necessity or style that all these previous tools opted for all these features Spotify shirks? I'll let you decide that.
- Toreno96 4y ago> 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/ https://spotifyshuffler.com/, if you have enough skills, time, and determination to do that.
- cropcirclbureau 4y agoI'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.)