This is my intuition too. The iPhone model is a single app page swimming in a top-level sea with others. For some things, that's fine. But for many apps (browsers are obvious, but also games that have splash menus, anything with a folder-like hierarchy, etc...) there is a clear and obvious "back" metaphor. And iOS just doesn't do back.
That's not an excuse for Android apps that use it inconsistently obviously (though the framework is pretty good about making sure obvious implementations do the obvious thing). But on the whole I think it's a very good feature.
Likewise, "menu" is something that almost everything has and probably deserves a hardware button (or at least a button with a persistent location and presentation -- the Galaxy Nexus apparently has no "hardware" buttons outside the touchscreen).
The "search" button that so many Android phone have, on the other hand, is completely beyond me. Ridiculous.
Sure, but I don't think that's the right criteria. Any task can be made faster by associating a fixed button with it. But every fixed button has a cost. If you do a ton of "searching" then sure, this is good. My personal usage would be improved with a "go directly to email" button. Most people don't search that much. Or if they do, they do it from a desktop widget (even faster IMHO). I don't think it's an appropriate usage for the very precious physical space on the front panel.
That's not an excuse for Android apps that use it inconsistently obviously (though the framework is pretty good about making sure obvious implementations do the obvious thing). But on the whole I think it's a very good feature.
Likewise, "menu" is something that almost everything has and probably deserves a hardware button (or at least a button with a persistent location and presentation -- the Galaxy Nexus apparently has no "hardware" buttons outside the touchscreen).
The "search" button that so many Android phone have, on the other hand, is completely beyond me. Ridiculous.