7 ms·
Navigation Should Be Boring
- platz 8y agoWhat alternatives are there to the ubiquitous "hamburger menu" for navigation that look good on both mobile and desktop? Does anyone think that that static links are better than flyouts?
- coldtea 8y ago>Does anyone think that that static links are better than flyouts? Only end users, but who cares about them?
- wlesieutre 8y agoI wanted to check out the menu at a local pizza place the other day and this was my experience: 1) Menu link, one of two important things on the entire site (the other one is hours) is buried in a hamburger menu 2) The menu is implemented as a fixed-size page designed for an iPad Mini (which they use as menus at the tables) 3) Different types of items (appetizers, entrees, pizza, drinks, etc) are in a horizontal bar across the top, with large font size. Since it's a fixed iPad Mini width, this scrolls horizontally. Less than half of them are visible at a time. 4) Individual items are listed by name, thumbnail photo, and price for each size. Want to know what toppings are on their "Eighth Street" pizza? Click on it! Then click to close that and click on the next menu item. Do this for each pizza, then try to remember what the one that sounded best was called, and probably go through half of them again to get back to it. Super efficient way to find which pizza you'd like. I think the restaurant understands in concept that they should have a website, but I don't think they care to think about it beyond that. EDIT: I just revisited this and you actually can get to the menu without the hamburger link. It's designed as one of those pages where the content is centered (vertically and horizontally) with a bunch of white space as a full page thing, so it doesn't look like you'd need to scroll, but there's actually more content (including a second link to the menu) if you try scrolling down. I'll blame this partly on Apple for taking away the always visible scroll bar indicators and partly on this stupid web design trend of giant "paginated scrolling" pages that don't look like there's anything running off screen that you'd need to scroll to.
- titanomachy 8y agoOr, the cost of anything but the most basic development is prohibitive and their margins are too low.
- wlesieutre 8y agoI suspect they've locked themselves in to whatever crappy menu system the iPads run on. Works well enough in-house, and the website's menu existence is an afterthought. Not great since they do takeout, but for the most part I think it's a sit-in restaurant. If the menu vendor had bothered with responsive design it wouldn't be half as bad, but "here's an iPad viewport centered in your browser" must have meet the contractual requirements. A $10/month Squarespace subscription is pretty damn cheap and IIRC you don't need to know much of anything about web development to set that up.
- coldtea 8y agoDo they also cut corners with their kitchen? And the cost of web development has never been lower.
- rat9988 8y agoWhy do you resort to such sophism ?
- coldtea 8y agoWhat exactly is the "sophism"? That the cost of web development has never been cheaper is a fact. That the restaurant website is important -- that's how customers find out about it -- and shouldn't be left behind because of "small margins" is also not very controversial. If the margins are so small as not to afford some $1000 (or less) for a decent website, then what other corners have been cut?
- dwaltrip 8y agoIt is likely they don't realize or understand the actual issue. The decision-makers probably don't ever look at the menu on a mobile device. Even if they recognize that there is an issue, they may be intimidated by the prospect of finding someone who can fix it. This is in stark contrast to kitchen-related matters, which they are likely much more experienced at identifying and dealing with.
- wtallis 8y ago> What alternatives are there to the ubiquitous "hamburger menu" for navigation that look good on both mobile and desktop? Step one is to stop trying to make the same UI for mobile and desktop. You're guaranteed to end up with a result that is insultingly bad for at least one of those segments of your user base.
- deleted 8y ago[deleted]
- hombre_fatal 8y agoThe issue is that you can always show more options on desktop. On mobile, you naturally have to choose fewer menu items to display. Where do you put the rest? The worst is when the mobile version doesn't have those additional menu items at all, anywhere, and certain things are simply impossible to do on mobile. Tossing the lower priority items onto an additional page (hamburger menu) when screen space is limited is often the fair and simple trade-off. "Don't use hamburger menus" is often coupled with the hand-wavy "just create novel mobile UI that doesn't need it", but the reality is that the items in hamburger menus usually don't need their own top-level button on a small screen at all. That's why they're hidden behind a click. They aren't worth the clutter, but they're still things a user may want to do. In my experience, seeing that just about everything uses the hamburger menu, like the Kindle, it's a concession users are willing to make in order to use a small device. What exactly is the trade-off here without downsides?
- platz 8y agoI would not characterize the "hamburger menu" as an "additional page". I would call that a "flyout". An additional page means that you navigate away - so you'd then be navigating to a sub-page that displays more links, if you did it that way.
- hombre_fatal 8y agoAgreed, I phrased it that way because, for some reason, an additional page seems more agreeable to people in these discussions, yet a hamburger menu is really just a much more convenient take on that: a quick flyout that only covers part of the screen.
- elicash 8y agoLink bars: http://growthrock.co/ecommerce-mobile-home-page-navigation/ http://growthrock.co/ecommerce-mobile-home-page-navigation/
- woogiewonka 8y agoNice to see an article by Devesh linked here.
- ken 8y agoHave you used iOS? Apple rarely if ever uses hamburger menus in any of their software.
- tniemi 8y agoOr, you could say "Don't make me think": https://en.wikipedia.org/wiki/Don%27t_Make_Me_Think https://en.wikipedia.org/wiki/Don%27t_Make_Me_Think Unfortunately UX people seem to hate boring and/or simple stuff...
- RealDinosaur 8y agoIt doesn't look good on a portfolio. If the mockups are boring then you have done your job well. The problem is that mockups that stand out, are what gets steak-holders interested. Some of my design work involved selling concepts, and the ones that sold were those that broke the UI conventions in some way. Those features that broke the conventions were then set in stone! Instant regret. Uniformity is bad! They want bright colors, low contrast text, and each page to be unique. If every page looks the same then they obviously are paying you too much. This is how lots of print designers get started in the web-industry, and wowing people is the main objective. UX doesn't come into it. The other thing that I've found happen, is business requirements sometimes further complicate the UI. We had a simple app that was a report of damages as part of a return process. This was mandated by the project manager to be displayed as a progress bar. Sofar as a vehicle that was 100% fucked would be 100% complete. I tried to push back with exclamation points for damaged areas, but progress bars were already sold to the customer.
- fipple 8y agoMmm... steak-holders.
- RealDinosaur 8y agoI wondered if anyone would pick up on that. :-)
- woogiewonka 8y agoIf you have to sell yourself on a portfolio then you are talking to the wrong prospects. Some of my best clients have never seen my portfolio. Even the ones who start off with "where can I see some of your work" forget all about my portfolio by the time we are done speaking. If you do a proper job of explaining what your job entails, what the client gets out of it and where to focus priorities, you'll likely never need to show your previous work. Sadly, most junior UX wannabes don't understand this and continue to try and impress people with portfolios. They get the client they deserve. This does the industry no favors, but I could care less. Once that business is butt hurt by a previous designer and decides to commit to a real process, we can talk. If you are part of the problem, you don't get to complain. Be the one designer who does 80% data and 20% design. Just say "no" to stupid ideas and squash them like a bug. If you are an entrepreneur running a business, you are in charge. Do you tell a plumber how to do his job? No. Then act like the plumber and do things the right way and tell them to thank you later. Results speak for themselves.
- toss1 8y agoAbsolutely key ==> "Their “attention span budget” can thus be spent considering how your new thing can fit into their lives, rather than trying to recall ..." UI is all about minimizing user workload, and NOT requiring people to learn redundant knowledge. Take advantage of every bit of knowledge that they already have from previous systems. Every split second they must use to figure out your new way to do someting they already knonw how to do another way, is squandered and redundant. Eliminate it. Work hard to eliminate it, so that they can focus on your real innovation Note: even if you have actually figured out some truly better UI controls, they must be not merely noticeably better, but better by a margin that exceeds the cognitive costs of both the new learning & the ongoing disconnect from the main UI (and remember, they don't live in your app the way you do). E.g., the fad towards 'clean interfaces' with minimalistic or totally hidden hotspots may look prettier, but is a huge waste of user time and generates animosity towards the product. Just the example of Gmail hiding the Trash folder; I don't know how many times I've had to help people telling them that they need to scroll down, click on the "MoreV" word (not even transiently highlighted as a control), then scroll down again... I use it so little I've even had to Google it myself in a rush... That and 1000 other things are not an improvement, they are a waste of people's time for some design conceit. Of course, if you want to give off signals that your core product ideas aren't all that uniquely useful, and you need to create cute & costly UI differences as distractions, by all means, go right on ahead... If you have a real innovation, the best thing you can do is put zero redundant learning between your user and your key innovations.
- toss1 8y agoThere may even be a good coding analogy way to think of this. Consider that the user base already has a set of pre-installed libraries and callable routines for most UI functions. These were effectively created by MS and Apple by their design process, and installed in the user base by endless familiarization, then extended by Apple & Android on mobile devices. Those libraries are now well embedded and installed. Make calls into those existing libraries. Don't force the user to rewrite and reinstall new libraries (unless absolutely necessary).
- rco8786 8y agoCan we all agree to stop putting the "back" button in the top left of the screen though? It's literally the worst possible place to put a button that has a very high likelihood of being used.
- ziftface 8y agoI'm actually fine with a back gesture in this case. I think it's pretty commonly known that you can swipe back. And it's way more accessible than the top left back button.
- Macha 8y ago> way more accessible It can be too accessible, see got example the swipe left/right to change articles gestures Blogger had (has?). I could never scroll a long article to the end without accidentally navigating elsewhere.
- ziftface 8y agoI agree, those are awful. Edge swiping from the left is a lot harder to do by accident though.
- rco8786 8y agoEdge swiping from the left is nearly as cumbersome as reaching to the top left of the screen, for me. Not to mention the general finickiness of edge swiping (at least in my experience).
- minikites 8y agoRight from the article: >many users don’t even find gestures
- saagarjha 8y agoThis is not an issue on any mobile platform. On iOS, you can swipe to go back, and on Android the back button is at the bottom of the screen.
- LoSboccacc 8y agoI mean, I wish I could use a navigation bar on the bottom of my web app, but on ios touching that area springs back the browser chrome and on chrome pinning something at vh will place it out of the screen when the address bar is visible.
- RealDinosaur 8y agohttps://medium.com/@eventbrite/mobile-safari-whyyyy-73cf61039047 https://medium.com/@eventbrite/mobile-safari-whyyyy-73cf6103... Here's a fix and description of the issue, but yes. The bottom of the screen will take trial and error. I've been messing around with fullscreen modals for interactive content, and iOS is the main problem, 100vh != 100% != position: absolute; bottom = 0; top = 0;
- myguysi 8y agoYeah this is actually something I wish Apple would change. For once the material design team are ahead of them by adding a bottom app bar: https://material.io/design/components/app-bars-bottom.html https://material.io/design/components/app-bars-bottom.html
- nine_k 8y agoI'd say that ideally navigation should be invisible. That is, natural, obvious, and requiring minimal cognitive load. If this is not possible, "boring" navigation is the next best thing: it's tedious but obvious and predictable. Highly creative navigation should be an exception, for art pieces of web design. Please note that the presence of "boring" navigation does not prevent having "advanced" navigation, which is a faster equivalent for power users. E.g. many sites have efficient keyboard navigation. But that advanced navigation should complement, not replace the easy-to-discover "boring" navigation. A good example is Stackoverflow.
- calvinbhai 8y agoI worked on an app for a few years (in the earlier part of this decade), and we redesigned the heck out of the app, moving from tabbar based design to hamburger menu. Literally everyone in the company were super happy about how the app looked. When we did UX testing with real users, and also some users who were given the scenarios, it became painfully obvious about how much of a cognitive load it was, for the users to understand what's hidden behind the hamburger menu. But we still continued with this design, because we (the organization as a while) didn't have the gumption to revert back to tabbar based design while HB menu was still the rage, and a year later Apple mentioned in one of the WWDC talks that Hamburger Menu is not cool. Recently, I quit an app company because (in addition to other reasons) they decided to move from tab to hamburger (and I had an another offer).
- contextfree 8y agoThe article is right that users overwhelmingly tend to prefer familiar navigation design, but elides the question of how new patterns come to be familiar and accepted in the first place. If everyone followed its advice there would be no advancement or broadening of the commonly accepted navigation language or culture.
- romwell 8y agoSome exceptions to the rule: Snapchat was made confusing on purpose[1], because its target demographics (teens) could adapt fast, but people used to more traditional UI schemes (their parents) had some friction using it. In that, just like Facebook's "college email only" lock-out at start, it was a feature, not a bug. [1]https://www.businessinsider.com/jeremy-liew-first-snapchat-investor-explains-why-the-app-is-confusing-to-use-2017-2 https://www.businessinsider.com/jeremy-liew-first-snapchat-i...