Why does it matter what the backend is? A music player is a music player; it shouldn't matter where the music comes from.

▲

slau 4 days ago | parent | next [-]

Well, it matters when you have to integrate with APIs and idiosyncrasies of third parties, and whatever draconian DRM they require. It’s obviously not impossible to add support for multiple backends, but from a development effort it definitely matters.

It’s not like streaming platforms are gingerly implementing open and common standards for music streaming. Winamp had support for .m3u and streaming back in ‘04, but we’ve moved on from that.

▲

MangoToupe 3 days ago | parent [-]

Sure, but presumably that is different from the actual value of the app itself—the frontend. It's just a matter of effort to connect the interface to the backend. Why you'd insist on tying the two together is anyone's guess (likely convenience).

▲

jazzyjackson 2 days ago | parent [-]

> (likely convenience).

AKA the limited resource of developer-hours

	▲	MangoToupe 2 days ago \| parent [-]
		> AKA the limited resource of developer-hours Sure, but each connected backend magnifies value to end-user. To say any one client is worth devoting to just a single backend is crazy.

▲

connorgurney 3 days ago | parent | prev [-]

But they never marketed it as a generic music player, did they? It also isn’t a toaster.

	▲	MangoToupe 2 days ago \| parent [-]
		> But they never marketed it as a generic music player, did they? It also isn’t a toaster. A music player is very much a dumb pipe (or "toaster" as you call it). There's nothing special about Apple Music that makes it a backend worth devoting an entire client to.