Users need to manage a collection of objects


Create an overview of objects that together is meaningful to users


Use when

Typically used in a Web-based Application in which 'Views' are the main elements. Users need to manage objects such as emails, bank accounts, stocks, orders and so on.


A view usually is an overview of a set of objects, e.g. email messages, orders, appointments, products, image, . When views are editable, they may take the form of a List Builder or a list of thumbnails or a custom-designed overview. Views usually contain 'abbreviated' description of the objects themselves. These descriptions are usually clickable which results in a detailed view of the object. Closing the detailed view takes users back to the view itself. Views are typically placed in the Center Stage of the page. When views are very large, some form of Paging or Stepping can be used. Switching from one view to another is done using the Main Navigation.

Typical behavior with forms consists of 'view-edit-return'. The user selects an item in the view and edits the detailed description using a Form and/or a Wizard. Once the editing is completed, the users is presented with the view again.


A view is sort of a 'safe place' from which all kinds of 'management' functionality can be used. It gives users the overview they need and it is obvious how users can access the management functionality.

More Examples

At can manage a collection of MMS-es. An overview is given from which users can 'copy', 'move', 'view', or 'delete' MMS-es.

plml logo


0 comments have been added to this pattern

Add a comment
Do you have something to add or say about this pattern? Perhaps some more examples of how this pattern is used in the wild? Add a comment to this pattern and I'll update the pattern when necessary. Please abstain from misuse. I reserve the right to delete or modify inappropriate postings.

Your Name


Enter the verification code you see in the image below