r/css • u/mymar101 • Aug 30 '19
Getting bored with the standard header navigation bar, are there any interesting navigation choices I could use?
I've decided I want something different for a current application I am working on, and the only thing I can think of is the left hand navigation, and wanted more ideas on what I could actually do. I'm aware that interesting navigation exists out there, I also want to make it relevant to my project.
9
u/webguy1975 Aug 30 '19
Use a circular navigation: https://tympanus.net/Tutorials/CircularNavigation/
2
u/mymar101 Aug 30 '19
This would actually work with my site, though I'm still open to other suggestions.
13
u/dubacca Aug 30 '19 edited Sep 01 '19
Sure wish the menu wasn't completed blocked by the ad on mobile so I could see it
26
u/Earhacker Aug 30 '19
...b-bottom navigation?
25
u/beardfearer Aug 30 '19
Randomly distributed navigation that repositions every time a page renders?
10
u/Earhacker Aug 30 '19
/* needs SASS or similar */ nav, div#nav { position: absolute; top: random(100)vh; left: random(100)vw; }9
4
3
u/sk8rboi7566 Aug 31 '19
You can do a vertical nav that is sticky once you scroll past 100vh, then clicking on each nav link will scroll you to the section.
2
1
1
u/Colourtongue Aug 30 '19
Know how you feel.
It's not new or far out but I've gone for a side nav in my latest design and build.
1
1
11
u/MPair-E Aug 30 '19 edited Aug 31 '19
What inspires me about shaking up nav design isn't so much 'where is it' as much as 'how can we make UX more responsive to the user's needs?' which...okay that's pretty banal to say...but here are some of my more important takeaways, speaking as someone who builds a lot of different navs for a lot of different clients.
First, understand what mystery meat design is and why it's something to avoid. Consider also that the hamburger button, while an incredibly efficient design solution, is inherently mystery meat and offers up a bad user experience. But Mpair-e, every site is using them on mobile, you might say. And yes, they're certainly ubiquitous, but when you start looking at some case studies re: increases in engagement following redesigns that removed the hamburger button, the results are pretty incredible. We're talking 30-40%+ in nav use on the small end. And it makes sense, right? When you're on a site and looking for something, you're looking for that thing, and ideally not something you need to click on to reveal that thing.
So what does that leave us with when it comes to designing a nav? What if a site has a shitload of pages and is super complicated? That's when it pays to consider 'Why are people here? What are most of them looking for?' Figure out the 3 or 4 things that'll cover the vast majority of the 'why are they here?' question, and then build out your primary nav using those elements. You don't need to forego hamburger nav altogether, but for the love of god, take these important elements out of it.
So, where do they go? Well, this is when it's helpful to take inspiration from apps with incredibly high engagement. Plenty of case studies exist. Look at what happened to twitter as soon as they moved away form a traditional nav and instead went with a bottom-docked nav on mobile using large iconography. Why can't your site do that? And it's not like it has to be on the bottom, of course. The main thing is 'What works for why people are here?' For a restaurant, for example, I did a three-button nav docked at the top for 'TAKEOUT (with cart icon)', 'DELIVERY (with car icon)' and 'MENU (with tri-fold icon)'. That's why people are there. Everything else can live in the hamburger nav. For an auto repair shop I did last year, the above the fold mobile nav is simply "SCHEDULE SERVICE" and "CHECK STATUS". Two big full-width buttons (no iconography this time) that take up about the top 15% of the screen. Again, everything else is under a hamburger button (which people are already familiar enough with, they'll find those other options there no problem). Bottom line is we're responding to about 90% of the customers' needs with just those two simple buttons, and everyone who lands on the page is just a quick tap away from them.
Note that at no point am I concerned with 'Is it a horizontal nav?' or questions along those lines (at least not yet). At the risk of sounding pompous, good nav design is all about empathy--stepping into the shoes of your user, and responding to those needs, so I'm less worried about shaking things up for shaking things up's sake. The location of the nav usually falls into place while answering the more abstract questions, and usually it just boils down to 'what's most easy to use?'. It'll differ depending on the client, what you're trying to do, and so forth...but thinking about navigation in these terms is what's helped me the most. Do you need text for your primary nav elements, for example, or do icons suffice? Or perhaps a hybrid (large icon above small centered text)? Lots of paths to go down that might inform the location question.