zag VS shadcn/ui

Zag.js and Ark are headless component libraries created by the teams behind Chakra UI.

ChakraUI: An emphasis on A11y, meaning it is fully compatible with the WAI-ARIA accessibility standard, has won OSS awards, and has a thriving community. As mentioned, it’s one of the better choices out there as it has a great model for building composable UI, built-in hooks, and great dark-mode support. This is the same team behind Zag.js, which handles UI as state machines. Once again, you’d need to learn the API, and swapping might be hard to do.

I agree with what another poster said about Zag (also part of the Chakra project). It seems to me that eventually, with the explosion of number of frameworks, consolidation is going to happen. Segun is influential enough that Zag has a good chance of being what the consolidation ends up centering around.

it's not perfect yet, but I find zagjs promising

Keep an eye on ZAG and ARK from the Chakra UI team, I feel like together with UnoCSS that could get very powerful.

🔗 Head over to https://zagjs.com/ to learn more about Zag.js and get started with building accessible UI components in your web applications!

The Zag.js documentation can be found here: https://zagjs.com/.

Check out the beautiful UI crafted by ShadCN over at the deployed version of our app — sign in with Google and get some sweet cards! Plus, the entire project is open source. Grab the code from GitHub.

It’s Headless so you can use it with whatever UI components you have in your project and as with everything in TanStack it’s type-safe! In this example we'll use components from shadcn/ui to build the form but you can really make it work with any UI library.

Shadcn UI

You can access shadcn/UI using the following links. Official Site Github Repo

I build an Angular or React app or smart component that uses the store in an Nx monorepo. I use the Shadcn UI in React apps, and the Shadcn-based spartan/ui in Angular apps, so I can use almost the same app architecture both in Angular and React.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

Shadcn/ui: I've never tried it before but have always wanted to switch from MaterialUI

Honestly the ergonomics of heavily customizable generic component libraries aren't great. Copy and pasting a simple component to make the specific customizations you want helps reduce JS ecosystem churn and dependency pain. Popularity of libraries like shadcn/ui [1] are good acknowledgements of that.

[1] https://ui.shadcn.com/

shadcn/ui