3 ms·
On that matter, I don't get Android's design trajectory: They used to have exactly that: A standard button in the OS for the app context menu, on some devices e
by xg15 1y ago
On that matter, I don't get Android's design trajectory: They used to have exactly that: A standard button in the OS for the app context menu, on some devices even a physical button. For some reason, they got rid of it in newer versions, so every interested app has to implement it itself, which of course causes to UI to become wildly inconsistent between apps. I don't understand why.
- izacus 1y agoThat was 15 years ago.
- fidotron 1y agoThey had enough fun getting app developers to support the back button properly, let alone the context menu! In truth Android has suffered from the fact everyone starts on iOS first and then ports to Android, screen by screen in many cases, meaning accommodation of Android specific UI flows simply doesn't happen. The removal of physical buttons was largely motivated by OEMs wanting to eliminate moving parts which make things far more expensive to build/test than simply one slightly bigger capacitive touchscreen.
- Kwpolska 1y agoThe problem with the old Android menu button was that you never knew whether or not there was a menu, and what would be in the menu. Some apps had navigation, some had actions. Some apps had different things on different screens. The usual pattern on Android nowadays is that hamburgers go on the left, actions go on the right. And an on-screen button is much more obvious than a hardware key, or something on the never changing bottom bar.