Juliana Amorim

Favorite UI component library

Hey folks! 👋

We’re gearing up for our next launch and would love your input.

There are so many great UI component libraries out there (Radix, Shadcn, NextUI, Tailwind UI, etc). Which one is your favorite, and what makes it your go-to?

Your feedback will help us shape what’s coming next 👀

Let us know what you use and why!

409 views

Add a comment

Replies

Best
Mike Ciesielka

@shadcn has a great post over on Twitter about their library calling it decidedly not "a component library" but instead "a way to build your component library".

https://x.com/shadcn/status/1912966327448584266

While they're doing a ton of things that make it easy to adopt all on its own via command-line tools and registry distribution, I think that central ethos is a big part of why it's so popular. Most component systems you build are going to want to do at least 80% (90%, more?) of the same things, and shadcn does an excellent job of handing you the baton for customization after its done the legwork on that shared functionality.

(Now I just need to get folks to let me use it here at PH)

Marcos Passos

@shadcn  @mike_ciesielka1 Totally agree.

Like I mentioned earlier, the only real downside is that once you install it, you're on the hook for maintenance and bug fixes. Sure, you can always re-download and tweak things again, but it kinda feels like a step back from everything we've streamlined over the years.

That said, as long as you're aware of the tradeoff, it's probably the best balance we've got right now between flexibility and reusability.

Hope you can get the team onboard! Btw, it goes really well with Croct 👀

Juliana Amorim

@shadcn  @mike_ciesielka1  Hey guys! We just launched this, and I'd love to hear your thoughts!

Lizelle van Vuuren

I'm sure it always comes to "it depends" but I find that all my frontend engineers love Tailwind and so that makes it easier for work to be collaborative as it changes hands.

Jake Crump

@amorimj You'll have to follow up and let us know which one you ended up going with!

Juliana Amorim

@jakecrump will do!

Juliana Amorim

@jakecrump, we just launched this! We decided to start with @shadcn/ui, @MagicUI, @Material UI , and @HeroUI . And we're currently working on the next libraries :)

Would love to hear your thoughts!

George Karan

For me, Shadcn is the one I keep hearing and coming back to. I like that you get the actual code for each component, so if I want to change something, I can just do it without weird workarounds. The components look good right away and they all fit together, which saves me time. Plus, the new registry feature is really cool and could change the industry—you can run your own registry and share custom components across projects. I just feel like I have way more control than with most other libraries.

Piotr Kusiak

For me it's either Radix or Bits UI - depends on the front-end framework

CaiCai

As one of the early initiators of Ant Design, I believe the most important thing about components is to unleash productivity and improve the efficiency of product iteration. Based on this, we can try to provide a better and more consistent product experience so that many projects without designer involvement can also achieve higher-level output.

Nika

My friend @annedevj created a component library: https://componentlibraries.com/ Maybe will be helpful for folks out there :)

Mather Marker

Honestly, I've bounced between a few but ShadCN/UI has been my recent favorite. It strikes a solid balance between flexibility and good design out of the box. What I love most is how it integrates with Tailwind makes customization a breeze without getting locked into rigid patterns.

Rohan Gayen

I use Shadcn. But looking for something for landing page, which shadcn doesn't provide.

Daad Kabbesh

Honestly, Shadcn has been my go-to lately. It strikes that perfect balance between utility and aesthetics. You get the clean look of Tailwind with headless accessibility baked in without looking you into rigid design patterns.

Marcos Passos

Shadcn is growing fast. The upside is that it literally copies the component files into your project, so you can fully customize them. The downside is that you're responsible for maintenance, you won't get updates automatically, so keeping things up to date is on you.

Launching soon!

adding a Tailwind-compatible starter kit or built-in dark-mode toggle would make Croct even more turnkey.

Alex Cloudstar
Currently I’m using ShadCN
steve beyatte

Tailwind because of the massive amount of well designed UI pieces that feel "copy and paste"

Alex Liu

I would say Hero UI, which is fit with Next.js framework smoothly

Juliana Amorim

@alex_liui, we just launched this, and we added support for @HeroUI :)

Would love to hear your thoughts!

Kay Kwak
Launching soon!

Tailwind 🍃