-
Notifications
You must be signed in to change notification settings - Fork 7
Description
One of @jkicillof's latest designs (https://projects.invisionapp.com/d/main#/console/4103589/465275288/comments) shows a main navigation menu with very few elements.
This is actually independent from the discussions about the transfer workflow and scanner interaction, so it makes sense to discuss this separately.
I like it. I've been annoyed by the navigation menu being so big and hard to actually navigate.
After some time you're used to remember where the items are that you typically use.
But for new users it's overwhelming. And it's not great for experienced users either.
Joni's approach is to have a nested menu for samples and related things (batches, transfers).
It moves elements that are not relevant in the current context, out of sight. That makes them harder to reach, but you
typically don't need to reach them anyway from the sample page.
I had been thinking about another idea, though. The pages in the main navigation menu have very different usage characteristics.
For example, if you're working with samples, you'll spent most of the time on the samples page (and related).
In contrast, configuring a site or device is pretty rare. Many users may never have to go there after initial setup.
There is a clear difference in the frequency of these pages. Navigation should make frequently used things easily accessible,
and rarely used things can be further away.
I think the split goes right in the middle, where the first half are frequently used pages and the last half are rarely used.
Of course, this also depends on the kind of work you do. IIRC, UCSD has no patient interaction, so they probably don't use the patients page at all 1.
In any case, I believe the last half of pages (sites, devices, logs, users, settings) are probably not frequently used.
They don't need to be easily reachable there when they're only used sporadically.
They are actually all kinds of settings. So I'd suggest to move them away from the main navigation menu and summarize all of them on the Settings page.
The link to that page could also be separated from the main entries, and moved to the right, next to the account menu.
It could also become a cog icon instead of a text label.
Then in the top right corner you have two menu items, one for account configuration and the other for context configuration. That fits together very nicely.
As a result, we get a clean, small main navigation menu with all the important links easily accessible and less useful clutter tucked away, but still reachable.
Footnotes
-
A further improvement could be to add configuration for hiding pages when they're not used.
If an institution like UCSD doesn't use patients data, they could easily hide that button from the nav. They don't need to go there anyways. ↩