Here we highlight some of the key benefits that make the system important
Consistency – thanks to Design System developers are able to implement consistent UI much easier. They can think of the particular page as of the set of components. Example: Developer does not have to think that this is a button with #0302fa background, 14pt Open Sans Bold font, and 8px padding. The engineer knows that this is just a Primary Button, and he is using this component in multiple pages.
Higher quality – consistency makes the impression of higher quality. QA Specialists will easily monitor the implemented design with Design System documentation. Inconsistency should appear rarely.
Better Communication with Development Team – Design System is the single source of truth – this means it also contains vocabulary that may be used in the project. When the developer and designer discuss the page, they will use the same names of the components. Thanks to this you will not talk about “this small purple button,” but the “Secondary one.” Many mistakes where done because misunderstanding, Design System allows you to speak in the same naming convention.
Faster Design Process – You have already built or purchased the Library of UI controls needed to implement UI. Now you just use them when the new feature requires to create a new page or modify the existing one. Even if you decided to build the UI Library from scratch – these tons of hours spent on that task would allow you to create UI for new features quickly.
Focus more on UX, less on visuals – Using UI Library means you do not have to figure out every time what should be the appearance of the input field on this page – it is already defined. The visuals are previously described in the system – now you can compose new pages with them and focus more on better usability and delightful experiences.