Component Library vs Pattern Library
A component library holds single parts, like a button or a field. A pattern library shows how parts work together. Each pattern solves one problem, like a sign-up flow.
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.
Pattern Library
Tried ways to solve design problems that keep coming up.
A pattern library collects tried ways to solve common design problems. A sign-up flow, a search with filters and an empty inbox are all patterns. A pattern is bigger than one part: it shows how a few parts work together for one job. Each entry says when to use it and when not to. It saves a team from solving a problem that another team already solved.
In one line
- Component Library
- The set of ready-made parts, like buttons. It lives in the design tool and in code.
- Pattern Library
- Tried ways to solve design problems that keep coming up.