If the iPhone had a home button and a back button, this wouldn't be an issue. But adding a physical back button is completely anathema to Apple's DNA.
Similar to the lack of out-of-the-box right-click functionality with their meece.
Similar to the lack of out-of-the-box right-click functionality with their meece.
The inconsistency you talk about only happens when authors poorly create their applications. Android's entire multitasking functionality is built on top of a stack of activities, which is easiest to think of as a stack of screen views. I start at my "desktop", click on my Photo Gallery, decide to share an image using Dropbox, and it takes me to choosing a Dropbox folder. That's roughly three activities or so (depending on how many screens within each app I have to go through) all on a stack. Built properly, if I decide I don't want to share on Dropbox while choosing a folder, I would just hit the back button, it'd pop the Dropbox folder browsing screen off the stack, and take me back to browsing my Photo Gallery. Poorly-created apps will try and "recreate" their internal activity stack when they're not supposed to. Let's say that getting to Dropbox's folder browser if I were to launch the app independently took four activities in and of itself. If Dropbox was poorly written, it would try and recreate that natural flow of previous activities when you're just trying to do a share, so hitting the back button won't take you to the Photo Gallery from sharing.
Sorry, it's complicated to explain but makes perfect sense when you're actually using a device. The tl;dr is that if app developers don't suck the back button's behavior is seamless and consistent.
Android's back button strikes me as an interesting idea that doesn't really work. If it depends on application X doing the right thing in order for the experience using application Y to be pleasant, then it seems pretty broken.
In the same vain, any poorly-written application on any device that doesn't conform to UI standards and guidelines will drag down the experience when using that device. This isn't a problem unique to Android, but it's more obvious when apps violate it due to how multitasking is built into the OS from the ground-up.
As for poorly-written apps dragging down the experience, I don't think that's necessarily a given. Obviously if you have a crappy app, then using that app sucks, but that crappy app shouldn't also make the experience of using other apps crappy.
Don't you think this is a silly argument to use against Android's back button when the post we are commenting on is a complaint about iOS's home button? By your logic, that should indicate that the home button's behavior is not intuitive and complicated... you know, because somebody complained about it.
Obviously some people disagree with the iPhone's home button behavior. Then again, they're not complaining that it's too complicated to understand, merely that it's not the ideal (or perhaps "correct") behavior.
Also, sometimes the back button in my browser totally sucks, such as when I click a link to a Twitter message and it decides to totally break my back button so that I have to press 3 times rapidly to go back. I don't want this experience with apps on my phone.
Would you rather your browser didn't have a back button at all?
And I would much rather have no global back button on my phone than a sometimes-broken one.
It makes sense with the way Android works. Applications are often interconnected. I can browse to reddit in Browser, click on a YouTube link and open it in the YouTube app, hit share, and open up GMail to send it to a friend. I can then hit back to go back to YouTube, then again to go back to reddit. Believe me, it feels so natural to me now that I find iOS clunky to use without it.
As for applications that get it wrong; that happens on all platforms for all kinds of different features -- it's unfortunate but it shouldn't reflex poorly on the feature itself unless it's particularly hard to implement correctly.
The "desktop" you're referring to is the functional equivalent of your web browser's home page. So yeah, the browser does take you there.
The idea that you have a linear sequence of "actions" across all apps seems pretty weak in a multi-tasking environment.
Google has simply extended the concept from web apps to regular apps -- and that's hardly a big stretch -- especially when all your regular apps can link to each other.
I know you have to cheer on your team here, but the back button is completely intuitive and users like it; you're creating problems based on what is theoretically possible and not what is reality.
But for example, as a user, I think it's confusing that you can open an app from home screen and can go back to home 2 different ways (either back or home button).
Also, if it's that easy for developers to mess up navigation, then it's going to create a frustrating experience for user.