Or we can look at it from the other side. "Where do I find the settings for this app?". Is it in File, Edit, View, Tools or Help. The answer depends on the app. Menus can be well organized or poorly organized but I don't think we should be banishing menus. The hamburger icon is just an iconic, space efficient way to say "menu"
For example, on Mac: https://developer.apple.com/design/human-interface-guideline...
And on Windows: https://docs.microsoft.com/en-us/windows/win32/uxguide/cmd-m...
> "Where do I find the settings for this app?". Is it in File, Edit, View, Tools or Help?
On Mac, it should be in the "App" menu and called "Preferences...", it should be the first item in the menu, except if you have an "About YourAppName" item which always goes at the top with a seperator underneath.
On Windows, it should be in the "Tools" menu, and called "Options...". 4 On Linux, it should be under the "Edit" menu, and called "Preferences".
If it's not, then the app (in my opinion) is broken. Of course, many apps are lazily ported across platforms or "hamburgerized". The Windows situation is obviously also more messy because of the newer "ribbon" standards complicating things a bit, but there are right answers.
(edit: fixed links)
> On Linux, it should be under the "Edit" menu, and called "Preferences".
This one is a stretch, there are no such consistent and agreed-upon guidelines.
My point here is that just because things can be abused (or even, in the case of desktop applications, are almost _always_ abused), doesn't mean the general concept is useless or should be removed from applications. I would recommend instead of trying to cram a hundred possible actions into a tiny icon bar at the bottom of your iPhone, or removing 97 of those actions from the app itself and leaving just the most basic three down there, to maybe consider building a sensible and well-arranged menu layout _if and when_ you need more than those three that you can fit at the bottom.
You mean well researched guidelines with tons of evidence behind their decisions [1] that are as relevant today as they were 20 years ago.
> almost all applications ignore.
That most current applications ignore because people think they are ancient rarely updated guidelines.
This is especially evident in the MacOS world. HIG were the guide on the platform, and developers tried to adhere to them. And then the new breed of "designers" took over and even Apple breaks nearly every single one of them [2]
Microsoft has always been worse when it came to enforcing consistency of user interfaces, but even their choices were never random until quite recently [3].
[1] Apple's original HIG even had a bibliography section because it was actual research, and not some Dribble showcase: https://twitter.com/andy_matuschak/status/144740917559669965... and https://twitter.com/andy_matuschak/status/144771024771228057... etc.
[2] See, e.g. their abomination of an App Store https://grumpy.website/post/0RsaxCu3P
[3] Even the ribbon menus they introduced in Office weren't a random choice. They surely are now. See the Why the UI blog series: https://web.archive.org/web/20080316101025/http://blogs.msdn...
> And on Windows: https://docs.microsoft.com/en-us/windows/win32/uxguide/cmd-m...
Both links return 404.
Nowadays it's just a random hodge-podge no one knows how to use properly.
Does it ? This is the issue when people see no more as their own OS.
In the past, just like today, there were multiple modes to exit a program. One of them is to press Exit and the programm will exit cleanly. The other is to press the X in the window corner in Windows ( or send a close message from a window manager) which, depending on the implementation, might lose data. There is also the option to kill the process. Now in my opinion this Exit is a good thing and it is clear what is doing.
Well, unless it's an Electron app. Which is another good reason to avoid them altogether.
A poor menu layout can be fixed. A hamburger menu will always be a byzantine mix of everything because everything has to be in there. There is no organization, except flyout menus--which were a problem with traditional menu designs, but you could organize without them.
Hell, some applications have just moved the traditional menu behind the hamburger. Why? Because that was a good way to organize operations, even if it wasn't perfect, or wasn't always perfectly implemented.
Happy to know I am not the only one who considers this weird.
It would probably make more sense to have an "Application" menu before "File". It could contain things like "About", "Help", "Setting" and "Exit". (Especially in cases where the current "Help" menu only contains "Show help" and "About". If it has more than five items, then I'd say it deserves a separate menu.)