Design System vs Component Library
A component library is the set of ready parts, like buttons and cards. A design system holds that library and more. It adds the tokens, the rules and the advice on when to use each part.
Design System
A shared kit of parts and rules. It keeps a product the same on each screen.
A design system is a shared set of parts, rules and docs that a team uses to build one product or many. It holds the design tokens and the parts, in design files and in code. It also says when to use each one. It turns a hundred small choices into one agreed answer. A design system is a product of its own, with owners, versions and updates.
Component Library
The set of ready-made parts, like buttons. It lives in the design tool and in code.
A component library is the set of ready-made parts in a design system, like buttons, fields and cards. It exists twice: once in the design tool and once in code. The two should match by name and by how they act. Then the button in the design is the same button in the app. A library alone is not a full design system, which also needs rules and guidance.
In one line
- Design System
- A shared kit of parts and rules. It keeps a product the same on each screen.
- Component Library
- The set of ready-made parts, like buttons. It lives in the design tool and in code.