Executive summary
- What: a Polaris 2.0 release candidate is available for embedded App Home interfaces, carrying the visual language of the redesigned Shopify admin.
- Why: the new admin design began rolling out to merchants on September 15, 2026, and apps that do not adopt will look visibly out of place inside it.
- Who: any organisation running custom or private embedded apps, and any app partner in the Built for Shopify program facing the May 1, 2027 deadline.
What changed
Shopify published polaris-2.0-rc.js on its CDN. When an embedded App Home interface loads that file, its Polaris Web Components render in whichever visual style the host store uses: the new design in stores that have received the redesign, and the existing polaris-1.js styling in stores that have not. Rendered outside the admin, components default to the new style, which is how teams without access to a redesigned store can preview it.
Adoption is explicit. Apps pointing at polaris-1.js or the legacy polaris.js URL do not move to Polaris 2.0 on their own. Admin UI extensions and App Home UI extensions are the exception: they already track each merchant's admin design automatically and need no code change.
Why it matters
The redesign is not only cosmetic. Most enterprise stores run at least one internally built embedded app: a returns console, an ERP sync dashboard, a wholesale pricing tool. Those interfaces were styled to blend into the admin, and blending in is what breaks when the admin moves and the app does not. Staff notice, and an interface that looks broken gets trusted less, which raises the support load around it.
The May 1, 2027 date is the part worth calendaring. Built for Shopify apps must match the admin's visual style by then, so any vendor app in your stack carries a remediation obligation you can ask about now rather than discover later. For your own custom apps there is no enforcement date, but the same visual drift applies, and the work is cheaper scheduled than rushed.
One practical detail matters. The redesigned admin includes a floating Sidekick bar near the bottom of the viewport. Apps with fixed or sticky bottom content will be overlapped unless they respect the environment API's --shopify-safe-area-inset-bottom CSS variable.
Role-specific impact
- Marketers: no storefront or campaign impact. Internal tooling used for merchandising will look different, so allow a short familiarisation period around launch timing.
- Developers: swap the CDN URL to the release candidate and test. If the interface still uses Polaris React, migrate to Polaris Web Components first, beginning with Page, Section, and Button, which carry most of the visual weight.
- Store admins: expect your admin to change appearance during the rollout, and expect custom apps to lag until they are updated. Collect screenshots of anything that looks wrong and route them to whoever maintains the app.
Use-case example
Real-world scenario
A distributor runs a custom embedded app that its customer service team uses to issue credits against B2B orders, roughly 400 times a week. The app was built on Polaris React in 2023. When the new admin design reaches their store, its buttons, spacing, and icons no longer match the surrounding chrome, and a sticky action bar at the bottom of the credit form sits underneath the Sidekick bar, leaving the confirm button unreachable on laptop screens. Caught during a release candidate test, that is a half-day fix. Caught in production, it is a work stoppage on 400 weekly transactions.
Implementation checklist
- Inventory every embedded app in your organisation and record whether each uses Polaris React, Polaris Web Components, polaris-1.js, or the legacy polaris.js URL.
- Create a development store with the new Shopify admin design feature preview enabled.
- For apps already on Polaris Web Components, point the script tag at polaris-2.0-rc.js and test.
- For apps on Polaris React, migrate to Polaris Web Components first, starting with Page, Section, and Button.
- Audit every fixed or sticky bottom element and apply --shopify-safe-area-inset-bottom.
- Test each app three ways: in a redesigned store, in a store on the previous design, and outside the admin.
- Ask each third-party app vendor in your stack for their Polaris 2.0 timeline against the May 1, 2027 Built for Shopify deadline.
FAQ
Q: Will our apps break if we do nothing?
A: They will keep working. Apps on polaris-1.js or the legacy URL are not migrated automatically, so functionality is preserved. The interface will simply look increasingly dated inside a redesigned admin.
Q: Should we adopt a release candidate in production?
A: Test with it now, ship on your own judgement. The value of a release candidate at this point is that it lets you find layout problems while both admin designs are still in circulation, rather than after the rollout completes.
Resources
Migrate from Polaris React to Polaris Web Components
Need guidance? Talk to Makro.