Hey all,
Has anyone here testing how users interact and react to priority+ navigations?
If so, what were the major issues with this pattern?
Scraped from the article: The priority navigation pattern by css tricks
Pros
- Relatively simple to implement – The logic required to execute this technique isn’t terribly complicated. It’s just a basic show/hide toggle to reveal the hidden navigation items.
- (hopefully) exposes the most accessed features – it’s hopefully revealing the three or four things the majority of users frequently access anyways.
Cons
- Hides potentially important nav items – what you may deem most important may not be what’s important to your users. Burying nav items means having to make some assumptions, and while it hopefully works out for most users, it might also piss some people off.
- Doesn’t work well with multi-level navigation – The priority+ pattern seems good for navs that have a lot of items at the same hierarchy level, but unfortunately it doesn’t seem to solve the sub-nav dilemma.
2 Likes
hi @lou_dufrane
a lot was already well explained by @jaisonjustus
From my side, I worked on a similar task in the e-commerce environment, what we found out from our tests, from UX/IX point of view (qualitative and quantitative), was:
- what is hidden/above the fold is rarely used by users
- the navigation pattern should be very straightforward to allow users to understand how to browse the navigation pattern
- always provide a plan B to browse the full menu (eg landing pages)
- if is possible make the navigation smart. According to our experience users were very happy to see that the system was able to re-arrange the menu according to the most clicked menu items
let us know what your design solution will be for such task 
You mean “below the fold” ?
yes, sure 