nextui VS shadcn/ui

Something like NextUI would work, i.e. a “New Gen” UI framework. It’s Tailwind based AND it works in both .astro and .tsx files. Amazing!

Official Website: https://nextui.org/

NOTE: NextUI cards are used here to aid with UX.

Next js+ Next UI

Next UI stands out as an elegant, swift, and contemporary React UI library. Offering a user-friendly approach to theme customization, it simplifies the process of adjusting colors, fonts, breakpoints, and more. Its performance is enhanced by minimizing unnecessary style props at runtime, setting it apart from other UI libraries.

GitHub stars: 16.3k GitHub link: https://github.com/nextui-org/nextui Documentation: https://nextui.org/docs/guide/introduction

NextUI - 3rd party minimally styled component library built with React ARIA

NextUI: Not to be confused with the React meta-framework, Next.js, this library is built on top of Tailwind CSS, and claims to have a minimal learning curve. Themes are handled by your tailwind.config.js file, a11y out of the box, and there’s dark theme support for all components. Overriding styles is done just by putting in different Tailwind class names.

As of August 2023, it has got 11K GitHub stars and more than 25K weekly downloads on NPM.

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

This model is very similar to the popular shadcn workflow. After files are creating in your local repo, you can modify them and check them into source control.

Link: https://ui.shadcn.com/

One of my biggest fears as a frontend dev is to build UIs that are inaccessible for people. It's easy to take so many things for granted.

The good news is you get a lot of accessibility out of the box using native html. For higher abstractions I love working with accessibility first libraries like Shadcn (which is built on top of Radix): https://ui.shadcn.com/

For development of the UI components, we tried something new. Vercel has this new AI tool called v0.dev that allows developers to take advantage of shadcn/ui and Tailwind using nothing but words, which can then be easily downloaded to your local project using nothing but a simple npx command.