The one big POTENTIAL flaw that could REALLY mess up Google Android

Given that I am not in Barcelona at the Mobile World Congress (nev kinda like the music I am not in a physical space where I can view all the Google Android.

But I am in a space where I can monitor what's going on, and offer opinions.

(My girlfriend calls them "assumptions," but I call them opinions, heh.).

So back to Google Android.

Something I've been thinking about that could really trip this up is sucky code.

Pulvermedia vp of community and content Carl Ford offers these thoughts in his Carl's Corner email newsletter:

...here is what I think I know about Android. Google has a RIM like development tool. It is not mind blowing and in the end the navigation is not clearly intuitive. App developers will be regulated to submenus, and it is not clear whehther the malware protection is sufficient for badly coded apps, and the extent of the a subscriber's ability to remove things once they have been put on the phone. Additionally, it looks like there will be flavors of phones that will require careful consideration in the look, feel and navigation of the devices.

"Badly coded apps," yes.

But as for me, a less impolitic create than Carl, I say "sucky code."

Some of you readers are even less impolitic than I am. What do you think about Google Android and the submenu coding hazards Carl points to as quality risks?