Linked by David Adams on Fri 25th Mar 2011 14:48 UTC
PDAs, Cellphones, Wireless The company revealed Thursday that it will delay publication of the Android 3.0 (Honeycomb) source code for the foreseeable future - possibly for months. It's not clear when (or if) the source code will be made available. The decision puts Android on a path towards a "draconian future" of its own, in which it is controlled by a single vendor - Google. The Ars link linked above is a pretty inflammatory editorial, so see also: Businessweek, GigaOM, The Register.
Thread beginning with comment 467860
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: There there...
by whartung on Fri 25th Mar 2011 17:19 UTC in reply to "There there..."
Member since:

Actually, it is pretty bad.

This is the money quote:

Rubin told BusinessWeek that Google has made the decision to keep the Honeycomb source code under wraps because it doesn't want hardware vendors to adapt it to run on other form factors where it might not function properly. Rubin says that Google cut corners during Honeycomb's development in an effort to rush it to market. He believes that widespread adoption at this stage in usage scenarios that Google didn't anticipate would lead to a very negative user experience.

This basically boils down to being unhappy with the vendor community around Android. They lack the controls and simply don't trust the vendors to "read the readme" and not use 3.0 where it's supposed to be used. To not test their hardware, and to ship crappy product with Androids name on it.

This a bigger rift than simply not releasing source code. It goes deeper than that to basic control over the platform.

As they say, "Freedom is letting others do things you don't like", but in this case it hurts the brand and becomes a tragedy of the commons as some shoddy vendors spoil the name for others that "use the same platform".

As someone else mentioned, there needs to be an "Android Inside" or some other certification process in place to maintain the brand consistency, or less than stellar performers can make it a mess for the entire platform. But that will slow down adoption and increase costs.

At this point, the phone audience is still pretty unsophisticated. Android needs to build brand recognition above and beyond the handsets (something the cell vendors probably aren't really keen on anyway). Depending on the marketing, a consumer that has a bad experience with an Android phone could well "blame Android" rather than the handset manufacturer.

Reply Parent Score: 6

RE[2]: There there...
by Alex Forster on Sat 26th Mar 2011 00:19 in reply to "RE: There there..."
Alex Forster Member since:

Couldn't they withhold use of the Android trademark? Wouldn't that solve exactly this problem?

Reply Parent Score: 3