Comment by vluft
7 hours ago
that is _purely_ netflix's decision; they have decided not to integrate. in fact, earlier this year netflix accidentally rolled out their internal version which has full integration with the APIs and then said "oopsie" and removed it again.
Yep. The APIs have always been publicly available for streaming services to use, Netflix just refuses to use them.
The reason is pretty obvious. Netflix would rather have users open their app directly so there’s opportunity to shove things in their faces, collect data from their browsing, and ideally become positioned as the user’s “main” streaming app. The user having a hub app and treating Netflix as one of several services directly opposes their aims.
The situation shares a lot of similarities with Spotify, which also refuses to take advantage of native APIs for the same reasons. Though in their case, there’s an added layer of irony with how they make all a big ruckus about how Apple needs to open their platforms up only for them to pretend APIs don’t exist after Apple adds them. As an example Apple had to hardcode a hack into HomePods to enable Spotify to work with them; where most services (Pandora, Tidal, etc) hook the official HomePod streaming APIs which pull directly from the service to the device, for Spotify Apple has to automatically AirPlay Spotify playing on the user’s phone to the HomePod. It’s ridiculous.