Related to that: The protocol that these (and many third-party devices) speak is called "Google Cast", yet Google refers to third-party devices speaking that protocol as "Chromecast built-in"...
> Similarly Chrome is their web browser so why call the physical device Chromecast?
I suppose it originally made sense, given that the physical Chromecast device only worked with Google Chrome, and in its early days even was used for tab mirroring (until most video sites started integrating the protocol natively). Wanting to benefit from the (at the time quite positive) brand perception of "Google Chrome" probably plays an even bigger part.
But at this point it seems like a weird historical leftover.
> Similarly Chrome is their web browser so why call the physical device Chromecast?
I suppose it originally made sense, given that the physical Chromecast device only worked with Google Chrome, and in its early days even was used for tab mirroring (until most video sites started integrating the protocol natively). Wanting to benefit from the (at the time quite positive) brand perception of "Google Chrome" probably plays an even bigger part.
But at this point it seems like a weird historical leftover.