Should Microsoft scrap hamburgers for waffles? Why menus in Windows 10 matter

One of the most controversial aspects of the design language of Windows 10 has been the virtually ubiquitous adoption of so-chosen hamburger-style menus. Microsoft has used the three-lined push button blueprint in apps before without much detect e.grand. SmartGlass, but it was not until the OneDrive app makeover, and eventual Windows x integration did people have find.

At present, new mockups of Microsoft's Delve app is stirring up argue about whether Microsoft should use the hamburger style push button, opt for the waffle type design or something altogether different.

The Controversy

Hamburger menus aka 'SplitView controls' are found widely beyond many apps on iOS, Android and even on Windows Telephone (often from ports of apps from other platforms). The push, represented by 3, short horizontal lines stacked upon each other are often referred to as 'hamburger' due to their ASCII-similar visual representation.

The purpose of them is to hibernate carte du jour information under a uncomplicated 'button'. The functions that get inside these style buttons are often not used and more adept to settings or account data for that app or service.

The problem is, for nigh of Windows Phone's history, such buttons had no function in its pattern language (which was formerly called Metro and subsequently Modern). Instead, Windows Phone opted for an ellipsis ('…') nigh the bottom of the lower app bar to service as an indicator for more settings.

Besides the design, what people like about the Windows Phone version is the proximity to your pollex when holding the phone. Unlike hamburger buttons, which are institute near the upper left, the Windows Phone ellipsis lets users access a larger, subconscious menu without needing to stretch their thumb across the display.

Putting the above usability concerns aside, many ardent Windows Phone fans feel like the Bone is also losing its identity by going the hamburger road. Indeed, Windows 10 is littered with many examples in apps of this new style of design.

For hamburger menus

The argument for the triple line style menus is two-fold:

Familiarity – The blueprint is used on websites and competing operating systems, making them more obvious to people transitioning to Windows 10 for the first time
Universal apps – The strong selling bespeak in Windows ten – universal apps – is also its weak point. Microsoft needs to try and proceed app design between desktop, tablet, and phone relatively yet. Having one manner menu on the desktop, with a different for phone decreases consistency and may increase user confusion

Alternatives

Wedge and gesture – In the recently released newsreader app for Windows and Windows Phone, Fedora Reader brings an unusual carte choice through the use of a sliver pattern. Users can tap/swipe from the left side to bring up the menu. Even so, usability is not obvious as fifty-fifty that app has a brief tutorial to let users know how it works. This tutorial is no unlike than how Windows 8.1 teaches users gestures when the operating system is first installed. Notwithstanding, skillful design dictates that discoverability should exist natural to the user.
Waffle button (Delve) – In the new Microsoft Delve app mockups, we can run across the utilize of a 'waffle push' represented equally a square with smaller squares on the inside. Google uses such a design for its Chrome apps launcher and Microsoft takes reward of its design in Office 365 online to bring up other Office tools.

Interestingly, in the Delve mockup, we can run into the waffle button integrated into the lower app bar. Presumably it behaves in a like fashion, as tapping it probable brings upward another menu for tools.

The problem here is waffle buttons look meliorate suited for mini-app launchers, tool boxes, and non-dialog situations. This usage is dissimilar from Microsoft's current ellipsis '…' bill of fare push or the hamburger design establish in Windows ten. In that regard, we practice not run into a strong argument for its usage over the electric current hamburger push.

The best solution?

Equally a compromise, Microsoft should reconsider using the hamburger style push for hidden menus. We can name a few compromises to make this happen, at least for the Phone UI, which is what well-nigh people seemed concerned about when making complaints.

Lower-Hamburger push button into the App Bar – At the very to the lowest degree, Microsoft should consider a style merely to go along the current hamburger button, only allow it reside in the lower app bar. This move at once ensures familiarity to the user and design consistency for desktop apps. The placement may be different, but the wait is the same. Such a pattern choice also goes a long way in answering user concerns about having to reach up and beyond the brandish to pull open a hidden card. Instead, it is nigh the lesser, amend suited for one-handed usage
Combine SplitView/Hamburger button with Pivot – This solution is proposed on the Windows Phone UserVoice page (and seen above), and information technology currently has nearly 1700 votes. The thought is to make the pattern on the phone (and tablet) a dual hamburger/pivot control. Users could tap the hamburger button to reveal the SplitView, or, swipe from the left to show the same page. This is both fluid, keeps discoverability the same, and it makes Windows Phone users happy.
Come with something different – Nosotros are not designers past any ways, so our chore is not to come with solutions for Microsoft. Nevertheless, if they want to keep the Phone OS more than phone-friendly for smaller displays, they demand to take a page from Palm'southward book almost UI blueprint. Address bars in browsers should exist near the lesser, equally should menus and frequently accessed tools, which is what makes the back push button and app bar so useful on Windows Phone.

For usa at Windows Central, the SplitView control for displaying more information is less near the icon design and more about the placement. Personally, we are fine with then-called hamburger buttons, but we would much rather see them kept near the bottom of apps for easy admission instead of the upper left corner. If we could selection one pick, it would be the Hamburger/Pivot philharmonic proposed on UserVoice.

The challenge for Microsoft is finding the right balance between design consistency in apps across desktop and phone and usability in the real world. The Windows 10 squad should at to the lowest degree accept into consideration user concern over this thing.

Poll

You know the drill. Take our user poll to let your voice be heard (and become to the Windows Phone UserVoice folio too). If you lot are using our app, make sure you lot become to m.windowscentral.com to cast your vote.

We know many of feel strongly nigh this topic, so audio off in comments. Fifty-fifty improve, give usa your proposals on how Microsoft tin solve this with links to mockups. Y'all never know what could happen.