ADITO Design Principles
These principles can support decisions when a customization changes a screen, navigation, or an action. They are a practical starting point for a design discussion; the individual viewtemplate reference remains authoritative for its configuration and behavior.
Principles
- The user's task is the starting point. A screen rarely needs to show every field or relationship of an entity; it needs to show what helps users complete the current task. See Information, navigation, and labels.
- A viewtemplate works best within its documented purpose and configuration. See Visual design and data presentation.
- Names, groups, and icons can make the current area of work clear. They help users recognise where they are and what an action will do. Spelling and wording provides the conventions.
- Actions are most useful when they support the task. See Actions and interaction.
- The central theme and visual highlighting help focus attention on information that needs attention. See Visual design and data presentation.
- Considering device variants and accessibility during design, rather than only before release. See Devices and accessibility.
Consistency across comparable contexts
When the same business concept or user task appears in more than one context, familiar patterns make it easier to move between them. Equivalent fields, actions, and tabs benefit from a consistent label, presentation, and relative position.
Consistency does not mean that screens need to be identical. A different task, role, device, or available information may call for a different arrangement. The familiar parts can still remain recognisable in those situations.
The topic-specific guidance explains how to apply this principle to information and navigation, standard view patterns, forms, actions, and data presentation.