4 ms·
I can stand these pretty easily :) The back button annoys me most in email apps - I think it's the stock Email app - when you scroll through all your unread em
by barrkel 14y ago
I can stand these pretty easily :)
The back button annoys me most in email apps - I think it's the stock Email app - when you scroll through all your unread email, and instead of doing an "up", it decides to go back through all the messages your just read. Meanwhile, it upsets me in other apps where, when I open a file from a file browser, and press back, it doesn't take me back to the file browser; it takes me "up" in the application that opened the file.
So this is the heart of the inconsistency. Sometimes I want up, and sometimes I want back. It's context and app dependent. I don't really see a way to do it right without letting apps fiddle with the stack.
Re icon size difference: I actually find this difference helpful in distinguishing one icon from another. On iOS, most icons are rounded squares, and are less visually distinctive. I had to go completely overboard with classification folders to make it easier for me to find stuff on my iPad.
A lot of the other points are QA polish. I don't disagree with many of them, but they don't really bother me either. On the multiplicity of messaging apps, I don't really see that as a problem either, since I don't use any of the Google ones apart from the SMS app when I'm forced to; I use WhatsApp instead (yes, insecurity, I know).
- georgemcbay 14y ago> "I don't really see a way to do it right without letting apps fiddle with the stack." Apps can (and often do) fiddle with the stack, at least as it applies to their own Activities. Of course, they do so inconsistently (even Google's own apps do so inconsistently). In any case, Google clearly recognizes the issues with the back button and have been trying to fix it (see, eg: http://developer.android.com/design/patterns/navigation.html http://developer.android.com/design/patterns/navigation.html ), but their attempts to fix it have also been clumsy. For example what they call the "up button" (both in the API and in their designer docs) visually looks like a back button. Trying to distinguish between "back" and "up" is great, but then making your "up" button look exactly what any sane person would expect a "back" button to look like is goofy. Not only is this confusing for users, but it is also confusing for developers, resulting in different apps handling the situation differently even though the app developers have tried to do what they think the right thing is. So the solution is in many ways more confusing than the situation before they tried to fix it.
- Shooti 14y agoThis was asked in one of the Google IO 2012 videos that was recorded, and their response is that it originally looked like an like a triangle to the left of the icon in Honeycomb, but nobody noticed it was there.