Component libraries
Styled, ready-made components that implement one design system, which you theme rather than build.
How they work
A component library ships finished components: markup, styles, behaviour and a theme. Material UI implements Google’s Material Design (version 2) for React. You install @mui/material together with Emotion, its default styling engine, then change colours, typography, spacing and shapes in a theme object, or a single element through the sx prop. Bootstrap does the same in CSS and HTML: it served as Twitter’s style guide for internal tools for more than a year before its public release in August 2011.
Pick one when the design system it implements is close enough to yours, or when looks matter less than speed, as in internal tools and admin screens. The cost shows when your design diverges: overrides component by component, extra CSS specificity for states such as disabled or focused, and breaking changes at each major version. Some libraries are open core: Material UI is MIT-licensed, while advanced data grid features in MUI X need a paid licence.
Technologies
What all ui libraries have in common →| Open source | MUI | MIT (Material UI and MUI X Community); MUI X Pro and Premium are commercial | 2026-10-09 |
Sources
- Material UI docs: Overview (implements Google’s Material Design; supports Material Design 2)
- Material UI docs: Installation (Emotion as default styling engine)
- Material UI docs: How to customize (sx prop, state classes and specificity, theme overrides)
- Bootstrap docs: About (created at Twitter, internal style guide, released 19 August 2011)
- MUI X docs: Licensing (MIT Community plan; commercial Pro and Premium)