Structure and grid

The layout and grid help the user understand the interface hierarchy. In addition to performing the structuring function, the layout also standardizes main product components and sets a unified visual rhythm.

The layout should be:

  • consistent across products,
  • predictable,
  • adaptive.

Relationships of elements and their characteristics

All elements of the system are built on the principle of minimal load of information, content, atoms, dots. The elements have length, width and height. These parameters can change - stretch and adapt - depending on the purpose of the UI element. Elements visually respond when interacted with.
For example: the user scrolls the page to the end with a sharp motion, the elements on the page stretch, following the user's action, thus simulating elasticity to indicate that the user has reached the end of the page. Elements are not clipped or reshaped (For example: from square to circle) and can only stretch, shrink and move.

Predictability

Information layers

Interface elements have different purposes or are located at different levels of the semantic hierarchy. Separate them into information layers.
Information layers are flat but have depth relative to each other. This helps quickly understand the hierarchy and function of interface elements.
Information layers are flat but have depth relative to each other. This helps quickly understand the hierarchy and function of interface elements.

Layout structure

Negative space. Use negative space in the grid as a visual hierarchy tool.
The interface is too clamped
Negative space helps to read information
Columns cling together, causing the layout hierarchy to collapse
The structure of the interface is well perceived due to negative space
Separators. We resort to using separators only when not having them impairs information readability and disrupts the visual hierarchy.
Separators make reading the list more difficult
The hierarchy of elements is maintained thanks to the negative space
Separators unnecessarily increase the height
The form is well structured
On a multi-column layout, separators are used only when cognitive load is significantly increased without them.
Separators aren't improving the interface navigation but only make it clamped
The structure of the interface is well perceived due to sufficient negative space
On lists, we use separators only for highly loaded elements.
SeparatorWithout separators, the list items fall apart, making scanning the email list more difficults aren't improving the interface navigation but only make it clamped
The structure of the interface is well perceived due to sufficient negative space

The principle of modularity

The entire design system is built on the modular principle. The main purpose of the modules is to create an integral chain of system elements and build a multi-level architecture. This principle is designed for infinite products' scalability, from the primary elements to secondary and so on.
For example: main modules of the site / application, which are to be displayed first in the chain of user interaction with the system. The first level modules nest the second level modules, and so on. This principle can be reflected both in the IA [information architecture] (the main page containing blocks (modules) of secondary pages, etc.) and in the visual display of UI elements (content card, title, image and CTA button).

Spaces

Use white space abundantly. Use white space to improve the user perception of content and UI elements. There should be more negative space than positive.
Don’t
Do
Use the pre-defined indentation system for the integrity of the design system and a consistent user experience. The indentation system reflects the basic principle of the system design - a dot (4-5px depending on the platform) is the minimum unit for building all elements and indents.
Use the principle of 'proximity' to indicate relationships between elements. It is used to ensure proper joint placement of related design elements. It is necessary so as to convey to the user the relationship of elements with each other and accelerate the understanding of the interface during scanning a website or application.
Don’t
Do
Clarity and usability should be achieved by maximizing the signal and minimizing noise, ensuring a high signal-to-noise ratio. In order to achieve this, one needs to make sure that relevant information (signal) is presented efficiently while irrelevant information (noise) is reduced or completely removed.
Don’t
Do

Adaptability

Depending on the type of product, we use variable approaches to adaptability. In one case, it will make more sense to rearrange interface elements. In another, it will be easier to create adaptive interface variations (for example, a header turns into a burger menu on tablet and mobile). A combination of the two adaptation methods helps to achieve the most user-friendly interface.
Use the auto layout and resizing functions to optimize the adaptation of UI elements on tablet and mobile versions.
Adaptation for tablets and phones should be done by compressing content into container sizes, without changing component styles, font, etc. Changing inter-screen indentation and indentation between UI elements is possible, provided the proximity principle. Rearrangement and changing of elements without compromising the styles and design of tokens are also acceptable.

Breakpoints

Combined breakpoints are used for adaptation work, depending on the tasks of the interface. Users should always have enough comfort reading the interface and content.
The main breakpoints of adaptability
Desktop
1920px
Laptop
1440px
Tablet
768px
Mobile
320px - 414px
Android
360px
IOS
375px
IPad OS
768px - 1024px