Shopify Polaris

Polaris is Shopify's design system for software that runs inside Shopify itself. Shopify now describes it as a unified UI framework built on web components, used across every app surface on the platform: App Home inside the admin, extension points in the admin, checkout, and customer accounts, and Point of Sale. If you are building a Shopify app, this is not one option among many; it is the system your interface is expected to be built with, and matching the surrounding admin is most of the value.

The 2025 pivot: React out, web components in Polaris started in 2017 as a React library, @shopify/polaris, built in a public monorepo with companion packages for tokens, icons, a VS Code extension, and stylelint rules. On October 1, 2025, Shopify released Polaris Web Components for app development and deprecated the React library in the same move. The old repository is archived and unmaintained, available for historical purposes, and Shopify directs developers to the web components for new work. Current documentation lives on shopify.dev, not in the old repo.

The reason Shopify gives is reach: web components are technology-agnostic, working with every framework, plain JavaScript, and server-rendered sites, where the React library only served React apps. For a platform whose third-party developers build on every stack, that is a sound trade, and it mirrors where platform UI is heading generally: the host platform ships components, and apps compose them.

What this means if you maintain a Polaris React app Your library still runs, but it is finished: no updates, no maintenance, and no path to the current admin look through React. New development belongs on the web components, and a serious maintenance budget now includes migration planning rather than version bumps. The component names and patterns carry over conceptually, but the implementation model changes from React props to web-component elements and attributes, so treat it as a rebuild of the view layer, not a find-and-replace.

The catch: it only makes sense inside Shopify Polaris is not a general-purpose library with a commerce theme. Its source license is a custom license based on MIT that restricts use to applications that integrate or interoperate with Shopify software or services, requires stand-alone apps outside Shopify to be visually distinct from Shopify products, and leaves icons and images to the separate Polaris Design Guidelines License Agreement. A team building an unrelated SaaS dashboard cannot adopt Polaris the way it could adopt Carbon or Ant Design, and should not try: the components are shaped for Shopify's surfaces, naming, and workflows, and outside that context you get the constraints without the payoff.

Bottom line Building for Shopify? Use Polaris Web Components, start from the shopify.dev documentation, and plan any remaining React surface as legacy. Studying design systems from outside the platform? Polaris is still worth reading as the clearest example of a platform house system, and of a maintainer retiring a framework library in favour of web components, but borrow the patterns, not the code.