Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Not that it matters but the rezound's capacitive buttons are dark red and when not backlit look quite fetching against its sleek dark surface. Sometimes I find myself staring at it. Then I think she is so smart she sees me staring. And then I feel embarrassed. You know beauty is in the eye of the beholder. And when my girl is turned off she looks prettier than yours.
The very best buttons were that on the X series. Small, hard buttons.They were ergonomically sound, and they stayed out of your way. No need for them to be large. Moto had it right. Sometimes the latest isn't the greatest. And it isn't here with this phone. IMO. I would guess the rom designers are at work to give rooters the flexibility to rid themselves of these huge things given all the threads and posts I've seen on the issue.

My biggest issue with this is that at the moment, there's no point having software buttons. That screen real estate is just sucking my battery juice.
I love the software buttons. And for the supposed wasted space on the bottom of the screen, it's very nice to have it there to rest your thumb on when holding the phone in landscape more. I can imagine it being rather annoying to accidentally hit the screen while viewing a video or browsing.

i will agree with the fact that the X phones buttons were nice.
One thing I'm surprised you guys haven't mentioned is that with AMOLED displays, when there is a black area of the screen, the display is essentially turned off for that section. So with the menu button bar being 95% black, it really isn't sucking up as much power as you think it is.
It's white you want to watch out for. That's why people like to invert the page rendering, it saves a lot of battery.
This is why the blacks are so satisfyingly black on AMOLED displays. It's intrinsic to their design.
(This was a) usability mistake by Matias Duarte ....(Though I think he's been a positive influence from a UX standpoint overall)
That said, it's been coming since Honeycomb.
The thinking was they had discoverability issues (or so they thought).
The question was actually asked ..... if anyone had these issues, only about 4 or the 140 devs there raised their hands.
And,....it's still hidden in a menu -- not much of a usability gain to move the menu to a smaller button and possibly to the top OR bottom instead of a dedicated key.
Additionally, I personally feel that while task switching is nice, there is no reason to have it replace the menu. It's less important than menu and search (IMO).
However, they did add the ability to show important actions outside the menu. So there is a silver lining here. For example, if you look at the screenshots, the search icon is outside of the menu, even though that's technically a MenuItem from a dev standpoint.
Still, I think the rationale was flawed in that it was incomplete. Some of the reasoning was correct, but I feel like they didn't consider the whole picture.
I think they re/moved search because it confused users in that it was sometime global, and other times contextual. I think they could have fixed this by giving users an option.
>if search pressed in app -> show "search this app or search global?" popup dialog....(maybe with "remember this choice for this app/all apps").
I also think that the real rationale for deprecating the menu button was because it's not a button you see on other platforms like iPhone, etc. This meant a fair number of iPhone -> Android app ports just ignored the menu completely.
So, to me this seems silly. I'm of course obsessively opinionated regarding my UI/UX with computing devices, but I think they couldn't have known the percentage that found search and menu keys helpful vs the percentage that had trouble with discovering features hidden in menus. And, considering they essentially just moved the menu around a bit, in some cases further away from the user's finger (it can be hard to tap now) I think they created more problems than they solved.
Another problem they seem to have created, not sure if they mentioned this in that post, (but I just noticed last night) is the long-press on menu used to bring up the keyboard for shortcuts. This was especially helpful for fast scrolling through alphabetical lists. I was just getting used to this and just thinking how helpful it could be. (Though admittedly I may be missing where they moved the feature).
Finally though, another silver lining, and back to the idea of having important features/actions right in front of the user. The "ActionBar" as a paradigm is actually quite a good one. Many devs (myself included) have created headers and footers to our apps to hold important buttons/information.
So it's a bit of a mixed bag. I think mostly the thing I hate about it is the execution. They forced these menus off into hard to use places, but rather they should have provided better "ActionBar-paradigm" solutions and let the devs gradually migrate. There is no reason they could not have kept the menu key there with equal weight but hidden if not used.
Devs do migrate towards best practices over time, but only when Google does a good job explaining how to get there. This is the problem they had with tablet apps. The API was so terrible, and they did such a poor job explaining it, they had to hold worldwide training sessions to teach devs how to use it.
TL;DR version
- Mostly a bad usability mistake
- Menu discoverability is still a problem
- Menus can now exists in two places
- Search is more obviously contextual
- Menu long-press = keyboard seems gone
- The execution of making things hard for devs (and users) was bad bad bad
- The idea of ActionBars is good conceptually
- The execution shows they did not take the bigger picture into account
- Hindsight is 20/20 (depending on how nice looking someone's hind is)
- Overall we're just at a stepping stone on the way to awesomeness
/end my $0.99


Wasn't it rumored last year that the iPhone 5 (4s) was looking to remove the iPhone's Home button with a capacitive button? I figured this was Google way of jumping ahead of Apple, or out-innovating them.