> "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 t

> "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.