The Structure Principle
Design ought to sort out the UI deliberately, in important and helpful ways dependent on clear, predictable models that are evident and conspicuous to clients, assembling related things and isolating inconsequential things, separating different things and influencing comparative things to look like each other. The structure guideline is worried about generally speaking UI engineering.
The Simplicity Principle
The design should make straightforward, regular errands simple, conveying unmistakably and essentially in the client’s own language, and giving great alternate routes that are genuinely identified with longer techniques.
The Visibility Principle
The design should make every single required choice and materials for a given assignment obvious without diverting the client with superfluous or excess data. Great designs don’t overpower clients with choices or mistake them for superfluous data.
The Feedback Principle
The design should keep clients educated regarding activities or understandings, changes of state or condition, and blunders or special cases that are important and important to the client through clear, brief, and unambiguous language well-known to clients.
The Tolerance Principle
The design ought to be adaptive and tolerant, diminishing the expense of mix-ups and abuse by permitting fixing and re-trying, while likewise counteracting mistakes wherever conceivable by enduring shifted information sources and arrangements and by deciphering every single sensible activity.
The Reuse Principle
The design ought to reuse inner and outside segments and practices, keeping up consistency with reason instead of just subjective consistency, in this way diminishing the requirement for clients to reevaluate and recall when it comes to app development.