Design System: Rules and Tools for Faster, Higher-Quality Development

Lecture 7 min.



A design system is a set of components, rules, guidelines and tools for improving the quality and speed of product development, as well as for the effective maintenance of existing products. In English, the term "design language" is most often used for design systems, and it also defines the main difference from a design system: a design language can be used outside the sphere of digital products. One example of such a "visual language" is the recognizable styling of BMW cars (the headlights, the radiator grille). A visual language defines the basic foundations for creating products and solutions.

Today specialists identify the following main components of a design system:

  • Guidelines and a style guide
  • Frameworks
  • UI kits, templates
  • Sets of UX patterns
  • Libraries of ready-made components
  • Documentation, rules, recommendations

Probably the best-known example is Google's Material Design system, on which many Android applications are built.

Design System: Rules and Tools for Faster, Higher-Quality Development

A design system usually includes several large sections. The set of sections may vary depending on the company and the number of products it has. The larger the company, the more complete and carefully thought-out a design system it needs. Here is what they may include:

Goals of a design system

The systematization of design aims to arrive, through the creation of interrelated basic elements, at a single field of interconnected products and solutions. In other words, design systems help create a convenient ecosystem of products that is understandable to developers and users.

The difference between a library of ready-made elements and a design system is fundamentally important: the latter is distinguished by an exceptionally detailed elaboration of all the nuances. A striking example of a large, well-thought-out design system is IBM's Design Language , which describes all possible ways of developing its concept in digital products and presents the philosophy of the system to the community. IBM records the special role of the design system in the structure of the relationships "user–product", "client–company", "developer–product" and "employee–company".

Using design systems provides a number of definite advantages:

  • Standardization of solutions
  • Independence of projects from the composition of the team
  • Easier handoff of a product between the stages "research – design – development"
  • Lower costs of supporting, developing and launching products
  • A design system saves time and resources on developing, testing or updating components. But, like any tool, a design system itself requires maintenance and updates, which will consume the teams' resources. This should be taken into account when assessing the financial benefit and risks.
  • Systematization of knowledge solves problems with the help of a ready-made library of elements and components. The ability to scale and improve standard solutions has a positive effect on the company's profit.
  • A design system makes it possible to obtain a cohesive interface and bring a brand's products to a single visual language. This helps the company increase recognition and loyalty among customers.
  • A design system is intended not only for big business; small teams can use it too.

Origins of design systems

The foundations of design standardization began to appear with the development of the "Swiss style", which took shape in 1927 thanks to Jan Tschichold . Tschichold introduced not only the key concepts of simplicity, conciseness and ease of perception, but also clearly outlined the limits of acceptable use of individual elements in graphic design. The designer is also credited with introducing the modular grid, a system actively used in web development, printing and the creation of design system elements.

The first approaches to creating design systems appeared in the 1960s, when the modular approach began to be applied in programming. The idea of modularity had been developing since the late 1950s and gradually went beyond the sphere of programming, covering adjacent fields.

Another important factor was the rapid development of graphic design and the demand for establishing stable principles of corporate identity. The manual for the New York City subway is often cited as an example; it describes in detail the use of all navigation elements, typography, symbols and graphic elements.

The idea of creating something new on the basis of developments in the art world was promoted by Karl Gerstner and Sol LeWitt. The concept of creating art by means of algorithms occupied a central place in the work of serial artists. Sol LeWitt was probably the best-known serial artist. For LeWitt himself, the true work of art was the algorithm, not the final product. In the modern sense, he was one of those designers who experiment with design systems.

Design systems today

The explosive growth of technical solutions and the appearance of new programming languages, libraries and frameworks required large companies to standardize their approaches to development. From that moment, design systems became an integral part of large projects, serving as the basis of the process of developing and scaling digital products.

At the moment there are several hundred large design systems in the world. The leaders in creating and developing the field are large IT companies (Apple, Microsoft, Google), banks and financial organizations (Tinkoff Bank, Alfa Bank, Sparebank 1, VISA), software producers (Atlassian, Mozilla, IBM), design studios (Chulakov, AIC), and FMCG manufacturers (Royal Canin).

The Atomic Design methodology

The creation of design systems is often associated with Brad Frost's "atomic design" methodology . Atomic design, used mainly for web design, has 5 levels of development:

  • Atoms – HTML tags
  • Molecules – simple elements connected to each other (a feedback form made of a button and an input field)
  • Organisms – separate sections of an interface (a menu, a navigation section)
  • Templates – standard solutions for pages (a product card)
  • Pages – templates that use real content

Following the methodology level by level brings clarity to the process of assembling both individual parts of a product and the solution as a whole. For creating design systems using the atomic design method, enthusiasts built a tool called Pattern Lab.

Tools for developing design systems

Specialists developing complex design systems are helped by applications such as Sketch, Framer and Figma. Various frameworks, SDKs and libraries (AngularJS, Flutter, React) also play a large role.

Government design systems

The development of government design systems can be seen as a logical continuation of the digitalization of the "citizen – state" relationship. Today Italy , Australia , the United Kingdom , Singapore , the USA and Estonia[10] have their own design systems for developing services and products.

The Russian government design system is being developed on the commission of the Ministry of Digital Development, Communications and Mass Media, but it has no officially confirmed final version of the visual and graphic design or of the rules for using the fonts and elements of the system.

Creating design systems with Atomic Design

Atomic design is a design methodology in which you describe a design at five levels of components:

  • Atoms (a button, an icon, an input field, a line of text)
  • Molecules (a button with an icon, a search field, a notification banner)
  • Organisms (a site header, a login form, a content card)
  • Page templates (pages without content)
  • Pages (templates filled with real content)

Interesting facts

Many design systems receive their own names, which reflect the essence of their philosophy and visual language:

  • Bootstrap – Twitter's framework and design system
  • Carbon – IBM's design system
  • Consta – Gazprom Neft's design system
  • Fluent – Microsoft's design system
  • Gel – the BBC's design system
  • Lightning – Salesforce's design system
  • Material – Google's design system
  • Nachos – Trello's design system
  • Paradigm – Mail.ru's design system
  • Photon – Firefox's design system
  • Polaris – Shopify's design system
  • Ratio – Rambler's design system
  • Solid – BuzzFeed's design system

Comments

To leave a comment

If you have any suggestion, idea, thanks or comment, feel free to write. We really value feedback and are glad to hear your opinion.
To reply

Lectures and tutorial on "design software UI and Web design"

Terms: design software UI and Web design