4 ms·
Good riddance. I hate when I look around how to do something and it was hidden in the menu button the entire time. It was completely unintuitive when there were
by pixie_ 15y ago
Good riddance. I hate when I look around how to do something and it was hidden in the menu button the entire time. It was completely unintuitive when there were menu options to use, and when there were not. That's why I designed the android version of my app, like the iPhone version, and put all possible options in the on-screen design itself. It's funny too because other android devs told me 'nooo use the hard buttons' screw that, even the back hard button is unintuitive at times, better to put it all on the touch screen.
- socksy 15y agoA badly designed interface will still be hiding desirable features behind an impenetrable "menu" option, only now you have to use the capacitive touch screen in order to reach it. The physical button was at least consistent and easier to press (or at least, on my device). If the menu button is unintuitive, that might be indicative that a redesign has to take place, rather than that the menu button concept is broken. I don't see what advantage this change has?
- pixie_ 15y agoThe difference is - when the menu is on the UI then you KNOW there are menu options available. The hard menu concept is broken because hitting the hard menu key is a crap shoot, it might do something, it might not, who knows. The problem is also developers like you think normal users think like them, they don't. Google has obviously figured this out, though pretty late in the game.