Web applications: Lack of context

Unlike Macintosh and Windows programs, a Web application does not bring up a dialog box to ask questions or get information to complete a subtask. On the other platforms, the main window remains visible behind a dialog box and provides context. This model allows users to remember how this subtask fits into their work. Web applications need to find a way to display information in context rather than requiring users to remember it.

A simple technique for Web designers is to redisplay the page that caused an error along with the error message, instead of displaying the message on a page by itself. Even though they are looking at a new Web page, users perceive it as the same one. They do not have to go back and forth between pages to interpret the error message.

Illustration of error-message in context
An error message shown in context rather than on a separate page

Show new information in context rather than in isolation, so users have less to remember and do not need to return to a previous page. This requirement is no different on the Web than on other platforms, but it can cause more problems on the Web because of the time it takes to go back to the original page and figure out the context.

Navigation in Web applications

1. Introduction
2. Basic navigation
3. Losing users and losing work
4. Separating the browser and the application
5. Lack of context
6. Delays caused by network connections
7. Conclusion

Download the full article (PDF, 52KB)