Also having different UI contentions doesn't mean someone else is doing something wrong. We port games from iOS to Android at Apportable (YC2011) so we deal with converting concepts every day. Neither is better or worse.
Also having different UI contentions doesn't mean someone else is doing something wrong. We port games from iOS to Android at Apportable (YC2011) so we deal with converting concepts every day. Neither is better or worse.
Any?
While the Galaxy Nexus has onscreen navigation controls now (and the Nexus7 followed suit), both the One X and the Samsung Galaxy SIII have dedicated capacitive back buttons "off screen". On the OneX the button is in the normal place (on the left) and is oddly (but in keeping with the SII) on the right on the SIII.
Tablets will move it to the bottom in whatever orientation you are in which good but the issue with that though is that the screen dimensions change and I can't tell you how frustrating that is in games and changing their OpenGL projections on rotation. Not only do you have to handle rotating your content for the orientation, but then you have to adjust for the screen size virtually changing sizes. For some games and apps (like ZenBound) this breaks things by moving the virtual center point of the screen.
Irrespective of where on the bottom row it is, it's still more useful than the top left of the iPhone 5.
Also, since Jelly Bean I can't say I've ever had an unexpected result by pressing the back button. As far as I can tell it always does The Right Thing since they got their guidelines formalized, at least with the couple dozen apps I regularly use. I have to say on balance I've been more annoyed with iPhone apps lacking necessary navigation buttons on some screens more than Android back button inconsistency.