Where Googles Android may have already failed

(Declaration of interest; I’m involved in AndAppStore.com which allows Android Applications developers to list Android applications and users to download them)

Imagine this; You have a product you want to make available worldwide, but you need the help of others to make it popular. You start a worldwide PR campaign, you make a mock-up available so people become familiar with your product, you run a worldwide competition for people to come up with uses for your product, and then you announce launch dates in one country for one date, another for a month later, a few more next year, and, well everyone else, you’ll have to wait and see what happens. Would you expect everyone to still help you make it popular? Well, Google, HTC, and T-Mobile seem to think it will work for Android.

Back in November 2007 Google announced the Open Handset Alliance and it’s Android platform to the world, the announcement included phrases such as “Android is the first truly open and comprehensive platform for mobile devices.”, “We see Android as an important part of our strategy of furthering Google’s goal of providing access to information to users wherever they are.”, “If you’re a mobile user, you’ll have to wait a little longer, but some of our partners are targeting the second half of 2008 to ship phones based on the Android platform”, indicating that it would be accessible, widely available, and there were going to me multiple phones available in the latter half of 2008.

In January Google followed up by announcing the Android Developers Challenge, a challenge which was open to “individuals, teams of individuals, and business entities … worldwide” which offered prizes of 25,000 USD, 100,000 USD, or 250,000 USD to the top 50 applications. The contest started developers around the world working on Android applications, and there winners from around the global including a German group winning one of the top prizes.

It’s September and we come to the first launch announcement, the moment when the first generation of hardware to power the Android revolution steps up to the stage, and what do we see….. a definitely non-global release. The US will see it on the 22nd of October 2008, the UK in November 2008, parts of Europe (including Germany, the home country of one of the ADC top prize winners) have to wait until some day in Q1 2009, and the rest of the world, well, thats anyones guess. If you compare this to the other main open phone platform, OpenMoko, who were taking orders in North America, Europe, and India from release, you can see why the launch is pretty much an insult to those developers who aren’t in the preferred markets given that the Android launch is backed by three companies who have significant global distribution and support experience.

This leaves all those developers who were encouraged to get involved with Android are left with one of three options;

1) Wait until an Android phone is released in their region and miss out on piggybacking on the buzz the initial PR blitz Google, HTC, and T-Mobile are already involved in (for some this isn’t an option because there is no guarantee that an Android phone will ever be available).

2) Try to get one from the grey market (with the developer hoping that it will work if they can get hold of one at all).

3) Release code tested on the emulator provided by Google and wait for user feedback.

Personally, I believe option 3 is the right choice, although I can see many going down the route of option 1 or 2 and many of those just moving on to other projects before they get a phone, which can only hurt Android as a platform, because after all, wouldn’t you feel disillusioned by a product where the manufacturer goes “It’s open to everyone!! Come on world show me what you can do with it!! Great, Cool!!, Oh, by the way, we’re not actually going to make sure you can get it” ?

[Questions]

Why do I believe in option 3? Android is a platform, not a specific implementation. Any J2ME developer will tell you about how the “write once, run anywhere” goal isn’t a reality, so although the G1 is an Android phone, claiming an application as an Android application because it runs on the G1 (or any other Android ‘phone) is no more or less valid than saying that it’s an Android application because it runs on an emulator or one of the other platforms people have Android running on.

What advice would you offer developers? Get your apps out there (possibly using AndAppStore.com) and get some feedback from users. It’s a model that works for programs of all types (from Linux and Windows beta releases down to one man apps following the “release early, release often” rule), so it’s shown to be a viable working model.

3 thoughts on “Where Googles Android may have already failed

Add yours

  1. Indeed I too have gone for option 3, based on a “best effort” using the emulator. From my own J2ME programming background, I can fully subscribe to your statement “Any J2ME developer will tell you about how the “write once, run anywhere” goal isn’t a reality”.

Leave a Reply

Your email address will not be published. Required fields are marked *

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑