6 ms·
The back button in previous Androids was mostly fine with a few overloaded functions that led to some understandable inconsistencies. It might get stuck going b
by guelo 14y ago
The back button in previous Androids was mostly fine with a few overloaded functions that led to some understandable inconsistencies. It might get stuck going backwards in the browser or it might dismiss a dialog or keyboard instead of going to the previous screen, but the annoyances were minor.
To fix this they inexplicably added a second iOS-style header back button (which is called Up even though it is normally shown with a left pointer). The combination of two back buttons and the difficulty of understanding it, even for developers who have read the long style guide[1], is an absolutely baffling design decision. There is no way that users can intuitively learn what these buttons do. Add the inconsistent implementations and it's a usability nightmare.
[1] http://developer.android.com/design/patterns/navigation.html http://developer.android.com/design/patterns/navigation.html
- gbog 14y agoIt is not two back buttons. It is like a browser: a history back button at browser level, and a suggested top left clickable app icon that usually brings you to app main screen, or some intermediary hub screen if the app is really multiple apps bundled in one. It's true that it can be confusing at times but the reason is that of inconsistencies and some bad behavior of some apps, eg hooking the back button. Don't think people are that stupid, they can understand such a simple model.
- fireflash38 14y agoIt becomes frustrating when the activity stack is invisible, but still accumulating additional activities in app. Old Gmail was especially egregious with this, where you could hit the back button 10+ times and end up switching between emails you've viewed days previously before you actually back out of the app. I love the general idea of the separate Up and Back, but I'd compare it to XP-era Windows explorer rather than a browser (though both are valid comparisons, I just think Explorer is closer). It just runs into issues where the developers have to try to divine what exactly you are wanting to do at each instance when you hit back. Sometimes users want to go back to where they were before when they hit back, sometimes they want to go 'back' to the home screen of an app - this is what the 'Up' navigation button should exist as, but seldom does. What about if you go Up in app, then hit the back button? Should you exit out of the app? Go back to where you were in app? Go back to the previous app? All are valid cases. It really does all come down to consistency.
- alanctgardner2 14y agoI actually really like this idea: If you're in an email and you open a picture, you go to Gallery. Now you can a) Go 'Up' to the main Gallery activity, or b) 'Back' to your email. That seems pretty intuitive, a lot of the time I've been frustrated by the lack of an 'Up' option in apps.
- shardling 14y agoIt is a good idea -- it's confusing if you're switching from old android devices, but only until you change your mental model. Someone starting out with jellybean as their first touch OS would have few problems... at least if apps actually followed the guidelines. >_>
- gareim 14y agoExcept it doesn't really work that way. I'm texting in WhatsApp when I get an email. I open the email from the notification area, read it, hit back, it exits to the home screen and not WhatsApp. When I already have a home button, why should the back button be used more for home (besides the actions in the app) rather than "up" a level to a previous state like it's supposed to?
- ljf 14y agoThat is what kills me in iOS, I regularly get an email with a few urls to check. Heck even one is a pain: open email, see link, click link, browser opens, check link, press home button, swipe to screen with email client, press email, press email account was in before, scroll to email, press email, scroll to point I was at in email before I was dragged away. In android it just a single back button away, or if something goes wrong, when I return to email I'll be where I was before, correctly scrolled in the email I was reading. I miss android!
- nicholassmith 14y agoNot to say that iOS isn't a pain for rapidly moving between tasks, but if you double tap the home button Email will still be in there so you should be able to swap back quicker.
- BenoitEssiambre 14y agoThis. The back button is one of the most powerful feature of android. It has always been great for navigating between apps even though it is a bit confusing. Adding a _second_ back button (a third if you count the home button as a long jump back) was the worst decision the android team ever made. I mean, I understand where they were coming from. When a user jumps between apps he or she might want to be able to navigate inside the apps not just between the apps. However, a single back button with an already too flexible implementation was confusing enough that adding even more navigation options was a terrible decision. One back button forced apps builders to make their app usable within a single thread of history which is a Good Thing. When a user jumps from app to app and suddenly decides she doesn't want to follow the current line of history, it is not unreasonable, and much less confusing, to make her go through the device home screen to get access to the start screen of the app and its full navigation tree. When an app opens another app it should be only to give access to a particular section of the second app that is relevant to the first app. A single back button also helped with the recent apps list mismatches. The mismatches happen when an app is opened from another one and happened less when this type of navigation was for limited specific actions that brought you back to the original app.
- Mythbusters 14y agoThe one in Windows phone acts up much more consistently then. The back button takes you to the previous screen in the app until you get to the home screen and then it takes you back to the page where you launched the app from.
- ljf 14y agoI love the back button. After losing my uninsured galaxy note I'm stuck with iOS for a bit. I literally hate the way that I can click a link in an email then have a mammoth task to get back to the email app, then the correct account, then the correct email, then the correct part of the email to find the next link I've been sent so I can start this dance again. Roll on the launch of the note 2, back to a phone and OS that allows me to accurately place the cursor when I'm editting text!
- 14y ago
- king_jester 14y agoI don't really agree that the home button behavior is confusing. The home button complements the back button to give you two options: stay in the app or go back to where ever you came from. I think the more real problem is that developers have been really bad at choosing the right default behavior for things like launching from notifications, widgets, or intents. These things are often the most likely way someone will interact with your app, so implementing them needs careful attention. At a minimum, an app like Gmail should offer a configuration to change the behavior even if they want to choose a weird default that overrides standard system behavior.
- cbs 14y agois an absolutely baffling design decision. There is no way that users can intuitively learn what these buttons do Says you, I picked it up pretty easily over a few days.