I frequently get designs for android apps featuring iphone-like functionality. In this case it has to do with a back button integrated in the layout as part of the header (on the left side).
Android already comes with a back button – although I have seen some technophobes completely ignore the back button and complain about the flow of an app. (“why is their no cancel button, 1 star, uninstall” push back)
First of all, recreating iOS elements is tedious and counterproductive, but in this case do android users expect a back button in the header at this point? Would a “back” button subtract from a UX at all?
For instance, Android users expect to long-click items in a listview to see what happens – often for options or to delete. Or at least the assumption can be made.
But for a back button in the layout, do Android users get enough apps with iOS-style back buttons to simply expect it?
Insight appreciated
Implementing a back button taking up screen real estate really has no point or benefit for an Android user. The only thing it does is cramp the UI for no real reason since the back button already exists.
Android users don’t expect a software back button, since it’s simply not the Android way of going back and not many apps have it.. hardly any apps have it actually.
Not only is a software back button completely unnecessary but it could even irritate the user since it could be seen as trying to “iPhone-ify” the app. Not popular at all for some Android users 😉