Google Announces Chromecast: Nailed It

About a month ago Benedict Evans shared his ideas about where the Apple TV could go from a hardware standpoint:

Now, consider a new ‘Apple TV’ that’s an HDMI dongle, powered by HDMI so you can just plug it in. … And to get the cost down, all it does is Airplay

Fast forward to today where Google has announced Airplay 2.0 Chromecast:

Google is making another foray into the living room with the Chromecast, a small $35 dongle that allows users to stream videos from a phone or tablet to their TV using Chrome.

On the surface, it looks like Chromecast hits the mark:
– $35 price tag
– Plugs into HDMI
– Multiplatform (iOS, Android, Chrome browser)
– Quiet development with release shortly after announcement

But look closer, and some obvious pain points become clear:
– First and foremost, it needs to be plugged in via micro USB cable for power. This ups the complexity and ugliness while reducing the simplicity and portability.
– A router is required for use. Again this reduces the simplicity and portability. Setup remains a question that will have to be answered once it starts shipping.
– Requires third-party developer buy in to implement a new API via the also released Google Cast SDK
– The video stream appears to be an improvised use of a video chat (WebRTC) instead of Miracast, Wireless HDMI or DLNA.

This looks like a solid debut with plenty of excitement from the press. Even though it will launch with limited app support (Youtube & Netflix mostly) you have to start somewhere (Apple with iTunes, Roku with Netflix). I like the idea that once you send something to Chromecast, it takes over the stream leaving the device free to operate or continue browsing for the next video to play. The difficulty in improving a 2.0 product lies in partnerships though; getting developers to implement the API, and getting TV manufacturers to properly support next generation standards such as CEC and MHL, along with deploying WiFi Direct across many products.

My biggest fear for Google is that while they “nailed” the basics in 1.0, the visual of a dangling cord and power adapter the size of the device itself will make Chromecast to easily laugh off with a picture and the sarcastic phrase “Nailed It!

Overall a big pivot in the livingroom strategy of Google that looks to be in the right direction. As is always the case though, time will tell if Chromecast will overcome the hurdles to success. Early praise and interest is easy for Google hardware, long-term success is more elusive.

Palm Reading

In January 2010, many tablet computers were announced at the Consumer Electronics Show in Las Vegas. Nobody really remembers them, mostly because they either failed to reach the market or failed to sell. This was a pre-emptive strike on the tablet everyone does remember, introduced just days later: the iPad.

Once the iPad started shipping in April 2010, the impact was swift and shredded roadmaps across the industry – including three other key April events:
Microsoft cancels the Courier project
HP cancels the Slate tablet announced in partnership with Microsoft at CES
HP purchases Palm for $1.2 billion

By scaling up its mobile operating system and hardware instead of scaling down their desktop counterparts, Apple immediately superseded years of work by Microsoft and its partners to establish a consumer tablet market. Left flat footed by the rejection of Windows 7 running on Intel Atom processors, Microsoft was at risk of being left behind completely in the tablet market, as HP bought Palm and Dell (and many other PC manufacturers) went with Android. This would seem to be the genesis for what was to become Microsoft Surface with Windows RT Surface RT.

But what if…

Suppose that instead, Microsoft – not HP – had purchased Palm, an idea at least one person, Jason Hiner floated in 2009. First, let’s look at the reasons why this didn’t happen:
– Microsoft was already well into ruining Danger Inc Project Pink (the Kin phones)
– Microsoft already had a nascent tablet UI idea in the Zune/Metro Style
– Palm WebOS had no lineage or compatibility with Windows CE or .NET
– Microsoft was already rebuilding a smartphone OS from scratch: Windows Phone 7

Had Microsoft jettisoned Project Pink earlier, it easily could have re-provisioned those funds into an acquisition of Palm. At the time Palm was acquired, it had the Veer and Pre 3 smartphones in development, as well as the Touchpad tablet. Microsoft could have released the Veer as its feature phone idea, with the Kin social elements on top of WebOS. The Touchpad could have become a development unit for its merging of WebOS and the Metro UI. Here, the card’s UI metaphor in WebOS could have made a lot of sense by calling them instead … Windows. The social information strategy is actually similar between WebOS and WP7; both wanted to combine your various information sources and present a unified interface for communications. Backwards compatibility, as it turns out, is a non-issue, as WinRT has none, and both WP7 and WP8 have broken it as well.

Armed with a well-developed mobile OS, Microsoft could have introduced Metro OS for use on tablets in late 2010/early 2011. This would have brought the manufacturing partners closer, rather than pushing them further away as WP7, Windows 8 and Surface RT have done. This could have led to Windows Phone 8 instead being Metro OS 2.0, now for tablets and phones, featuring app compatibility with established developers, apps and ecosystem.

By allowing HP to purchase Palm instead of acquiring it for themselves, Microsoft let the relationship between itself and  many PC and smartphone manufacturers sour, encouraging an “everyone for themselves” survivor mentality. This represents a missed opportunity to quickly bring to market a competent mobile OS that anyone would want to license, rather than everyone fumbling with costly, amateur attempts at vertical integration.

Surface RT Observations

“Microsoft might have some great software and server-side logistics, but its hardware experiments are a series of breathtaking failures, like the playboy sons of a super rich guy who doesn’t know how to raise children properly.”

I liked this editorial from Daniel Eran Dilger. Punchy, a little silly but harshly honest. Let’s not forget a couple of additional details I’d like to point out:

– Go big [and then] go home: It seems as if Microsoft is always willing to give a project a billion dollars (Zune, Kin, RT).
– The bizarre naming story of Metro/ WOA/ WinRT/ SurfaceRT. They should have sent a poet marketer…
– Palm Pad / HP acquisition: The number one PC vendor blew its pivot to mobile in a billion dollar acquisition to no where.
– WinRT was supposed to have plenty of apps as developers flocked to redesign apps for the Metro UI, which has yet to happen for Windows 8, let alone RT.
– HP, ASUS, MS all launched iPad competitors that required accessories to be complete “tablet PC” packages as they envisioned, and the cost of a complete experience was always way above iPad, even at $499 (now $329). All were unwilling to sink a few billion dollars into hardware losses to win second place by including the accessories (usually a keyboard) and competing on price and value first.
– Don’t forget all the manufacturing partners that walked away from MS after the Surface announcement; it pissed them off and few produced RT devices.
– The irony that Microsoft could find a profitable niche in content creators; as Apple shifts focus from the creative markets of yesterday, those professionals are increasingly turning to alternatives like HP workstations for work, and the Surface Pro is a well regarded visual artists’ tool. Actually, scratch that, this doesn’t help the case for WinRT anyway.
– A billion here, a billion there, pretty soon we’re talking real money. Microsoft may no longer have the influence, but they do still have the cash (for now) to buy their way into market share significance.

Britta’d it.

“Those that have come from other failed or failing retailers will be allowed to peddle their poor ideas at Apple, and tarnish what has been one of the single greatest retailers on the planet.”

IFO Apple Store has a great write up on Apple retails latest misstep. The dead on quote above really does a good job of summing up the apparent britta’d direction of the retail stores.

Reports Persist of Budget Cuts, Emphasis on Revenue

September = holiday, not back to school

This article over at AppleInsider about an analysts memo from Brian White erroneously suggests that a September product launch by Apple would be timed for educational sales. Unfortunately the buying time for educational institutions is now, by September they have deployed their new tech and settled in for the school year. For Apple, September is when you launch product for the holiday buying season.