Video streaming alone creates an argument for consumer harm against most major platform vendors, since nearly every FAANG has at some point been locked out from paying customers within another one's hardware ecosystem. Prime Video and YouTube were unavailable on each other's devices for years, Apple TV briefly wasn't carrying Netflix, Apple services are paywalled behind Apple devices, etc. Additionally, the ones that
do work still depend on access to integrations for features like voice control, leading to scattershot functionality across any from third parties.
Google in particular has also abandoned support for open specs in favor of deepening the Chromecast ecosystem -- having both removed DIAL support from later versions of the Cast protocol and Miracast support from Android itself.
And that's before you get into the interop for purchases within these ecosystems, because under the DMCA you can't legally do anything about the incompatible DRM schemes, even for media that other devices are more than technically capable of playing.
Another, related issue is that the additional set of proprietary APIs on top of AOSP amounts to an Android ecosystem that's "open," but renders any implementation that they haven't blessed as a second-class citizen. This has tangibly impacted compatibility efforts by other vendors, ranging from Amazon (Fire devices) to Huawei (loss of Play Services via the ban) to Microsoft (Project Astoria) -- for reasons that, in part, involved maintaining a walled garden of complementary hardware.
To be completely fair about this one, it's not strictly that cut and dry, as the ability to leverage vendors with Play licensing has also forced widespread adoption of solutions like Treble. But over time, large sections of the OS have been abandoned in favor of proprietary Google apps, and the API incompatibility hampers the growth of alternative ecosystems, even if you're another FAANG that can bring your own cloud and develop your own hardware.
To that point - while I personally think Oracle's SCOTUS case amounts to brazen trolling, it's, uh, not great optics for that whole argument that API compatibility is fair use when Android apps across several different categories will break just because updating your EOL'd device or getting rid of manufacturer bloatware will trip SafetyNet -- or because your vendor is a competitor and your device just isn't allowlisted by SafetyNet in the first place.