In the wake of Android 2.0’s grand public unveiling, everyone is talking up how this is the Android we’ve been waiting for. With a truck load of new and exciting features, Android 2.0 is the most competent competitor to the iPhone and iPhone OS yet. So why does it need to get better? I’ll lay it all out right from the start: Since the iPhone 2G and iPhone 3G are powered by a 400MHz processor, why is it that they run circles around not all, but most Android phones, phones with processors roughly 30% faster clocked at 528MHz?

Now there’s one thing that needs to be highlighted and taken into consideration. The iPhone OS is not built for multi-tasking, therefor all the resources go towards only one (or a few when considering the in-house Apple apps) app at a time whereas with Android you could have many apps running simultaneously. With multiple apps open at once comes the obvious negative effects such as slow downs and other performance obliterating instances. If Android is so great and modern, shouldn’t these issues be cleared up already?

Many people, myself included, have started to cast Android as a “modern WinMo” of sorts in that Android is quickly encroaching into WinMo territory and spreading to countless devices built by many manufacturers. Much the same way Windows Mobile is received in the mobile world — one OS licensed to many vendors. The only difference is that Android is much relevant and lusted after.

With the issue mentioned above, Android’s seemingly laggy performance on even speedy hardware shoots a warning flare across my face. While I love how Android is overtaking the market and giving users options when hardware is concerned, I’m left with a nagging worry in the back of my mind that just as Windows Mobile suffers from poor hardware utilization, Android is too heading down that path. Take for example Windows Mobile 6.5 running on the few 1GHz Snapdragon powered beasts we’ve seen leaked so far. While indeed fast and snappy — snappier than pretty much everything else — if you were to take Android or the iPhone OS and run it on a processor clocked between 600-800MHz, the same performance could be seen. Again, it’s the poor management of hardware resources.

It’s understandable and given that the approach WinMo and Android are employing in licensing to many hardware manufacturers means more diversity at a slight trade off for tight integration. This tight integration is perfectly highlighted with the iPhone and iPhone OS. No surprise there. Though not all is lost. With the Moto Droid freshly announced and tested across the interwebs, we can see just what a close relationship between hardware and software achieves — perfection. Is Android 2.0 and the Moto Droid perfect? Far from it. But it’s pretty damn close and the closest Android has come to perfection so far.

Is Android doomed to a fate of Windows Mobile syndrom — slow, archaic appearance, and inefficiently programmed for life? Not a chance. The Android community is an active one. One that is constantly on the forefront of mobile OS technology. Android developers and programmers of all circles need to continue this forward push to keep Android progressing with the best. Efficiency just can’t be left behind.

I want Android to proliferate as Windows Mobile has done. I want to see it succeed. But I want it to do so without building the old, outdated stigma that has veraciously attached itself to the aging and lacking Windows Mobile OS. Understand what I’m trying to say? Agree? Disagree? Let’s hear it.

{Image Source}