Comments on: Google’s Late Release of Android 2.0 Hurting Developers

By: Android Tapp

Android Tapp — Thu, 07 Jan 2010 20:17:22 +0000

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

By: timmyjoe42

timmyjoe42 — Thu, 31 Dec 2009 02:09:51 +0000

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

By: Alex

Alex — Mon, 16 Nov 2009 17:39:00 +0000

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.

By: Alvin Brinson

Alvin Brinson — Mon, 16 Nov 2009 12:39:11 +0000

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!

By: rowi

rowi — Wed, 11 Nov 2009 12:32:13 +0000

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

By: schwiz

schwiz — Tue, 10 Nov 2009 23:13:53 +0000

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?

By: Dadical

Dadical — Tue, 10 Nov 2009 18:11:05 +0000

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.

By: Seanieb

Seanieb — Tue, 10 Nov 2009 12:58:27 +0000

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.