17 ms·

Please don't use hamburger menus on iOS. http://blog.manbolo.com/2014/06/30/apple-on-hamburger-menus http://blog.manbolo.com/2014/06/30/apple-on-hamburger-menus

hnriot 12y ago
Apple are just pissed they didn't think of the hamburger menu first. This is terrible advice, the are understood by all and the few people that don't know where this mysterious control will take them can just click it and see. It's not like it's the rm -rf button.
- calvin_c 12y ago
  Apple doesn't usualky care if someone else did something first though. If they decided the Hamburger Menu works well in particular use cases, and want to use it in an app of theirs at some point in the future, they'll just drop it into a new iOS SDK and hope everyone forgets about this advise.
- panzerboy 12y ago
  Disagree, they took the pull-to-refresh from Tweetie and integrated it into iOS because they thought (rightly so) that it makes sense. If they would feel the same about the hamburger menu, then they'd do the same.
Hytosys 12y ago
Is there a solution for when you have anything more than 5 primary sections in your app? The Apple suggestion would probably be to reconsider the scope of your app, but what if that's just simply not coincident with your goals? Shit out of luck?
- accatyyc 12y ago
  Actually, the UITabBarController supports more than 5 items perfectly well. It automatically adds a "More" button if you add more than 5 items. There you can cram everything in that you would otherwise have put in your hamburger-menu. Also, if you enable it, it automatically allows users to choose which tabs that goes where, just like in the music app :)
  - deleted 12y ago
    [deleted]
IkmoIkmo 12y ago
Oh wow, moral of the story is that hamburger menus, like every other design decision, requires careful consideration, and has its place in modern app design. Who knew. Not using hamburger menus doesn't magically make your app better. You need alternatives. Would I suggest a hamburger menu for a menu with 3 items? No of course not. But if you have an app with 10 core menu items, there's not many alternatives. You could try to force and cram that into a navigation bar with 3 item-categories, which open pages with deeper navigation trees, and that'd tick all the 'why-not' boxes of the menubar the article mentions (like unnecessary clicking, users that can't find their information, don't know where they can go or where they are on the page etc etc). Fact is that a lot of users are indeed familiar with hamburger menus these days and they're becoming a type of standard just like a back arrow is universally understood, and find their way outside of apps, too. (like the Chrome browser which I'm typing this on right now.) Combine that with the fact the top navigation bar's title telling you where you are, and a non-crammed side menu showing you exactly where you can go, it's certainly a decent solution for many apps.
coupdejarnac 12y ago
Well, all my companies apps from now on will have the drawer menu. First, users are familiar with them at this point. Second, the drawer looks a lot nicer than the UITabBar as suggested below. I haven't heard the the term "hamburger menu" until now. That's a pretty condescending term for a UI widget that looks visually pleasing (to many people). For what it's worth, this is what I have been using: https://github.com/erichoracek/MSDynamicsDrawerViewController https://github.com/erichoracek/MSDynamicsDrawerViewControlle...

hnriot 12y ago

Apple are just pissed they didn't think of the hamburger menu first. This is terrible advice, the are understood by all and the few people that don't know where this mysterious control will take them can just click it and see. It's not like it's the rm -rf button.

calvin_c 12y ago
Apple doesn't usualky care if someone else did something first though. If they decided the Hamburger Menu works well in particular use cases, and want to use it in an app of theirs at some point in the future, they'll just drop it into a new iOS SDK and hope everyone forgets about this advise.
panzerboy 12y ago
Disagree, they took the pull-to-refresh from Tweetie and integrated it into iOS because they thought (rightly so) that it makes sense. If they would feel the same about the hamburger menu, then they'd do the same.

Hytosys 12y ago

Is there a solution for when you have anything more than 5 primary sections in your app? The Apple suggestion would probably be to reconsider the scope of your app, but what if that's just simply not coincident with your goals? Shit out of luck?

accatyyc 12y ago
Actually, the UITabBarController supports more than 5 items perfectly well. It automatically adds a "More" button if you add more than 5 items. There you can cram everything in that you would otherwise have put in your hamburger-menu. Also, if you enable it, it automatically allows users to choose which tabs that goes where, just like in the music app :)
- deleted 12y ago
  [deleted]

IkmoIkmo 12y ago

Oh wow, moral of the story is that hamburger menus, like every other design decision, requires careful consideration, and has its place in modern app design. Who knew. Not using hamburger menus doesn't magically make your app better. You need alternatives. Would I suggest a hamburger menu for a menu with 3 items? No of course not. But if you have an app with 10 core menu items, there's not many alternatives. You could try to force and cram that into a navigation bar with 3 item-categories, which open pages with deeper navigation trees, and that'd tick all the 'why-not' boxes of the menubar the article mentions (like unnecessary clicking, users that can't find their information, don't know where they can go or where they are on the page etc etc). Fact is that a lot of users are indeed familiar with hamburger menus these days and they're becoming a type of standard just like a back arrow is universally understood, and find their way outside of apps, too. (like the Chrome browser which I'm typing this on right now.) Combine that with the fact the top navigation bar's title telling you where you are, and a non-crammed side menu showing you exactly where you can go, it's certainly a decent solution for many apps.

coupdejarnac 12y ago

Well, all my companies apps from now on will have the drawer menu. First, users are familiar with them at this point. Second, the drawer looks a lot nicer than the UITabBar as suggested below. I haven't heard the the term "hamburger menu" until now. That's a pretty condescending term for a UI widget that looks visually pleasing (to many people). For what it's worth, this is what I have been using: https://github.com/erichoracek/MSDynamicsDrawerViewController https://github.com/erichoracek/MSDynamicsDrawerViewControlle...