- App Shopify, Polaris 2.0, Shopify Admin, Shopify Development, Web Components
- Francesco Guiducci
Shopify Polaris 2.0: preparing an app for the new admin
Polaris 2.0 is now available as a release candidate for embedded App Home interfaces, while Shopify's redesigned admin has been rolling out progressively since September 15, 2026. For app developers, the practical point is simple: embedded interfaces do not move automatically, and as of September 28, 2026 Polaris 1.1 remains the stable production recommendation.
Shopify released the Polaris 2.0 release candidate on September 24. The new bundle carries the styles required for Polaris Web Components to match the admin design available in each store. Stores already on the refreshed admin use the new color, typography, spacing and icons, while stores still on the previous admin keep the Polaris 1-style appearance.
Who needs to update and who does not
Admin UI extensions and App Home UI extensions automatically receive the design used by the merchant's admin because Shopify renders those surfaces directly.
An embedded App Home that renders its own UI is different. Adoption is explicit. An app that stays on Polaris 1 or the legacy unversioned entry point does not move to Polaris 2 by itself. If the interface still uses Polaris React or a custom UI, the migration to supported Web Components needs to be assessed first.
A release candidate is not the stable release
Shopify's documentation still recommends the stable Polaris 1 channel for production. Polaris 2.0 remains a release candidate and can change during the soak period. I would use it now to prepare and validate the migration rather than automatically moving a stable production app.
When Shopify promotes 2.0 to stable, a stable channel will be published. Moving to it will still be an explicit app decision.
Polaris React is not a simple version bump
Apps already using Polaris Web Components can start testing by switching the loaded bundle and checking the interface. Apps still based on Polaris React need a more deliberate migration. Shopify is publishing component-by-component migration guidance and not every old primitive has a one-to-one replacement.
The goal should not be pixel-for-pixel imitation. Preserve behavior and accessibility: keyboard focus, error states, selection, navigation, responsive layout and save flows must continue to work after the UI primitives change.
Test checklist for an embedded App Home
- Test both the refreshed and previous admin. During rollout, the same app can be viewed in either environment.
- Check Page, Section and primary actions. They have the largest effect on visual alignment.
- Review custom CSS. Styles that manually reproduce old Polaris colors, shadows or spacing can become inconsistent.
- Check sticky and fixed content. Sidekick now appears as a floating chat at the bottom of the admin and can overlap controls near the lower edge.
- Test responsive layouts, zoom and keyboard use. Narrow widths, long translated content and visible focus are easy regression points.
- Finish with functional tests. Forms, filters, modals, navigation and saves must still produce the same result.
Shopify also provides a bottom safe-area CSS variable to help prevent fixed content from being covered by Sidekick's floating bar.
Built for Shopify: the date to remember
For apps participating in Built for Shopify, Shopify states May 1, 2027 as the deadline for embedded App Home interfaces to match the Shopify admin visual style. This is not a requirement to ship a release candidate today; it is a window to prepare, test and then adopt the stable version.
Three mistakes to avoid
First: treating the release candidate as if it were already stable. Second: manually redesigning the app to mimic the admin instead of relying on supported primitives. Third: checking only appearance while ignoring accessibility and behavior.
For Shopify app work, I would treat Polaris 2.0 as a migration gate separate from the functional release: test environment, incremental migration where needed, regression of merchant workflows, and only then a decision on the stable rollout.
The same principle applies to technical monitoring: a change is not finished because code changed, but when the real runtime confirms the expected behavior. See the guide to the Shopify Dev Dashboard. For coding agents and current Shopify documentation, see also Shopify AI Toolkit and the unified shopify skill.
