Jakub's Nielsons Heuristics

Visibility of system status

Designs should keep users informed about what is going on through appropriate timely feedback

Match between sytem and the real world

The design should speak the users language use words, phrases and concepts familiar to the user

User control and freedom

Users often perform actions by mistake. They need a clearly marked emergency exit to leave the unwanted action

Consistency aand standards

Users should not have to wonder whether different words, situation, or actions mean the same things. Follow platform conventions

Error Prevention

Good error message are important, but the best designs carefully prevent problems from occuring in the first place

Recognition rather than recall

Minimise the user’s message load by making elements, actions and options visible. Avoid making users remember information

Flexibility and efficiency of use

shortcut - hidden from novice users - may speed up the interaction for the expert users

Aesthetics and minimal design

interfaces should not contain information which is irrelevant. every extra unit of info in an interface competes with the relevant units of information

Recognise, Diagose and Recover from error

Error message should be expressed is plain language precisely indicate the problem and constructively suggest a solution

Help and Documentation

It’s best if the design doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users complete their tasks