Chromecast: It’s about time.

Chromecast: It’s about time.

Finally, after weeks of waiting and delayed shipments from Amazon, the lab has a Chromecast.  And we have it thanks to Leslie’s pal Ryan Petty, who loaned us one of his – thanks Ryan!

I’ve been putting it through the paces for the past couple weeks, and it’s left me intrigued for future applications (and a bit frustrated with the current limitations).

What it is: Chromecast is a streaming dongle that plugs into the HDMI port of your TV, so that it’s barely visible (much less taking up precious shelf space). It’s similar in form factor to the Roku Streaming Stick, with one big difference: Roku uses MHL (Mobile High-Definition Link) to power the device, so it only works with a small subset of newer TVs. But you don’t need to find power for it.

This isn’t true for Chromecast – you need to find power for it. It uses micro USB, which means it plugs in to the USB port on your TV, and then to the included wall adaptor. Then you need to find another hole in the power strip.

So, while MHL devices like Roku’s Streaming Stick have the advantage of being completely cordless, with no powering requirements, Chromecast has the advantage of transforming any TV set with an HDMI port into a connected TV. But it needs power.

How it works: Chromecast receives signals from smartphones and tablets, and from computers using Google’s Chrome browser (with the Chromecast plugin installed). It can mirror any web page or video from the computer’s browser, on the TV screen, and it also works with a few mobile apps to play optimized video. The mobile apps work by sending a URL to Chromecast, which then retrieves the video, rather than streaming directly from the device– making for much better video quality.

The premium video content is limited — just Netflix and YouTube were available initially, and Hulu Plus just joined the crowd yesterday — but HBO Go, Redbox, Vimeo, and others have expressed intent to porting their apps to Chromecast as well.

So assuming those Chromecast-optimized apps arrive soon (and there’s no telling, since the Chromecast SDK isn’t even finalized yet), this device will likely be a real contender for the holiday season.

Initial Setup

Chromecast setup involved me going to a URL on my mobile device, which then directed me to install the Chromecast app (on both my iPhone and laptop.) From there, I connected to the Chromecast from the WiFi settings on my iPhone (as if it were a wireless network) and gave it the name and password for our local network. Then, it was just a matter of connecting my phone to the home WiFi network again, and then opening an app on my iPhone (i.e. Netflix) and selecting a piece of content. A new button within Chromecast-compatible apps allows you to select the Chromecast dongle as your output device, so whatever you select from your phone or tablet automatically starts playing on the TV.

Bonus: Chromecast doesn’t tie up whatever device you’re using to control it – so you can start a video from Netflix, and then go back to checking your email and browsing the web on whatever device you’re using. Likewise it won’t keep calls from coming in, though I think it would be nice to see it integrated a bit with the phone features – I’m thinking of Boxee’s remote control app, which automatically paused the video when a call came in. Allowing the viewer to select options like “Do not disturb” or “Pause video when phone rings” at the start of a session might make for a better experience.

Playback 

 

The Netflix app worked quite well, with no noticeable lag in picture quality or streaming performance. The quality was a bit diminished when I tested it on my slow (~4 Mbps) connection at the farm, as expected.

I did notice that the Netflix app on my iPhone frequently forgets that it’s connected to a Chromecast, especially if I’m using it in areas of my house where the WiFi signal is weak. Then, I’m unable to control the Chromecast or pause the video, and I have to scramble to mute the volume if a call comes in.

I didn’t notice the same problem with the YouTube app, which was somehow able to maintain a connection with the Chromecast as my phone dropped off and on the WiFi network.

Streaming from my laptop, I quickly learned why it might not be such a big deal that people are able to mirror Hulu’s free web content up to the TV using Chromecast – the audio skipped almost constantly, and the reduced picture quality and large frame around the video made for a truly sub-par experience. Fortunately, Hulu finally released a compatible app yesterday so we won’t have to suffer through it any longer.

The Verdict

Chromecast does a lot for $35, but still lacks content – however, it appears that the content situation might get a lot better. If we get apps like Spotify and Amazon Instant Video down the road, this might be my go-to device. I really like being able to browse on a mobile device, rather than using a remote control to browse on my TV screen. Could it really be that Google TV finally got it right?

Well, maybe. Enter Sony’s Bravia “Smart Stick,” which breathless media reports dubbed a “Chromecast competitor” as soon as the first FCC filing surfaced — not so. For starters, the “Smart Stick” only works with Sony Smart TVs, and it requires MHL – that’s a very small percentage of the market.

The idea is to unite Google TV features with Sony’s Smart TV features, plus cable or satellite service using an HDMI pass-through. And of course, it wouldn’t be a Sony Google TV device without the same overly complicated remote control that shipped with their last device – surely a big part of the $115 price tag.

We’ll stick with the Chromecast, thanks. And wait to see what Comcast and its brethren have up their sleeve….