Filter
Top Products
operation. For this a softkey labeled, for example,
“Cancel’ is provided.
Figure 5-41. A wait note with a Cancel function in the right softkey.
Some guidelines concerning note usage:
Use a confirmation note when:
The effect of the operation can't be seen directly by some other means.
Example: Message sent.
·
·
·
·
There is some relevant information to be communicated by it.
Example: Last call duration.
Confirmation notes should not be used after every completed operation, this would
easily start to annoy users. Confirmation notes should not be used when:
- There is already another dialogue in the procedure, for example "Do you want to
remove this message? Y/N"
- A progress indication is visible during the procedure.
- The user can see the result of the operation when it is done. Example: adding or
removing objects in a list.
- A setting has been changed. The new value of the setting is visible in the setting
item.
- The operation can be considered minor or so frequent that a note would be
annoying. Example: copy-paste actions.
Use an error note when:
The user does something that may cause considerable harm immediately or later.
Example: the user gave a wrong PIN code. Repeating this a couple of times
would block the SIM card.
To keep the error notes effective, they should be used very sparingly. In most
"ordinary" error cases, an information note should be used instead of an error note.
It has less aggressive sound and graphics.
It should also be noted that if the information to be given is such that the user
must see and acknowledge it, a confirmation query is a better component to
use than a note. Then the user must press a key to dismiss the information, and
there is time to read and think about the notification.
57