About the Polaris category

Polaris
1

This board is for questions related to Polaris. Polaris is a single UI framework that makes it simple to integrate with all Shopify surfaces, including Shopify Admin, Checkout, and Customer accounts.

2 Likes
2

Are there plans to have more polaris components moved to web components in the future? They are much easier to work with then the react components

1 Like
3

Yes absolutely. This is just the beginning :slight_smile:

1 Like
4

Glad to hear it, my team is very excited to have web components and even in basic testing I am already a huge fan and will be porting my existing projects over where possible

1 Like
5

Polaris using web components is a great idea, enabling more developers to use, better performance, fewer breaking changes, unified experience among Shopify Admin, UI extensions, etc.

A few questions and suggestions:

  1. UI extensions (like Checkout and Customer Accounts) and Shopify Admin are pretty different. If I understand correctly, UI extensions are buyer-faced and have limitations by design, for security and for consistent branding of the merchants; while Shopify Admin is merchant-faced and has more flexibility.

    • So how would the unified web components work for both? Would all components still be added, with some certain components being limited for UI extensions/Shopify Admin; or would only components that are common to both be added; or would Shopify Admin later be limited as the UI extensions?

  2. Maybe too soon to ask this: will Polaris React or Web components be the new standard, recommended way to build Shopify Admin apps?

  3. I think app developers would appreciate the CDN JS file to have some versioning. I think supporting only a few versions with relatively short lifespan could already help.

    • Although one intention of web components is to have much fewer breaking changes, frontend tends to change pretty frequently, so there could still be some breaking changes.
    • Some apps would prefer to have more control over the UI changes (e.g. look and feel, layout). So that they could prepare their Helpdesk, CS team, their internal mockups, etc.
    • Changes may not mean to be breaking changes, but some can have unexpected side effects. I think app developers would appreciate some control over when changes happen. So that, for example, when an issue happens, app developers can narrow down the cause easier.