Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
In which you are read that how to make design in android application
Typology: Study Guides, Projects, Research
1 / 14
This page cannot be seen from the preview
Don't miss anything!
10 USABILITY HEURISTICS FOR USER
INTERFACE DESIGN
"The 10 most general principles for interaction design. They are called 'heuristics' because they are more in the nature of rules of thumb than specific usability guidelines."
These are one of the most used heuristics for User Interface Design. They were developed by Jakob Nielsen together with Rolf Molich in the early 90's. The final set, which you see here, was released by Nielsen in 1994.
“What is going on?” – The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
When you do some action or referring to a continuing process the status should be clearly mentioned until its completion. Let’s look in to some examples.
When you login to the Gmail it shows you what’s happening in the background and the progress.
When you check flight details on Google it clearly shows you the status in a appealing way. Color represents that it’s on time and the location of the icon shows the progress of the journey.
“What are you talking about?” – The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
Basically it’s making the designs, interactions labeling and conversations more familiar to the real world.
iBooks application using the appearance of wooden bookshelf.
Recycle bin icon is similar to a real bin, and icon itself shows weather it has files in it or not.
When you trigger an action accidentally, and you want to get out of there without going through any of the details, small cross is there to rescue you.
If you do a simple mistake you can always undo and recover from it, and if you want to go deeper Medium has revision history that you can restore to a previous state.
“Oh, I know that!” – Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
You will always find sign-in, profile details and shopping cart information at the top right corner.
Microsof t Word, Excel, and PowerPo int all use the same style toolbar with the same primary menu options: Home, Insert, Page Layout… Consistency results in efficiency and perceived intuitiveness
“Glad I didn’t do that!” – Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
When a user returns to a eCommerce site like Aamazon and Ebay, the personalized home page includes a list of recently viewed items, suggestions by your browsing history and recommendations through your purchase history.
When you Google it gives you list suggestions as you type in based on your previous searches and related most searches. It also lists your matching bookmarks as well.
“It doesn’t matter if you’re an Expert or a Newbie” – Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
While novice user use the default Google Image search, expert user always can refine the search by size, color, type and so on.
“Wow… and WOAH!” – Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
When there is an error you should not panic user, you need to help them recover by suggesting a solution. This error message assures you are safe and suggest some alternative links.
This funny error message keeps the audience engaged, while relevant links keep you on your website.
“Now I get it!” – Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.
You can provide any extra information that would be useful to users, along with the label. But you should do so only if it is necessary.
WSO2 products quick start guide is a good example for documentation. It’s well organized, structured and contains the minimal information that requires to quickly install and use a product.
