4 ms·
I'm not sure why Google didn't go with DLNA or Miracast, but presumably they looked at this. Second screen devices with no control on their own are a bit new, s
by spankalee 13y ago
I'm not sure why Google didn't go with DLNA or Miracast, but presumably they looked at this. Second screen devices with no control on their own are a bit new, so maybe they weren't a great fit. Chromecast is built on at least some open protocols like DIAL and WebRTC, and it works with 3rd party apps, and there are broadcaster and receiver projects out there. I use [CheapCast] [1] on an old phone and it works great (for non-DRM'ed content, admittedly). Google also said they want devices like TVs and radios to include Chromecast support, I'm hoping without any licensing beyond the branding, and hopefully no fees. It certainly looks like it's heading in a pretty open direction.
Yes, I know that one guy used an undocumented API call and had his broadcast app broken, and pitched a hissy fit, but that's what happens when you do that. The API is supposed to stabilized soonish.
So I don't see your lock in claim holding much water. I think it's much, much more important to make Play content available on devices at all, than to lock out other content. When you sell digital media you generally want it to be available everywhere possible.
[1]: https://play.google.com/store/apps/details?id=at.maui.cheapcast&hl=en https://play.google.com/store/apps/details?id=at.maui.cheapc...