Last updated on April 22, 2014
The iPhone distinguished itself with a single home button for returning from an app to the launch screen. While its functionality may have been strained a bit as the platform has progressed. e.g., having to tap twice to bring up the app switcher, its single UI depression concession made a statement about minimalist simplicity that few platforms (webOS may be one example) have answered.
In contrast, Android launched with four major UI buttons (Home, Menu, Back and Search) and Windows Phone launched with three (Windows/Start, Back, and Search). Exactly how many – if any – buttons is optimal can be debated by user interface experts or considered personal preference. As is the case with much of what I consider Android variation, the media has jumped upon the tendency for different vendors to implement the Android button order in a different way, even in different handsets from the same manufacturer.
I don’t see that as such a major issue, but the Search button, in particular, always struck me as gratuitous. Yes, we know Google is a search company, but that doesn’t mean I need a search button omnipresent on my device. And I was somewhat disappointed that Microsoft followed suit (since, of course, Bing is really important, too).
Now Google, if not having so much seen the error of its ways, will give licensees the option to forego any and all buttons in Honeycomb tablets and presumably Ice Cream handsets. Perhaps this was due to the influence of Matias Duarte, a notion that buttons are trickier to place on a tablet versus a generally vertically oriented handset, or simple feedback from partners.
The drawback is that now, in addition to potentially having different button layouts, Android devices may now have different combinations of buttons and gestures for the same task. Regardless, these devices now have the potential to look cleaner and more streamlined because of the change. Perhaps that’s one of the liberties that Nokia will feel free to take as it balances its unique customization privileges against compromising the consistency in the Windows Phone ecosystem.