Pros/Cons for these UI libraries
Unanswered
Anhinga posted this in #help-forum
AnhingaOP
Asking for help, I'm newish to NextJS and the amount of React libraries is overwhelming.
Can people offer pros/cons for each of these libs and if any of my concerns are valid?
I've chosen 4 to examine: Mantine, MUI, Shadcn and TailwindUI. I work in a very small startup where currently I'm the only dev. We have no UI/UX designer, I have some design sense - I just don't want to spend an eternity designing.
- I love the look of Mantine and the fact that you can use Tailwind if you like, but am unsure about the longevity of this kit.
- Willing to pony up for TailwindUI if it's truly as excellent as people claim (?). Since it's behind closed doors, I don't have enough info.
- MUI is a bit dull looking, but there's a huge amount of components/templates/everything really
- Everyone raves about Shadcn, but I guess I wonder about future proofing. If I have x amount of sites that all use Shad's components and there's a bug found in one, is it a pain to then update? (That being said I am building my app using 'next-drupal' which Shad wrote, I am a huge fan of his work).
- Being a solo dev, community support would be nice if I get stuck, but with Reddit/Discord and GitHub I feel it's not too huge of a factor.
Can people offer pros/cons for each of these libs and if any of my concerns are valid?
I've chosen 4 to examine: Mantine, MUI, Shadcn and TailwindUI. I work in a very small startup where currently I'm the only dev. We have no UI/UX designer, I have some design sense - I just don't want to spend an eternity designing.
- I love the look of Mantine and the fact that you can use Tailwind if you like, but am unsure about the longevity of this kit.
- Willing to pony up for TailwindUI if it's truly as excellent as people claim (?). Since it's behind closed doors, I don't have enough info.
- MUI is a bit dull looking, but there's a huge amount of components/templates/everything really
- Everyone raves about Shadcn, but I guess I wonder about future proofing. If I have x amount of sites that all use Shad's components and there's a bug found in one, is it a pain to then update? (That being said I am building my app using 'next-drupal' which Shad wrote, I am a huge fan of his work).
- Being a solo dev, community support would be nice if I get stuck, but with Reddit/Discord and GitHub I feel it's not too huge of a factor.
1 Reply
Everyone raves about Shadcn, but I guess I wonder about future proofing. If I have x amount of sites that all use Shad's components and there's a bug found in one, is it a pain to then update? (That being said I am building my app using 'next-drupal' which Shad wrote, I am a huge fan of his work).
Shadcn uses radix and tailwind. shadcn is merely a "full" library since all it does it make styled radx and tailwind components that are fully customizable.
If there were to be a bug in Shadcn, it is mostlikely caused by the underlying libraries which even more people uses.
MUI is a bit dull looking, but there's a huge amount of components/templates/everything reallyIf you dont like MU, try chakra or NextUI
These are UI libraries but they have different domain - i.e whether or not they tackle behavioral interface, or just the "aesthetic" part of it.
I would double bet on tailwind or any style that are pregenerated in the server because that aligns with the paradigm Next.js is trying to solve.
I would double check my use case if i were to select any css-in-js libraries like MUI or Chakra so its also not entirely out of my option. If they support server side rendering its good to go. (i heard
antd supports ssr)Willing to pony up for TailwindUI if it's truly as excellent as people claim (?). Since it's behind closed doors, I don't have enough info.There is also material-tailwind and other premade tailwind components