The concept of Design Systems consists of achieving application designs which are consistent, maintain the same style, and reuse the same aesthetics.
It also proposes to be able to systematize and reuse components to avoid redesigning them repeatedly.
At the same time, it integrates and speeds up the interaction between designers and developers.
A Design System is a group of:
- Principles (that define what good design is in your industry. Such as, for example, one that is mostly clear above all other aspects, followed by efficiency, consistency, and appearance in the last place).
- Patterns (such as typography, the colors to be used for different parts, and so on) and functional patterns (like the division into components that may be assembled as puzzles to make up the screens and thus convey the idea of an organic app).
- Practices (like the tools with which you develop/design, and how you do it, among other things).
This set of principles, patterns, and practices are oriented at building a digital product that is coherent, uniform and robust.
Design systems are not universal. Even when they share consensuses, they are defined for each digital product or family of digital products, and they also depend on the tools you have available at a given time within the software industry.
By just observing the apps you use on a daily basis (for example, email apps, messaging apps or social network apps) you can identify some of their aspects that make it easy for you to intuitively interact with them, since their viewing and their type of interaction are the same, regardless of platforms and screen sizes, allowing you to recognize them with a naked eye.
Definitely, you want to seduce users and make them love your app, so you have a growing need for defining Design systems.
- Start with its purpose.
- Specify who the audience is.
- Find Themes and share them with the team.
- Test and evolve the principles.
Design Systems Introduction
GeneXus default Design System