Polaris 2.0 RC is great, but we still can't match the admin's index table

[Luke]

First off, I’m genuinely loving the Polaris 2.0 RC. The refreshed styles look great, and components like s-empty-state, the new s-section slots and fontSize on text have already let me delete a load of workarounds from our app.

But once again we’ve hit the same wall: the admin has moved ahead and the components we’re given don’t match it.

The clearest example is the index table. Here’s a bare s-table in our app on 2.0 RC, straight on the page with no section around it:

And here’s the Products index in the refreshed admin:

They’re completely different. The admin table floats on the page, the search and filter bar is its own rounded bar above it, the header row is rounded, and each row gets a rounded hover. None of that is available to us with s-table, in or out of an s-section.

The search and filter bar is the part that hurts most. There’s no component for it, so I built our own to match the admin’s, for good reason: merchants move between the admin and our app all day, and they should get the same UI and UX in both. It’s the most hacked-together part of our codebase, and 2.0 has just made it look outdated overnight, because the admin version has changed again and there’s still nothing we can use to match it.

I’m not the only one. Other developers I’ve spoken to are in exactly the same position, each building and maintaining their own copy of the admin’s search, filter and table patterns, and each copy drifting a little further from the real thing with every admin update.

What would help:

1. An index table component with parity with the admin: search and filter bar, saved view tabs, sorting, bulk selection and the new floating layout. Even just the search and filter bar on its own would remove the biggest hack most of us carry.
2. When the admin gets a new pattern, the matching component ships at the same time, or at least a public note on when it’s coming.
3. Some visibility on the roadmap, so we know whether to keep maintaining our own versions or wait.

Built for Shopify asks us to match the admin’s look by 1 May 2027, which I’m all for. But it’s hard to match something when the building blocks for the most-used screen in any app aren’t available to us.

Is an index table or a search and filter component on the roadmap for 2.0?

[marconappa30]

I agree with you. How are we supposed to comply with BFS if Shopify doesn’t provide components that match the Admin 1:1? Polaris React was much better in that regard, because at least the components were complete. I hope a Shopify developer can clarify this.

[Tommy_Gaudreau]

Claude managed to do a pretty good job for me with a few screenshots and a bit of guidance!

Though I hope we won’t get penalized because we had to make our own components to replicate Shopify’s UI

(I do plan to use polaris table as soon as it reflects the look of the actual Shopify UI and definitely would have preferred not to have to go through that just to get something the library should have by default)

[Luke]

Yeah I already spent quite a fair bit of time hacking together to replicate the new search/filter bar, but I refuse to waste any more time hacking anything else when it should be the standard that they’re shipped when available internally.