Compare design
systems

Polaris launched in 2017 to unify the merchant-facing surfaces of Shopify Admin. It has matured through multiple major versions while remaining unusually grounded in the realities of merchant workflows — long forms, complex tables, error recovery, asynchronous bulk operations.

IBM open-sourced Carbon in 2017. It absorbed lessons from earlier IBM design languages and aligns with the IBM Design Language. Carbon ships across web (React, Angular, Vue, Svelte, vanilla), iOS, and Android.

Google introduced Material in 2014. Material 3 (announced 2021, matured through 2022–2024) is a full reset around dynamic color, expressive theming, and a token-first architecture. The earlier MDC libraries are still maintained but the design philosophy has shifted decisively.

Centralized core team owns the canonical components and tokens; product teams contribute through a public contribution model. Token decisions go through internal RFCs; component changes ship behind versioning with deprecation periods.

IBM design and engineering teams own the system; community contributions accepted through GitHub. Strong RFC discipline and explicit deprecation policy. Open-source with a public roadmap.

Google design and engineering teams own the canonical specification. Component implementations exist for Android, iOS, Flutter, and Web (MDC, Material Web). Cadence is fast and Google-product-driven.

• Industry-leading content guidelines — Polaris's voice & tone documentation is widely cited beyond Shopify.
• Mature data-table and form patterns built for genuinely complex merchant flows.
• Public, opinionated guidance on accessibility for transactional interfaces.

• Strong cross-framework support — Carbon ships first-class libraries for React, Angular, Vue, Svelte, and Web Components.
• Public design tokens with a clear primitive-vs-semantic structure.
• Detailed motion language with documented duration and easing tokens.

• Dynamic color — extracting a palette from user wallpaper or brand seed and generating accessible tonal scales automatically.
• Token-first architecture: design decisions live as tokens, components reference them.
• Expressive type, motion, and shape systems that scale from product to brand.

• The empty-state and error-state catalog — better thought through than most public design systems acknowledge.
• Detailed admin UI patterns (bulk actions, async results) that most design systems duck.

• The data visualization tokens and component family (Carbon Charts) are an underused asset.
• Carbon's grid system is genuinely flexible and well-documented.

• Material's accessibility documentation is more thorough than most teams realize.
• The HCT (hue, chroma, tone) color space behind dynamic color is open and adaptable to non-Material systems.

• Polaris is built for Shopify Admin, not for marketing surfaces — applying it to a content site without adaptation produces a tool-shaped marketing site.
• Heavy on patterns specific to commerce; you will inherit assumptions you may not want.

• Visual identity is intentionally enterprise — bringing Carbon to a consumer product means significant retheming.
• API surface area is large; full adoption is a real commitment.

• Material's visual language is strong enough that adopting it without retheming makes your product look like a Google product.
• Material Web (the official web implementation) is still maturing — many web teams use community ports or build their own.

• ResourceList / IndexTable
  Bulk-action data grids that are genuinely usable at scale.
• FormLayout
  Field grouping that handles long forms and inline validation cleanly.
• Banner
  The reference example for inline status messaging in admin UIs.

• DataTable
  Sortable, filterable, expandable grid that scales to enterprise data volumes.
• Notification
  Toast and inline notifications with clear severity and dismissal patterns.
• Tile
  Composable surface with selectable, expandable, and clickable variants.

• App bar (top)
  Composable header with scroll-aware elevation behavior.
• Filled / outlined / text fields
  Three input styles each with clear use guidance.
• Cards
  Three card variants (elevated, filled, outlined) that map to information hierarchy.

Pick Polaris if you're building merchant- or operator-facing tools with form-heavy interactions. Don't pick it as a marketing or storytelling system — its patterns assume a logged-in user doing real work.

Pick Carbon if you're building enterprise tools that need to look serious, work across many frameworks, and survive a security review. Don't pick it for a consumer-facing brand-led product.

Pick Material 3 if you're shipping Android, building a Flutter app, or want a reference for token-first system design. For pure web product work outside the Google ecosystem, Material is more useful as a reference than as an off-the-shelf component library.