Earlier quoted context omitted.
> It is pretty much impossible to build a music UX that optimizes for all three of these user types 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 su…
You could have different clients for different kinds of users. But then you would almost certainly have users complaining that they need more than one client to do what they want.
It's also an easily solveable problem if the APIs are actually open. If Apple put out three music clients, you would definitely get people complaining that they weren't unified. If Apple shipped an open iOS API that covered everything in their official client(s), somebody in the community would just build one client that did everything a complaining demographic wanted, and then sell it for $4.99 on the app store.
When you see large groups of people complaining about current tech offerings for sustained periods of time, that usually means that the legal and/or technical barriers to entry to build alternatives are too high.