Adobe's UI Library is Finally Out

preview_player
Показать описание
I'm pretty skeptical when it comes to large corporations releasing their own tech. This one is kind of a banger though

-- my links
Рекомендации по теме
Комментарии
Автор

Its react-aria-components vs radix-ui, not shadcn. Radix UI is what powers shadcn and it is also focused on accessibility.

clamentjohn
Автор

Congrats on 100k, hard work pays off. 200 videos and really good content. Keep up the good work!

pelazas
Автор

Wouldn't a better comparison be Radix? Isn't ShadCN essentially a modified version of that?

michael.knight
Автор

What everyone misses about this library is that is breaks everything down into hooks for interaction, state and accessibility. The components are awesome but if you need a component to act a different way in your design system it's hard in most UI libraries to alter it. This one gets around that issue by making so that you can build your own with their hooks and alter it in anyway with your own state. It's roll your own + use ours. Truly one of the best react specific libraries out there. Definitely needs better docs as they don't do it justice.

CommunityAllSeasons
Автор

the hit for bad contrast came from their choice of Gray text on black background

jmula
Автор

We use RAC at work. And I must say it is far better than what we think. The integration with tailwind is just awesome

nikhilsnayak
Автор

I've been using React Aria for nearly a year now and love it. The new RAC library is just awesome. Especially love the button component - as simple as it is.

dMDzn
Автор

I bet you have to rent it for £20 a month

DeepTitanic
Автор

bro I stay following your channel cause you always posting the hottest new packages and component libraries.

rjwhite
Автор

1:44 I'm suprised the contrast issue doesn't point to a certain HTML element because Lighthouse usually does show that to easily be able to see what elements are causing trouble.

2:50 I do think shad cn is a nice concept and looks great, but please stop talking about it like it invented how to build component libraries. People have been building component libraries with these patterns for a long time. Only difference is that they didn't share their source code for others to copy paste.

randmtv
Автор

As a full time video editor who deals with Adobe’s inefficiencies in basically every program they have on a daily basis, I want nothing to do with this library no matter what 😂

robertm
Автор

“Become a UI dev” -> uses comic sans.
THIS 😂
I f’ing love you man hahahaha

Hellbending
Автор

800kb of bundle size for a ui library is a very rough pill to swallow through....

davidsiewert
Автор

This is the component version of react-aria, which has existed long before, am I right?

_nikeee
Автор

I would love to see your take on styled components sir. Great content! 😊

paw
Автор

it's good? Not sure. I am honestly disappointed by it. But it's understandable for a v1.0.0. I've been using it in the past two weeks and I saw two big issues with it: 1. in a Nextjs 13/14 app server components, it loads the entire 40+ components even if you use only a simple button. In client components, it doesn't split correctly the modules per page. 2. The onPress even is pressing twice on mobile Android devices if you have a button under the button you press (using conditional rendering to render the 2nd button after the first one is pressed. This like a show/hide component).

ionelCristianLupu_
Автор

Every time you start a video, you open your arms. I feel like you want a hug 😊

hyperprotagonist
Автор

Can you explain the obvious reasons styled components shouldn’t be used?

jgoon
Автор

That's really cool that they are aiming for React-native Pressable like experience.

iLiran
Автор

the goal is to delight the user. that's what matter in a product not the biggest technical score on google light board when you have a product that people love people come back to it

TheBlackManMythLegend