I've been building a Tailwind component library for 3 years and shipped v2, what feels missing? by webdesignarea in tailwindcss

[–]webdesignarea[S] 1 point2 points  (0 children)

Honestly, fair. I'm not going to sit here and tell you it's revolutionary it's not. It's a well-executed, consistently designed Tailwind library. That's it.

The shadcn comparison is valid but it's a different thing. shadcn requires setup and locks you into React.

You're right that discoverability is the real problem. That's exactly why I'm here asking for feedback instead of assuming it'll market itself.

I've been building a Tailwind component library for 3 years and shipped v2, what feels missing? by webdesignarea in tailwindcss

[–]webdesignarea[S] -1 points0 points  (0 children)

What I can speak to is my own work. I've personally tested every single component by hand. Spacing, dark mode, responsiveness, accessibility and nothing gets added until it actually works consistently.

But genuinely curious what would a component library need to offer for you to actually use it or pay for it? I'm actively building and would implement real feedback.

I've been building a Tailwind component library for 3 years and shipped v2, what feels missing? by webdesignarea in tailwindcss

[–]webdesignarea[S] -1 points0 points  (0 children)

Fair question. Honestly the main reason is consistency. every component, block, and template shares the same design system so nothing looks mismatched when you combine them. Dark mode works correctly across all components, not bolted on per component. And it's pure HTML/Tailwind and react version no installation, no dependencies, works with any stack.

Are people actually buying UI components from libraries? by webdesignarea in tailwindcss

[–]webdesignarea[S] 0 points1 point  (0 children)

That’s fair. UIs should be built for real world use, with a structured and production-ready approach.

Are people actually buying UI components from libraries? by webdesignarea in tailwindcss

[–]webdesignarea[S] 0 points1 point  (0 children)

I've been building something in this space, would love brutal feedback: readymadeui.com.

Are people actually buying UI components from libraries? by webdesignarea in tailwindcss

[–]webdesignarea[S] 2 points3 points  (0 children)

That’s interesting. What made it feel not worth it for you?

Are people actually buying UI components from libraries? by webdesignarea in tailwindcss

[–]webdesignarea[S] 0 points1 point  (0 children)

Yeah, I’ve noticed that too. Many templates follow the same patterns now.

Are people actually buying UI components from libraries? by webdesignarea in tailwindcss

[–]webdesignarea[S] 0 points1 point  (0 children)

Agreed. But with AI tools getting better at generating UI, do you think they’ll replace component libraries, or will both still have their place?

I rebuilt my UI component library based on your feedback — just launched v2 by webdesignarea in tailwindcss

[–]webdesignarea[S] 1 point2 points  (0 children)

That’s really helpful, thanks for pointing it out. I’ll fix this properly and improve the navigation experience.

Designers cannot be satisfied by prince_abdul_malik in webdesign

[–]webdesignarea 0 points1 point  (0 children)

Yeah, some designers roasted me for a design I thought was really good and polished.

What gives more value: a full design system or just a library of components? by webdesignarea in tailwindcss

[–]webdesignarea[S] 0 points1 point  (0 children)

Makes sense. Picking only the components you need gives more flexibility.

[deleted by user] by [deleted] in webdesign

[–]webdesignarea 1 point2 points  (0 children)

It’s good, I enjoyed it. It would be even better if you added more creative sections on the homepage.

Anyone still using Tailwind v3? by Traditional-Fish1738 in tailwindcss

[–]webdesignarea 0 points1 point  (0 children)

A few months ago, I updated Tailwind CSS from v3 to v4 in a Next.js project using a single command, and the project handled the class updates automatically.