|
|
|
|
|
by Shebanator
2333 days ago
|
|
As someone who worked on Google Play Music for many years, I'd like to point out that a lot of the UX criticisms here are really just personal preferences, and those preferences are based in very large part on the way you listen to music. Some people are "lean back" listeners who just want to put on a radio station of music they like and not fiddle with it. Others are expert curators who have tens of thousands of tracks in their personal collections. Some are all about their personal custom playlists, and don't care about music libraries or radio stations at all. It is pretty much impossible to build a music UX that optimizes for all three of these user types, since they want such different things. Apple Music, Spotify, and Google Play Music have all made different choices in how they address this. Some of those were (IMHO) good choices, others weren't. But it is dangerous to assume that what works well for you will work well for others. The discussion about the queue here is a great example: one person hates it with a passion, another loves it. |
|
This is a good argument for not tying music subscriptions to a specific client -- ie, allowing 3rd-party clients that are optimized for my specific user-type to freely hook into and stream from my Google Play Music subscription via an official API. The Google Play Music client is not optimized for users like me. I'm sure it was a lot of work to build, but I am not the target demographic of any of the interface decisions that have been made, and I curse the designers every time I open the app.
So it's weird that, say, Shuttle, a music client that is optimized for me as a user, can't hook into my account or even download my purchased music.
I don't mean to call out Google Music in specific, because while it doesn't have good public APIs, they're at least consistent enough that alternative clients are being made on desktop.[0]
But I do see this as a trend across a lot of SaaS services -- Netflix, Twitter, Facebook, Apple Music. People complain that the services aren't optimized for them, and designers will roll their eyes and say, "you can't optimize for everyone".
And that's true. But who's fault is it that you have to optimize for everyone? Who's fault is it that you have to try and figure out how to balance a bunch of wildly diverse and often contradictory needs? There used to be really good alternative Twitter clients, and if Twitter wants to complain now that building one client for everyone is hard, I just can't muster the energy to feel sorry for them.
Apple's whole shtick is trying to get everyone to use the same official apps, to have the same consistent, good experience. I'm not sympathetic to a company that deliberately puts themselves into that position and then complains, "optimizing for everyone at the same time is hard."
[0]: https://github.com/MarshallOfSound/Google-Play-Music-Desktop...