Putting navigation on the left is very orthodox and through repetition it has become enshrined in the cannon of UI dogma.
However that doesn't necessarily make it true.
Jared Spool wrote on this subject:
In my opinion, you shouldn’t care what I (or potentially most others on this list) like for navigation. I don’t even think you should care what your ...
He's correct. The reason is that typical western style of reading is from Left to Right. You can see point #2 at: http://sixrevisions.com/usabilityaccessibility/10-usability-tips-based-on-research-studies/
There are also a great number of additional points you might want to look at while there.
Saying 'a user will get used to it' is really a design excuse: people may not be willing to take the chance of just clicking on your icon to see what happens. Not used these apps, but Google Ventures uses a good technique where the labels for the icons are shown onMouseOver. I'd recommend that as a good way to teach people what your icons mean without the ...
I'd say go with the second example (arrow placement to the left of the text). Why's that? Well, take a look at for instance the Explorer of Windows and you'll notice the arrows being placed to the left, or e.g. in the Component inspector of Google Chrome. In other words, this is most likely where users expect the arrows to be placed (based on previous usage)....
It can be, if you answer yes to anyone of these questions:
Has your sidebar remained the exact same for the last 3 months?
Does your sidebar exhibit signs of “sidebar creep” ?
Was there a time when people clicked around in your sidebar, but now you’re thinking you might have dreamed it?
Do you have more than 4 affiliate buttons showing at one ...
In terms a reachability for large displays i agree on your concerns. I also appreciate luke w.'s design video sessions.
But here some things which you should consider:
Reading direction - Page Scanning
I guess i do not have to mention studies here, where it was proven that the point with most attraction/attention is the top left corner. So, if this ...
Learn, don’t justify
Here's your problem:
How can i justify my assumption
Don't justify it — test it. User experience is about discovering the answer, not enforcing it through academic stubbornness. What if the alternative performs better for some reason you didn't foresee. Users are a complex animal.
I suspect your resistance to change is ...
If you want to follow Apple's Human Interface Guidelines then you have to think of another pattern, because last year they announced that hamburger menus are not a welcomed sight in iOS applications:
And again, I’m not going to say that there’s no place for these controls categorically. I think there are some apps that could maybe use one. But I will say ...
If your intention is to reduce the reduced sidepanel real estate to zero, there's really very few options available in terms of design patterns. The question simply becomes 'where do you put the button'
For example, The Opera Desktop Browser has a button at the bottom left, in the status bar which toggles the visibility of the panel:
Other positions could ...
When user triggers an action, let it happen. Don't initiate another action simultaneously unless it behaves like toggle/switch.
Here user clicks on one of the categories (Material design, Motion, ...). It leads to the sense that user wants to explore more about that category. It does NOT mean that he/she wants to close currently opened ...
There are different design patterns depending on what kind of content we are talking about. Looking at the article Placing Sidebars: Do You Lean to the Right or the Left? one can read the following:
To most people, where the sidebar navigation is on a website seem like
something pretty insignificant. Chances are if you’re an average
website user, it’s ...
Is using a cascading design a good approach, given that the level
wouldn't be more than 3? What I mean is that, when a user hover over a
parent item, it would list the next children items and so on. Pretty
much like a drop-down navigation menu.
Why not a file browser approach:
breadcrumbs to let you see where you're at
current "folder" view
Complexity is a relative term. It depends on the context of the user and the tasks they are trying to complete using your interface.
For example, the instrument panel of a Cessna 182 will look very complex to a non-pilot:
Similarly, the instrument panel of a Boeing 787 will look very complex to a private pilot that has only ever flown a 182:
The question ...
Sidebars are considered "reserved spaces" for good reason. If you want a user to find a button / menu item quickly then the best place to put it is on one of the edges (this can be top, bottom, left, or right). This is because targets that are easiest to reach quickly with a mouse are the corners and edges of a screen / window.
If you don't have enough ...
On Android this is also very common pattern but with few differences.
On Android you position this tabs on top of the screen (mainly
because of hardware buttons on the bottom of the phone)
You can use scrollable or fixed tabs (for more info: http://developer.android.com/design/building-blocks/tabs.html)
Using the hamburger icon for lower navigation components it's not a good idea since most people already associate it with high level navigation. You could try using a different icon for the lower level navigation components like Wikipedia does:
Additional suggestion : Placing a "Menu" label next to the hamburger icon improves its recognition ...
Most users are used to the logo as a link to home, so I would recommend that you don't shake that expectation up needlessly, ...
That depends on how much you want to emphasise it. A background colour is definitely more noticeable than a coloured link, but it is also more distracting.
You need to decide what the best balance is for your application as one is not always better than the other.
The first screenshot shows navigational items, and is placed to the left because of English reading order, left-to-right (LTR). This means that items to the left are higher up in the hierarchy than items to the right. Works perfectly.
The second sceenshot shows option menu (not for navigation) to the right of the main item. These options are attributes of ...
Two columns of the same width visually indicate to the user that each column is equally important. Information displayed in either column would thus hold the same amount of value to the user.
If you have made to columns of equal width but the information your are displaying in each is not equal in value then it can lead to user's feeling some sort of '...
If you happen to be filling the form below the scroll fold and add a top section you'll not only have the same problem of not seeing the section appear right in front of you but also experience your current view being pushed down by the new content which very is annoying.
I'd suggest going with an accordion of collapsible sections like below:
download bmml ...
Before I address your actual question, I have to point out..
I have seen this layout many times and it always annoys me - the problems I see with that layout are:
Global menu takes you out of current site, yet appears to be a part of the site
Site menu is in a different region of screen, making it confusing - which menu are you supposed to look at?
2nd one is better, fast glance and the user will know where they are and how deep they are on the website. take a look at what Google is saying about this kind of navigation.
I wouldn't make the text much smaller, because that would make it hard to read. but indenting sub categories is a common practice. Think about Windows Explorer view
download bmml ...