Let’s assume for a minute that Nokia had decided to go Android rather than Windows Phone.
We would be 20 days away from seeing the first Ice Cream Sandwich powered smartphones from Nokia announced at Nokia World 2011. Now, what’s the problem with that? Take a look at this video:
Now, from a design perspective, what are the problems in this video? First of all, note where the interface buttons have been positioned. There’s no physical buttons per se, but they are still physical buttons, they are just taking up real-state from the screen. If a company is going to come up with a “buttonless” interface, they better come up with something like SwipeUI. Moving the existing buttons to the screen does not cut the deal. Second point: you have to use bigger screens since the buttons are now taking more space. The result is a horribly big screen that no one will be able to handle, or a smaller screen whose effective usable space has been reduced by these “physical” buttons. From every perspective, Android Ice Cream sandwich seems to have some design failures deep embedded into their UI. Let’s not take into account the widget screens that *99% of the users don’t bother to arrange, differentiation of a crowded platform, the whole Motogoogle deal, and apps that have inconsistent UI guidelines.
Phew… I am so glad Nokia and Elop went Windows Phone. We are just 20 days away from Nokia World 2011 and Nokia’s first WP. Stay tuned, because we’ll be covering the event live!
*Obviously an hyperbole, I don’t know the exact percentage, even if there’s one, but my point is that most users don’t bother to arrange the widgets on Android.