For apps that integrate with the SDK (currently Youtube & Netflix, but I am sure more will be coming soon), the processing of the content can be transferred to the the Chromekey. Hence, once you "flick" your Netflix content to Chromekey, your phone is free and not processing content anymore unlike Airplay, which is a huge win for your phone's battery.
If that's the case, I wonder why Chromebooks (other than the Pixel) aren't compatible.
Close. It's hardware encode acceleration. The Ivy Bridge CPU in the Pixel has it, the earlier Chromebooks don't (I don't know if that's true universally; I didn't check).
It only requires CPU usage when it's streaming the contents of your screen. For Youtube/Netflix, all it does is tell the key the url of the stream and everything is done either on the key or the server.
I don't believe that's correct -- from what I can tell, when it's streaming webpages, it is actually only synchronizing two copies of Chrome -- one on the stick, one on your PC. It is not encoding/transmitting a video, as with AirPlay or Miracast.
From what do you discern that? Given that everything they showed about the the product was variations of it receiving and decoding a video stream, it would be quite a switch for it to also have a full platform running a web browser in synchronicity. It seems much more likely that it is a direct video send, making it enormously simpler to design.
> The receiver device runs a scaled-down Chrome browser with a receiver application that receives data over Internet Protocol and transmits it to the television via HDMI.
Very cool, though incredibly surprising (a browser is an intensive, complex thing, so will people have to constantly be patching their Chromestick?), especially given that once you add the cost of synchronizing all interactions, it seems so much easier to simply video grab the tab.
If anyone has this device, what is CPU usage on the source like when tab-casting?
I don't know, maybe because it needs a browser extension which older ones don't support at the moment. I would assume they'll support them later, but honestly, I don't know.
If that's the case, I wonder why Chromebooks (other than the Pixel) aren't compatible.