11. 1.Visibility of system status
2.Match between system and real world
3.User control and freedom
4.Consistency and standards
5.Error Prevention
6.Recognition rather than recall
7.Flexibility and efficiency of use
8.Aesthetic and minimal design
9.Help user recognize, diagnose, and
recover from errors
10.Help and documentation
12. VISIBILITY OF SYSTEM STATUS 1.
“I know what’s going on”
google drive
- loading percentage
- status bar
13. MATCH BETWEEN SYSTEM AND REAL WORLD 2.
It’s important for the application
to speak the user’s language base
14. USER CONTROL AND FREEDOM 3.
Giving the user the freedom to
navigate and perform actions.
The freedom to undo any
accidental actions
15. CONSISTENCY AND STANDARDS 4.
Button, icon, etc in one page should look
the same across the site on any page
Google Plus launched “+1” to counter
Facebook’s “Like” without much success.
Facebook’s “Like” already became a standard.
16. ERROR PREVENTION 5.
There are times when you wrong typing
then google gave correction for you
Try to validate it as the
user types rather than
waiting for him to click
submit.
17. RECOGNITION RATHER THAN RECALL 6.
It’s always better to suggest the user a set of options than to let him
remember and type the whole thing. The goal is to minimize the
application of user memory.
18. FLEXIBILITY AND EFFICIENT OF USE 7.
The Interface should be
flexible transforming itself
between a novice user and an
advanced user.
19. AESTHETIC AND MINIMAL DESIGN 8.
KISS!
“Keep It Simple Stupid”
Interfaces need to be cleared
of unnecessary elements and
content that do not support
the page goals and tasks
20. HELP USER RECOGNIZE, DIAGNOSE AND
RECOVER FROM ERRORS
9.
A check needs to be made if those errors are
being explained to the user in
understandable language
21. HELP AND DOCUMENTATION 10.
If there is any user who could not make it out,
adequate help should be provided within the
product.
22. Use this guidelines as general rules if you want
to make better UX for user. Mostly be
applicable to any web and mobile application.