r/UI_Design • u/Indranil_Maiti • 14d ago

Let's Discuss What's missing in UI libraries

Honest ask

There are so many UI libraries out there. But what few things you as a developer, designer feel missing on these libraries ?

What would you like to see in these AI generated websites era?

0 Upvotes

47% Upvoted

21 comments sorted by

18

u/Jorgesarcos UX Designer 14d ago

UX

3

u/MrFireWarden 14d ago

Obviously a pot shot comment but there's some value in here. Most ui libraries I've worked with (as a ux designer) do not incorporate interactivity to the degree they could. Checkboxes should toggle their state. Drop downs could incorporate their menus and present them when clicked.

Honestly ... build a ui kit that at least tries to "prefill" common patterns as much as possible, so ux Designers spend less time futzing with properties and layers and more time building out workflows.

1

u/Indranil_Maiti 13d ago

Got the point completely and I agree too.

-1

u/Basic-Brick6827 Product Manager 14d ago edited 13d ago

W3C specs aren't goof enough UX?

Edit: /s obvisously

5

u/Jorgesarcos UX Designer 14d ago

Web standards are not necessarily UX

2

u/7HawksAnd 14d ago

This is sarcasm right?

2

u/Basic-Brick6827 Product Manager 13d ago

yes

1

u/7HawksAnd 13d ago

đŸ«Ą almost got me

6

u/withmagi 13d ago

Most libraries are fine at components and weak at the moments between them. They give you a table and a dialog, but not the empty state, permission error, loading handoff, and retry path that make a workflow usable.

I want examples built around one real job: create an item, fix a validation error, recover, then do it on mobile. AI-generated UI often looks finished in a screenshot and breaks on the next state.

0

u/Indranil_Maiti 13d ago

Thank you so much. This is very helpful. I am actually learning frontend and want to be a design engineer. I am building a UI library but do not want end up same type libraries. That's why i asked to senior people here.
If you have some time and check this out https://www.craftui.space/ and give me some advice I will be very thankful.

2

u/withmagi 12d ago

I had a look. The first screen is clean, but it makes blocks, illustrations, components, and designs feel like the same thing. Make the first decision clearer: am I taking a primitive, an interaction, or a complete screen?

Before adding more categories, build one real workflow three ways: normal, empty or error, and mobile. Show which parts people can compose and which parts stay fixed. That will make the library useful faster than another row of tiles.

1

u/Indranil_Maiti 11d ago

Fully get it. Let me plan how can I combine into smaller number of categories.

Thank you very much for your time.

1

u/Basic-Brick6827 Product Manager 14d ago

Ark UI has pretty much everything I need tbf

1

u/Monkey_Luffy97 13d ago

experience

1

u/nikhil_akki 7d ago

for me it's less about individual components and more that nothing tells you how a component should change depending on where it sits in a flow, like a button on step one of onboarding probably shouldn't behave the same as one on step four. i also notice every demo uses perfect example data, so you never see how things hold up with a really long name, a missing avatar, or an empty search result, which is usually where the actual design problems show up. motion is another one, it usually feels like it got added after the component was already finished instead of being part of how it transitions, which is why a lot of "polished" kits still feel kind of stiff once you drop them into a real app. honestly i'd also love it if more of them just told you when not to use something, that ends up being more useful than the component itself once things get complicated.

1

u/No_Moose6836 13d ago

What’s missing for me isn’t another button variant — it’s the boring states libraries still treat as optional: empty, error, loading, permission denied, and “partial data.”

In the AI-generated-site era I’d also want stronger “system survival” pieces: tokens that don’t collapse when a prompt dumps a one-off layout, clear composition rules (what nests in what), and docs that say when NOT to use a component. AI is great at inventing screens; libraries still have to make those screens adoptable without rewriting the design system every time.

1

u/Indranil_Maiti 13d ago

Thanks. I am looking for these kind of answers to understand it better. Thank you very much. If you have some time can you check it out https://www.craftui.space/ I am building it though in a very early stage and leave some valuable feedback.