An Early Look at the Android 2.0 SDK

android_20_eclairWell, the Android 2.0 SDK has been out for a few hours now. In and around helping out with the Sprint Open Developer Conference, I have been reading up on and analyzing what is new in the SDK, from a programmer’s perspective.

This release seems more focused at end users than developers. Much of the sizzle comes from things like Exchange support, camera enhancements, and whatnot. That’s not to say that Android 2.0 adds nothing for developers, just less than one might expect from a major version release.

The primary new APIs are the long-lost Bluetooth APIs and the new contacts and sync APIs. The former have been oft-requested, but both should open up many new areas for new apps or new capabilities in existing apps.

As welcome are the relative few planned regressions. Outside of two constructors for BitmapDrawable, nothing was outright removed in this release. The only published functionality change — BACK button and kin now being processed on key-up rather than key-down events — should impact fairly few apps. Of course, there are probably some other things that are different that are undocumented, as there usually are. Developers will suss out those issues over the next several weeks. However, compared to Android 1.5 (wiping out a bunch of functionality in the area of settings management), Android 2.0 seems mild.

Some of the best improvements, though, may come from the tools support. There is a new tool to suggest optimizations for your XML layout files (layoutopt), to go along with tighter integration between DDMS and Traceview for performance diagnostics. These will help developers wring better performance out of their apps for existing hardware, as we await snapping dragons, bigger cortexes, and other stuff to improve hardware speed.

Some changes need further evaluation. For example, the HTML5 features are decidedly welcome, particularly the <video> tag support. However, we need to do more testing to see how well these features hold up in the real world, whether they are available from the WebView widget (remember: Gears was only available to the Browser app), and so on. Similarly, we will need a lot more time to evaluate the multi-touch data that comes in MotionEvent objects.

Overall, Android 2.0 is shaping up to be an interesting, if not earth-shattering, release for developers.

About author

AndroidGuys 4627 posts

Founded on November 5, 2007, we've enjoyed bringing you the latest in Android news and rumors. Updated daily, we strive to deliver reviews, opinions, and updates on all things related to Android.

You might also like

News and Rumors

Huawei pulls curtain back on flagship Ascend P7

Huawei on Wednesday pulled back the curtain for its latest flagship smartphone, the Ascend P7. Making its debut at an event in Paris, France, the handset is sleek, thin, sexy,

News and Rumors

HTC Puccini Passes FCC With AT&T Bands, Launching Soon?

The HTC Puccini, rumored to be HTC’s first ever Honeycomb tablet, was revealed back in May, and now we’re learning a bit more about the device. We told you that it will

News and Rumors

Moto X+1 to hit Verizon on September 25

Still holding out for the next iteration of the Moto X? Well your wait may be coming to an end.  The folks over at Droid Life believe that the new


  1. Andrex
    October 28, 01:12 Reply

    The "simultaneous-event" additions to MotionEvent have peaked my interest the most, though I'm also looking into the Sync API – I think they stole the idea from me!

    From my comment at the Motodev blog (

    …One big idea I've been playing with is an API to sync app settings across multiple installations. The point where more Android users have more than one Android device will probably happen really soon, and syncing in the cloud would fit perfectly with the push abilities of phones.

    Made on September 23 in response to Motodev's question, "How would you improve the Android platform, the tools, and ecosystem?" Not to say I'm angry of course, I just think it's somewhat coincidental.

Leave a Reply