The React layer for Polaris Web Components
Skip the boilerplate. Ship production UIs faster.
One-time purchase · Lifetime updates · No subscriptions
Try selecting rows. This is a real Shopify-style index table — copy/paste ready.
How it works
Write React, not web component wiring.
Polaris Web Components
<s-button
commandfor="delete-modal"
command="--show"
tone="critical"
>
Delete
</s-button>
<s-modal id="delete-modal" heading="Delete product?">
<s-text>This action cannot be undone.</s-text>
<span slot="primary-action">
<s-button variant="primary" tone="critical">
Delete
</s-button>
</span>
<span slot="secondary-actions">
<s-button>Cancel</s-button>
</span>
</s-modal>Manual id wiring. Web Component syntax. Slot-based composition.
With this kit
<AlertDialog
trigger={<Button tone="critical">Delete</Button>}
heading="Delete product?"
>
This action cannot be undone.
</AlertDialog>Auto-wired triggers. React composition. Same Polaris output.
Try the Recipes
Real patterns. Real interactions.
Destructive Confirmation
View Component →Product: Blue T-Shirt
SKU: BTS-001
Require explicit confirmation before irreversible actions.
Success → Loading → Empty → Error
View Component →Handle every state — loading, empty, error, and success — in one component.
The problem
Polaris Web Components are not React-ergonomic at the app level.
It gives you primitives that are correct — but leaves composition, state, and flows to every app.
In React, that means glue code everywhere and inconsistent patterns.
There's no shared, React-native way to build real Shopify app pages on top of Polaris.
The solution
React-friendly APIs that just work.
Recipes and primitives
DataTable, AlertDialog, StatusBanner, LoadingState...
App-level building blocks
Bulk actions, destructive flows, async job states...
Opinionated defaults with escape hatches
Copy the code. Adapt it. No lock-in.
Same Polaris foundation. Much better React DX.
Application-level recipes
Opinionated page layouts and flows built from Polaris primitives. Index pages, detail views, bulk actions, and async job UX — already wired.
React-ergonomic by design
Intent-driven APIs, predictable state ownership, and shallow trees. Designed for React apps — not raw web component wiring.
Storybook for real scenarios
Every primitive, pattern, and recipe documented in Storybook. Inspect edge cases, loading states, and destructive flows before shipping.
Copy, own, and adapt
No runtime dependency or lock-in. Copy the code into your app, customize freely, and keep full ownership. One-time purchase.
Ready to ship faster?
Buy it once. Own the code. Get new recipes when they're worth adding.