Google’s Late Release of Android 2.0 Hurting Developers

by Antonio Wells Nov 10, 2009 5:00 AM – 8 Comments

Now that Verizon’s DROID has launched, I’ve been getting many reports that some Android Apps don’t work; force close errors, portions of the app freezes, or the graphics look crappy due to the higher screen size of Motorola’s DROID (all other devices were 320 x 480, whereas DROID’s illustrious screen is 480 x 854).

If you’ve been following Android’s growth since launch, this pattern with Google is not new… and actually attributed to another factor: the ability to test on the actual device. For a brief time developers experienced app crashes on the T-Mobile G1 until they got their hands on one or the Android Dev Phone 1. Verizon’s network of isolated phones can make it difficult for some developers to get their hands on practical applicable devices. Hint… hint… Motorola, please release a GSM compatible or non network choked Droid, or Google do us another favor and give some away or sell a Developers version.

Also when Google released Android version 1.5 (Cupcake) to Devs in mid April 2009, OTA updates were rolling out in mid May 2009, they had to quickly update their Android Apps or sink. In some cases; Google, Motorola nor Verizon are not at fault… Developers need to get busy cranking out Android 2.0 compatible apps! Some Android apps even become abandonware as they may never see an update.

This release timing was worse… at the time of this article, DROID is the only retailed and released phone with Android OS version 2.0 (may possibly get 2.1 update 12/11/09), all others phones and carriers support Android version 1.6 and lower. Google didn’t release version 2.0 until 10/27/09, DROID debuted 11/6/09 and developers have to scramble to learn what’s changed and update their apps. The sad part about this is most devs don’t know their app is not compatible until they start getting negative reviews in the Market.

I would encourage emailing the developers (which you can find their email address on the app listing in the Market) to let them know your problem. A majority of them will take the time to work with you to prepare a fix.

Tags: Android 2.0, Android App, Android Developers, Google, Late Release, Motorola, Motorola DROID, Verizon, Verizon DROID

Categorised in: Apps Blog

8 Comments

By Seanieb on November 10, 2009 at 6:58 am:

AndNav2 seems to have died. I dont know if it has anything to do with Andriod version 2.0, but something is going horribly wrong.

Have a look at their forum:
“Are the developpers still alive??”
http://www.andnav.org/index.php/en/community-forum/topic?id=431

And the comments on bottom of the download page:
http://www.andnav.org/index.php/download/

Its very sad as this was a fantastic app that introduced thousands to and ideal use case of the OSM project. I hope that the project comes to life again.

Reply
By Dadical on November 10, 2009 at 12:11 pm:

What would REALLY, REALLY help would be:

– earlier SDK access. maybe even some kind of beta program
– early developer device support for new O/S versions… rumor is 2.0 won’t even install on the official dev phone, and the emulator can only go so far

My app, Screebl (http://www.keyeslabs.com) was an example of one that got flaky on DROID, and I have no way to debug other than user iterations. I got lucky and found a knowledgable user that was patient.

Reply
By schwiz on November 10, 2009 at 5:13 pm:

well google has made it implicitly clear that the only thing they care about is the money the make off exclusive licensing of Android. Is anyone surprised?

Reply
By rowi on November 11, 2009 at 6:32 am:

There is a GSM Version of the Droid. It’s called ‘Milestone’ and O2 Germany wants to deliver it from next week on. It’s also available from amazon.de for EUR 463,50

Reply
By Alvin Brinson on November 16, 2009 at 6:39 am:

As much of an Android fanatic as I’ve been, this hi-lites a SERIOUS flaw in Google’s model of how Android should work.

Unless Google intends on ensuring that every carrier is able/willing to promptly update devices to the newest software (which they don’t seem to intend), then Android is moving too quickly.

Bug fixes? Yes. Streamlined user interfaces? Yes. Those are fine.

Major OS upgrades breaking old applications with no regard for backward compatibility? A serious no-no that has been grafted lock stock and barrel from the Linux OS community which has in the past not given a damn about backward compatibility.

However, unlike Linux, where a system that is 1 or 2 years old can easily upgrade to the latest Ubuntu, Android is designed to go onto CLOSED devices that are purchases under 2-year agreements.

Worse, these devices do not have the hardware capability it appears to keep up with the fast paced development.

By breaking backward compatibility in EVERY SINGLE RELEASE, Google has ensured that those of us who paid $399 for a G1 just a few months after release will be left in the dust and forced to upgrade or forgo the benefit of any new Market applications before what should be the reasonable end of life of our phones (2-3 years at a minimum).

Developers are required then to write to new devices, or maintain multiple versions of their applications, which many aren’t likely to do.

Hey Google, howsabout you slow it down a bit? Fix what’s wrong, yes, but quit trying to deprectate shiny new hardware!

Reply
By Alex on November 16, 2009 at 11:39 am:

Same issue here.

And the worst part is only the US and a few European countries have access to a WVGA device to test on.

Hardly fair for devs outside those countries.

Reply
By timmyjoe42 on December 30, 2009 at 8:09 pm:

(pssst…the Motorola Cliq and Samsung Behold II are both stuck on Android 1.5 because of manufacturer’s customizations of the operating system.)

Reply
By Android Tapp on January 7, 2010 at 2:17 pm:

With the launch of the Nexus One, Developers were screwed worse as far as receiving access to the latest Android SDK 2.1 to try to test their apps. To date, version 2.1 is not available for testing… see more frustrations illustrated here: http://www.pcworld.com/article/186201/android_devs_complain_about_no_nexus_one_sdk.html

Reply