Any doc about what developers have to do to support Chromecast?
Google Chromecast
301–310 of 326 posts
Re: Google Chromecast
#302Earlier quoted context omitted.
It's pretty [1] standard [2] to not include cords in product pictures. 1. https://www.apple.com/appletv/ 2. https://www.apple.com/imac/
Really funny. Everybody else does it. Even though two devices are not comparable in form factor. Why it is in minuscule fine print though? Please ...
Re: Google Chromecast
#303Earlier quoted context omitted.
> They made it dead simple to stream content from any device to your TV. So anyone can use it, particularly the older generation. That's not really new. Apple TV lets you do the same thing with AirPlay, and it works great. Seems like a decent device, and the fact that it works with non-Apple hardware is obviously useful for people who don't have Apple households, but I don't think it's disruptive.
> Apple TV lets you do the same thing with AirPlay, and it works great. With Apple-devices only. The majority of the market has non-Apple devices. And that's across a range of product-classes: Desktops, Laptops and mobile devices. To be able to take advantage of AirPlay you need to be all in all across all those classes. That brings the effective market-share which can use AirPlay (in developed countries) down from a…
Assuming they use Chrome or Android, that is...
Re: Google Chromecast
#304This is exactly what I've been wanting the Apple TV to be for ages. The only thing Apple TV is actually good for is Airplay. There doesn't need to be an OS or a UI for the Apple TV: your phone or tablet will be a better experience for typing and searching for content every time. Its a fool's errand to try to design a UI for a TV that isn't dreadfully painful to use: no one ever wants to interact with something 10 fee…
Re: Google Chromecast
#305Earlier quoted context omitted.
> Apple TV lets you do the same thing with AirPlay, and it works great. With Apple-devices only. The majority of the market has non-Apple devices. And that's across a range of product-classes: Desktops, Laptops and mobile devices. To be able to take advantage of AirPlay you need to be all in all across all those classes. That brings the effective market-share which can use AirPlay (in developed countries) down from a…
> This will be a device people can actually use. Assuming they use Chrome or Android, that is...
Well, actually, iOS and OSX devices are supported too.
Re: Google Chromecast
#306Earlier quoted context omitted.
I find it a pain to get my phone/tablet and 1) wake it up 2) unlock it 3) type password 4) close running app 5) scourge screens for the remote app, and 6) wait for it to start and connect, sometimes it takes a while. It's infinitely easier to grab the aluminum remote or bluetooth keyboard and just press a key. You're also missing the fact that the AppleTV is a shared device. It doesn't need locking/protection, and ca…
Except you don't necessarily have to do 2, 3, 4, 5 or 6 with this. It either has controls over lock screen or in the notifications tray depending on the app. (and most users don't use passwords anyway. So really it's just a matter of picking up your phone and turning it on, which is usually easier than finding a remote.
Is this true? Everyone I know with a smartphone -- everyone -- uses a password.
Re: Google Chromecast
#307That said the MediaLink HD often had lag issues that kept it more in the realm of presentations and media and made it difficult for real time games. Even for presentations I'd often carry my own WiFi AP around with me or find ways to get it just to connect between the phone and device to avoid them. Home performance is probably better than conference and event performance.
I recently tried a Netgear Miracast adapter to send HDMI from an HTC One and the lag is completely gone. I haven't tried Google's implementation of Chromecast yet, but I'm suspicious it won't be nearly as lag and trouble free as a WiFi Direct only device like the Netgear, though. You have a whole extra OS running device in the chain to make things a pain. So I'm suspicious the extra complexity isn't worth it for this class of devices.
Re: Google Chromecast
#308Re: Google Chromecast
#309I think people aren't understanding how awesome this technology is: 1. Every time someone shows you a YouTube video, you spend 10% of your time watching it and the other 90% thinking about that one video you know of that's funnier. With Chromecast, you can queue that sucker up for nexties right from your own phone, without interrupting the video that's currently playing. 2. Chromecast does NOT use the resources of th…
Completely agree. This is potentially an incredibly disruptive innovation. Provided third parties (TV Networks, Vimeo, etc.) write apps for this, I think it will radically change the way people watch TV.
No-one wants another box with another clumsy interface. They just want to watch what they see on their phone or laptop on a better screen.
Wow.
Re: Google Chromecast
#310I'm confused. Can it grab and process the stream itself? So, if I pull up netflix on my phone, start a video, then force close netflix, will it still be playing?
Basically your phone is not only practically, but technically, just a remote.