From a user perspective you're right but from a technical sense, Chromecast got its roots as little more than a remote-controlled Chrome session. Alike the Netf

From a user perspective you're right but from a technical sense, Chromecast got its roots as little more than a remote-controlled Chrome session. Alike the Netflix DIAL protocol that it evolved from, Chromecast was for many years merely a hdmi-out stick device that ran Chrome! It's not at all clear to users though, isn't a meaningful name. And now as well as web there are also Android Custom Receivers from Chromecast. https://developers.google.com/cast/docs/web_receiver/basic https://developers.google.com/cast/docs/web_receiver/basic https://developers.google.com/cast/docs/android_tv_receiver/core_features https://developers.google.com/cast/docs/android_tv_receiver/... It would have been interesting if there was an alternate path where Chromecast really did expose its underlying browser-ness better. If I could just tell my phone to cast hacker news and then scroll on my phone's screen. I wonder if that was ever considered. Also note that ChromeOS was also a web-centered thing at the time, so there was some symbiosis with that. Both web powered tech platforms. But given the recent announcement that Google is killing ChromeOS & Android is the way forward for everyone, well, extra sensible that Chromecast has to go: finalizing/cementing the (imo unfortunate for all) cultural victory of Android-over-all at Google.