I'll use Gogobot as an example. From the home page of the app, the user can click the "Trending" link, to navigate to the trending page.

In this workflow, the icon in the top left becomes a back/up button.

But when accessing "Trending" from the side nav. drawer, the icon remains as the 3 lines representative of the nav drawer.

I understand this design decision in using the conceptual model the user has of the app, though this creates inconsistency when on this page. Getting home is not always the same workflow.

I'm curious as to what the common/accepted thing is to do in this situation.

2 Answers 2


If you think about it, the default iOS guidelines somewhat reflects Jef Raskin's idea about zooming interfaces:

As you work your way deeper into the navigation hierarchy transition animations will slide you towards right and if you move back they will slide you to the left. If there is some sort of contextual popover it will always slide in from the bottom.

Even though we are not navigating a canvas as explicitly as we are in for instance Prezi, that's still what we are doing and the consistent slide-animations provides a subtle way to give the user cues about where in your app he is.

If you ad an off-canvas menu and a hamburger icon to that pattern, the idea is that the menu must be the first level of navigation and from there on you drill down in the hierarchy by moving to the right.

For this reason I would argue that you should replace the hamburger icon with a back-button whenever you are on subpages, as to not ruin the conception of this "virtual world" you are navigating. This is actually the way Facebook worked "pre iOS7". In addition Facebook allowed you to get directly from a subpage to the menu by swiping from the left, but I don't think a lot of people knew about that.

If you have a deep navigation hierarchy, however, this might not work as the user might end up having to press back > back > menu too often. In that case you might have to stick to the hamburger and then either skip the back button altogether or maybe provide it within the menu.

As for Android you should not provide a back-button in-app, as it is already available on the phone, either as a real or a soft-button.


I would suggest a Back icon in both scenarios. It will provide a consistent look. Also, I don't feel anything wrong with displaying a Back icon on a screen where you move through Navigation icon.

  • The problem with that approach is that it almost defeats the purpose of the navigation drawer. I see the goal of the drawer is to access any page from any other page (like a large tab bar). Jul 15, 2014 at 13:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.