Executive summary
- The Shopify admin redesign began rolling out on September 15, 2026. Admin UI extensions and App Home UI extensions pick up the new styling automatically, with no code change required.
- Embedded apps rendering their own App Home interface keep their current styles until developers explicitly adopt Polaris 2.0, which is not yet released. The current Polaris Web Components release candidate is 1.1.
- Concerns anyone maintaining a custom or private Shopify app, and merchants who will notice one looking dated inside the new admin.
What changed
The admin has new color, type, spacing and icons inside a new frame, with search, notifications and the store picker moved into a collapsible side navigation. For app developers the important part is how that styling propagates. Apps built on Admin UI extensions or App Home UI extensions inherit the refreshed styles automatically as the rollout reaches each shop, with no functional change and no extension code to update.
Apps rendering their own embedded interface fall into two groups. Those on Polaris Web Components 1.0 keep their current appearance and can move deliberately to Polaris 2.0 when its release candidate lands. Those not using Polaris Web Components keep their styles and will not pick up the new design at all. Under the Polaris CDN semantic versioning model, adopting a new major version is always explicit, so a merchant never sees an app partially restyled mid-session.
Why it matters
The explicit opt-in is the right call. The alternative, pushing a major design system change automatically, would have restyled thousands of embedded interfaces untested, producing broken layouts in front of merchants. The trade is that visual drift is now your decision and your timeline, which also makes it your problem when a merchant notices.
That is the real cost. During and after the rollout, an app keeping its old styling sits inside a visibly modern admin looking neglected, and merchants read that as staleness whether or not it works perfectly. If you maintain a private app your operations team lives in daily, or commissioned one as part of a custom Shopify app build, budget for a styling pass rather than discovering the mismatch when someone complains. Migrating to Polaris Web Components now is what puts you in position to adopt 2.0 cheaply when it ships.
Role-specific impact
- Marketers: If you distribute a public app, refresh listing screenshots once your interface matches the new admin. Old-frame screenshots will date your listing quickly.
- Developers: Nothing is required before the Polaris 2.0 release candidate. Use the interval to migrate embedded App Home interfaces to Polaris Web Components, and test under both the previous and new admin, since shops differ during the rollout.
- Store admins: Expect some embedded apps to look inconsistent with the refreshed admin for a while. This is a styling gap, not a fault, and functionality is unaffected.
Use-case example
Real-world scenario
A manufacturer runs a private app its service team uses to build quotes in the admin. It was built three years ago with a hand-rolled interface and no Polaris Web Components. When the redesign reaches their shop, the app renders in its original styling inside the new frame, and the break is obvious enough that agents ask whether it is broken. Nothing is broken, but the team files internal tickets and loses confidence in a tool they use for roughly 120 quotes a week. A scoped migration to Polaris Web Components, planned before the 2.0 candidate lands, removes both the visual gap and the future migration cost.
Implementation checklist
- Inventory your apps and classify each as Admin UI extension, App Home UI extension, embedded App Home on Polaris Web Components, or custom embedded interface.
- Confirm that extension-based surfaces need no work, since they inherit the new styles automatically.
- For custom embedded interfaces, scope a migration to Polaris Web Components on the current 1.1 release candidate.
- Test your app on a shop with the new admin and one without, since both exist during the rollout.
- Watch for the Polaris 2.0 release candidate and plan the version bump as an explicit, tested step.
- Refresh app listing screenshots and internal documentation once your interface aligns with the new design.
FAQ
Q: Will our app change appearance on its own when the new admin reaches a merchant?
A: Only if it is built with Admin UI extensions or App Home UI extensions, which inherit the new styles automatically. A custom embedded interface keeps its styling until you adopt Polaris 2.0.
Q: Should we wait for Polaris 2.0 before doing any work?
A: No action is strictly required before the 2.0 release candidate, but migrating to Polaris Web Components now means far fewer changes when it arrives. That is the useful work to do in the meantime.
Resources
Need guidance? Talk to Makro.