System Feedback
Success Messages | Error Messages | Help
Success Messages
If the system has executed a function the user should receives a confirmation message on the activity. For WAP applications such a success message is very important to give the user the control of what is going on. This is because there is only a limited possibility of online help available and also the user probably wants to stay online only as long as needed for completing the task.
|
Good: |
New order with no. 1234 was created |
|
|---|---|---|
|
Bad: |
New record was created |
Error Messages
- Avoid error messages if other ways on feedback are possible. The user should experience error messages only if it is strictly necessary.
- An error message should help users to overcome problem situations and to continue their work. Typically error handling is done by sending error messages that note the error, explain the reason for the error and - ideally - provide hints how to remedy the error situation.
Error Prevention Comes First!
Before handling errors, you should first ask how errors can be prevented.
WAP applications have little space for error messages, especially for messages that explain causes or provide hints for error recovery. This problem is counterbalanced by the fact that WAP applications typically have little functionality and that thus errors are less probable. However, this is not a satisfying answer to the problem of error handling. Therefore, the route to go is: Design WAP Applications so that errors cannot occur!
Help
Explaining Texts
Typically WAP applications should not have explaining texts on the screen. There may be exceptions, where special fields or status displays, alert or error indicators need explanation, but normally a WAP application should be self-explaining.
Field Help
There is no field help in WAP applications!
Value Help
Value help can also be provided by using dropdown listboxes instead of input/output fields, provided the number of possible values is small enough (typically less than 20 items).
