A friend may be confused, a friend may not understand the program. A friend is not a programmer, not a developer, he has not worked for long hours on the program and therefore does not know all the nuances of the program (Sometimes the developers do not know all the nuances of their program). At the initial stage of working with the application, a friend does not know how to use the application. Only with the accumulation of experience with the application, the user increases his level of proficiency in the application.
Let a friend be confident in working with your application, be confident
The friend may be confused about what is currently happening in the program. This creates uncertainty for the friend in the course of his work. Make information about the state of the program obvious to a friend, not a programmer. This will give you confidence in what the app is doing right now and thus allow you to be confident in your actions with the app for your friend. Sure.
Create a scenario of logical and obvious communication between a friend and your application
A friend takes an action and the application responds to the action. Provide feedback on a friend's actions with your app. Did the action really take place or did some errors occur, did the friend get the expected result or only part of the result and other actions are required from the other? What actions? Does the friend know about these actions? Has your friend forgotten about these actions?
A friend may be nervous, in a hurry, or simply this information “dropped out” for a moment and was not remembered by a friend at the moment.
Does the application give consistent messages so that a friend is guided not only by the nature of the feedback, but also by the external characteristics of the feedback, and can understand a lot by external attributes? Do the characteristics of a friend's feedback confuse over time, in different fragments of the application, with different actions?
A friend can quickly look at the message, at the interface, be inattentive, be absent-minded.
, , , ? , ?
. , . , , .
, , , - « »?
?
, . , , , . , , , .
, , , . . .
, . , .
.
? ? ? ? DNS ?
, , , , . .
, , . , . , , . .
, , ? ( .)
, , . ?
, , , , , ( ).
? ? ? ?
, – . .
, , .
. . . . . .
« ». - . , . , , , - , .
, ?
« ». , . .
, « ». , . -, , .
, , , ? , , ?
. . , .
.
, , , . , .
, , . , , .
. . , , , . , , . , .
, «» «», , , , , . , .. .
. .
.
, . , , , , .
, , , , ?
, .
, , . , .
, , , . .
, , , .
Let your friend know you made a mistake and figure out how to recover from a mistake
A friend has the right to make mistakes. The programmer can tell you when a friend might make a mistake and how best to recover from the mistake.
Let a friend explore the app in different ways. Let's even read the documentation
A good application requires no documentation, but a friend might want to know how to achieve their goals in your application.
PS As you understood, these are the classic 10 heuristics of Jacob Nielsen . Only from a slightly different angle. Thanks to those who read.