User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
With more and more people using mobile devices (or devices which doesn't have right click gesture), its getting tough to indicate that there is an activity that involves right click on desktop devices, especially for those applications which became popular on mobile devices or people started using them on mobile devices first like facebook or gmail.
Do you think right click is still an important gesture to hold on too, or should it be completely ignored while doing website design?
I have rather strong views on this subject so please take my opinions with whatever serving of salt you like.
That said, I love right click in the browser. When I am on the desktop and working within a web application (Google Dive for example) I often find myself right clicking and seeking to perform an action. And often times - especially when operating within a web app - I am disappointed to find limited or no functionality nestled away in that menu.
That said, I don't believe you should ever have to right click in a web browser for any reason. And for our touch only friends this can be especially frustrating.
So, my approach when designing web applications where I could see benefit of adding a right click context menu to some portions of the app is to first design the interactions so that they can be accomplished with no right clicking whatsoever. Once that is done, if I do believe that some significant portion of users will find benefit from a right click context menu and there is enough time and resources to properly implement the menu, I say go for it!
I hold this same view on keyboard shortcuts. A lot of users don't know about them or care to use them, but for some certain power users they sure make life easier and work quicker.
Firstly, right click isn't a consideration in website design, but may be in desktop software.
Try to design your software to not need a right click in the first place. It will be more discoverable, and will translate to mobile well. I have seen some applications use a long press as the equivalent of a right click, but I wouldn't recommend this as you would be breaking the generally accepted use of long press. The Android design guide recommends long press as:
It's possible that in the future the right click will go the way of the Dodo, but a lot here depends on your intentions and your user demographic.
If your intention is to be strictly cutting edge and your user demographic is very familiar with gestures (and perhaps Mac users?), then by all means avoid it. If your intention is to hang on to conventions that most users will recognize and your users are a broader range of people including older people who may not be up to date on gestures, then my advice is to continue using a right click.
It should be noted that intention is the most critical aspect of great web design.
This article will give you great insight: http://sachagreif.com/the-flat-sink/
yes I Back,JohnGB. Right click is not recommended for websites. If you are using it, please be cautious about the findability score of that feature. Again Mouse Hover is also auto-of scope for touch devices.
So Try to be selective, minimilistic about features and pitch on the most commonly used interactions.
I don't think that there is a generic answer to this. You need to determine if your users expect there a contextual menu.
If your users (or some important subset of your users) expect that there should be a contextual menu, and have expectations about what that contextual menu should contain, then you probably need a contextual menu. If you increase the time that it takes for a user to complete their goal, or if you block them from completing a goal, then you are negatively impacting their user experience. There are many workflows on a website that could benefit from quick access via a contextual menu instead of having to look elsewhere to find the same functionality.
That said, I strongly agree with the Apple Human Interface Guidelines, which says this:
Avoid providing access to features only in toolbars or contextual menus. Because toolbars and contextual menus may be hidden, the commands they contain should always be available in menu bar menus as well. Presuming that your website won't have its own menu bar, but the point remains the same: a contextual menu should never be the only way that a feature can be accessed. There should always be another entry point.
For the purposes of this answer, I'm not drawing a distinction between a website (ex: http://google.com/) and a web application (ex: http://mail.google.com/). The line between these two is thin and getting thinner with each passing day, as it becomes easier to create very rich web experiences.
I don't know that right-click is going to ever disappear completely because it is such a well used and loved tool for desktop design. I have seen many a user trying to use right click in user tests as well.
A great way I and other designers have found to avoid using right click in web based design is by giving a settings or tools button in the upper right hand corner of whatever card or div the user wants to take action on. By giving them a button to open up the context menu you avoid the discoverability issues that come with invisible right clicks, while still giving the user those nifty contextual tools in a semi familiar way.
Example:
