October 29, 2009

Android's fast release cycle could backfire

Android 2.0 is coming hot on the heels of the previous version, but will such rapid change leave customers wary of Google's mobile OS?

Remember the original "Star Wars," where the Jawas would roam the deserts of Tatooine in their Sandcrawler, rounding up whatever odd droid models they could find to sell to their human customers? It seems the market for Google Android handsets follows pretty much the same principles.

Google made the Android 2.0 SDK available for download this week, just six months after the release of the Android 1.5 SDK in April and a mere six weeks since it announced the Android 1.6 SDK update in September. That's a lot of versions for an OS that only hit 1.0 last year.

[ InfoWorld's Galen Gruman handicaps Android 2.0's chances against the iPhone and BlackBerry | See the Android 2.0 OS in action in our video preview. ]

Android developers, frustrated with OS bugs and with UI issues with the Android Market store, have been pressuring Google to bring updates to market more quickly. The Android 2.0 SDK release, in particular, is a significant milestone, not least because Android 2.0 will be the OS that powers Verizon's hotly anticipated Droid handset.

But what about the almost 50 other members of Google's Open Handset Alliance? Which versions of the OS will their phones support? And more important, where does that leave developers who want to write software for Android handsets, when they're confronted with as many options as at a Jawa swap meet?

Android's fragmented ecosystem
Android isn't the only mobile OS that's a moving target for developers. Research in Motion's BlackBerry platform, for example, has long confounded app builders by offering multiple SDK versions, most recently adding a Web-based development option.

But Android presents unique challenges. Because it's open source and backed by a consortium of handset vendors, carriers, and semiconductor companies -- rather than a single vendor, like RIM -- Android partners have broad leeway to modify the OS to suit their own ends.

Further complicating matters are the "homebrew" versions of the OS now appearing, such as Cyanogen, which add tweaks of their own while cherry-picking features from forthcoming Android versions before they are officially released.

White Paper

D2D Virtual Tape Library Replication Primer

This whitepaper explains the terminology and concepts behind Data Replication technologies and establishes some sizing rules through worked examples. Learn the new paradigm in disaster tolerance—protect data anywhere.

Download now »

White Paper

An Alternative to Virtualization for Datacenter Cost Savings

Server virtualization is a popular option for dealing with mounting datacenter costs. Another equally promising approach is the use of an Application Delivery Controller. Citrix NetScaler provides a low-cost way for organizations to reduce their server count and accrue cost savings from a reduction in space, cooling, power and personnel.

Download now »

White Paper

Why Your Firewall, VPN, and IEEE 802.11i Aren't Enough to Protect Your Network

The emergence of WLANs has created a new breed of security threats to enterprise networks.

Included in HP ProCurve WLAN solutions is security technology that alleviates threats from WLANs through:
* Monitoring wireless activity inside and out of the enterprise
* Classifying WLAN transmissions into harmful and harmless
* Preventing transmissions that pose a security threat to the enterprise network
* Locating participating devices for physical remediation

Download now »

White Paper

Bringing the Edge to the Data Center

Effectively address data protection challenges, implementing solutions that help store and protect business–critical data while cutting costs and improving efficiency and reliability.

Download now »
graya 29-Oct-09 11:35am
Great article. I feel the same way and is why I look away from thoes phones.
bw 29-Oct-09 2:01pm
All valid points. However as msoft proved in its late to market entry of the windows vs apple all those years ago, multiple manufacturers and distribution channels are a small price to pay for minor inconsistency. The intervals between version levels will slow as more phones launch.
ktopera 29-Oct-09 4:23pm

Interesting comments, Neil.

This will definitely limit developer coherence, but I think carriers will just market the heck out of their Android phones and customers that are less aware of mobile apps, free updates, etc, will just bite (and be stuck in 2-yr contracts).

I'm not really certain that Google cares. Remember that outside of app development, all these Android phones will have built-in Google svcs to drive (Google's) revenue, so the carriers are kind of stuck in terms of where to get an advanced mobile OS (paid or free).

One step below choosing a mobile OS may be to do what AT&T did with "ATT.NET": look at Opera powering their mobile browser on the existing "dumb OS," and transforming every phone into a quite powerful internet phone for web apps, Opera widgets, (Opera Unite apps?), etc...

varvar 30-Oct-09 9:11am
I agree with the columnist and many of the comments--Android's documentation is scanty--I paid good money for the developer's handbook which is more or less useless [cannot hold a candle to the superb documentation that has been the Apple hallmark]--the SDK is full of arcane mumbo jumbo and apparently supports a subset i repeat a subset of Java with inconsistent syntax and definitions? Why bother, Google could go out and acquire the Revolution platform---a slick internet-savvy client server GUI platform and SDK risen phoenix-like from the ashes of Apple's Hypercard see http://www.runrev.com
Gray_Hair 3-Nov-09 8:11am

CARTERFONE for WIRELESS!!!

merrill77 3-Nov-09 12:58pm
Are you kidding me? What, so Google should slow down development? Don't be absurd. Think back to 1988 and say "Microsoft should stop adding new APIs to Windows because the developers can't keep up. There are just too many new computers, printers and video cards that it works with - customers won't like that." Get real! This level of diversity in the hardware landscape and the rapid pace of improvements in Android are a beautiful thing. This market segment has been desperate for these things for a long while. As long as the APIs allow developers to query the device capabilities, then they can use (or not use) the new features as they become available.
ASB 10-Nov-09 9:42am
The speed of change will not be a huge impediment unless the code that Google is putting out is buggy or otherwise fails to address market need. Most people in the smartphone market make a determination about what carrier to use based on phone choices, features and coverage. This situation will not change that. The carriers who provide Blackberry smartphones don't support all the same features or even releases, and that has not significantly undermined RIM's marketshare. What is needed is a smooth upgrade path between versions, and applications that can probe the APIs for the current feature set. At the end of the day, it is the carriers that are Google's customers, not the actual smartphone users, and Google needs to satisfy them. This will add some pressure to Apple, resulting in competition and better customer outcomes. ASB (My XeeSM Profile)

Sign up to receive InfoWorld Resource Alerts

Subscribe to the Today's Headlines: First Look Newsletter

Find out what will be news for the day, with our first-thing-in-the-morning briefing.

©1994-2009 Infoworld, Inc.