ui.mantine.dev VS shadcn/ui

Official Website: https://ui.mantine.dev/

🔍 Site ⭐ GitHub

There are tons of SaaS templates, they look really professional and visually appealing, but once you have to customize it to your product it you will inevitably feel the pain. Different code styling, outdated libraries, lack of specific features. Them when you change its code and make it working, it becomes painful to sync with newer versions of the theme (if they are publishing updates lol). Screw it. I ended up using building blocks from https://ui.mantine.dev/

Website: https://mantine.dev/ and https://ui.mantine.dev/

More importantly, though don't feel bad. I've been doing frontend dev work and flex and grid are still confusing to me. They never behave the way I expect. I've come to rely on UI libraries that abstract away a lot of the concepts to make it easier for myself. I've been working with React recently and Mantine UI (https://ui.mantine.dev/) is the only reason I can make a half decent UI.

mantine ( https://mantine.dev/ ) is a good option. you need to learn their components and structure but it isn't hard. also, they have ready to use ui designs ( https://ui.mantine.dev/ )

Have a look at Mantine UI. It has a huge no. of components, hooks, etc. It's fairly easy to setup & customize as well. If you are familiar with Material UI, this shouldn't be too hard to work with.

For my last project i used mantine. Checkout https://ui.mantine.dev/

Using https://ui.mantine.dev/ as a personal favourite atm.

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

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/