Skip to main content

Standard View Patterns

Standard views give users a familiar way to interact with data. These patterns describe the user experience of common views. The viewtemplates and layouts reference defines the supported components and configuration.

Filter views​

A filter view helps users find, compare, and select records. Filter criteria are most useful when they narrow the records for a real task. The first representation should be the one that best supports that task, rather than a fixed default for every kind of data.

A timeline is often helpful for chronologically ordered content, such as comments, posts, or events. A table suits tasks that involve scanning, sorting, or comparing several records and their values. A treetable is useful when a hierarchy or grouping helps users understand the records. Further representations, such as charts, can complement the primary view when they add a meaningful perspective.

The labels of alternative representations help users understand their purpose before choosing one. Their order can reflect how frequently each perspective is needed, with the most suitable representation appearing first.

Frequent, task-critical actions benefit from a prominent position. Less common actions can remain available without competing with the next likely step. The Actions and interaction guideline explains how to make this choice consistently.

Preview views​

A preview view provides focused detail for a selected record. It can give users enough context to check the record or start a common action without interrupting their work with the current set of records.

A prominent primary identifier supports orientation. Supporting information is valuable when it helps distinguish the record, explain its current state, or inform the next step. Common first actions can be available from the preview when they shorten the usual workflow.

Concise headings make related details easier to scan. Groups with one clear subject tend to be easier to understand than mixed collections of values. Key figures are useful when they support a decision. Information needed for more extensive work can remain available in the full record.

A main view supports more extensive work on a record. Its overview provides a stable point of reference while related information is available in the detail areas. Because users can arrive at a main view directly, the overview and preview can usefully share the information needed to identify and understand the record.

The appropriate amount of overlap depends on the context. For example, the full text of a post can be important while it is being previewed, whereas the main view overview may only need to identify the post when the first detail area already contains the full text. Repeated information is only useful when it provides context at the point where users need it.

The relevance to the selected record and the user's task usually provides a helpful order for detail areas. When the same area appears in comparable contexts, a familiar label and relative position make it easier to find. A different role or task may justify a different arrangement.

For data entry, use Forms and validation. For links to related records or contexts, use Contexts.