Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A React implementation of Spectrum, Adobe’s design system

react-spectrum.adobe.com

Post reply on HN
Print view View original

51–60 of 74 posts

Re: A React implementation of Spectrum, Adobe’s design system

#51

Post by hardwaresofton »

devongovett wrote: post #49
hardwaresofton wrote: post #46

Earlier quoted context omitted.

"design systems" in recent frontend parlance is generally colors + fonts + screen wids + methodology + components (usually) that all fit a certain visual style/philosophy. Material Design can be considered a "design" system. While the pieces of design systems make sense in and of themselves (you can argue for a clearer, easier to read font), I think a lot of bullshit gets dragged in along with people wanting to embra…

Many of our products also support third party extensibility, so the main business reason we pitched internally was making this easier for external developers. This helped us convince the bosses to invest in the project and let us open source and maintain it. And hopefully with React Aria, we provide value beyond the standard "look at our fancy components".

Congratulations on the launch! The external developer use case is one I didn't even think of -- I assume this is something like helping people make products that look and fit in with the feel of your other offerings.

Please feel free to amend/improve my definition of design systems above -- the term has meant so much over the years inside and out of the strict boundaries of pure graphic design -- I am not a designer/UX person by trade (I do it only when there is literally no one else), but write frontend code and have had some friends bellyache to me recently about trying to get design systems implemented in a local mid-large size company with a startup-like environment.

Re: A React implementation of Spectrum, Adobe’s design system

#53

Post by flowerlad »

devongovett wrote: post #44
flowerlad wrote: post #43

Earlier quoted context omitted.

Overall this looks nicely architected. However I don't see any data-intensive controls. Adobe being a graphics company may not need such controls, and this will probably be the weak point of this lib. If you want to see what data intensive controls take a look at Azure Portal. Hope to see such controls in a future version of this lib.

Adobe actually has a pretty big marketing business as well, along with applications like file managers (think web based versions of Finder or Windows Explorer). Tables are one of our most complex components, and are quite commonly used in some of our products. Our table implementation is a work in progress right now. It supports keyboard navigation, sections, sticky columns, multiple selection, infinite loading, drag…

That's good to hear! Here's another very important control: ComboBox. Data-intensive applications need powerful and flexible ComboBox with options such as dynamically supplying suggestions, ability to select multiple items (i.e., multi-select Combo which has checkboxes next to each option displayed in the dropdown), ability to search for an option in the dropdown (so the dropdown has a searchbox at the top) and so on.

Re: A React implementation of Spectrum, Adobe’s design system

#54

Post by devongovett »

flowerlad wrote: post #53
devongovett wrote: post #44

Earlier quoted context omitted.

Adobe actually has a pretty big marketing business as well, along with applications like file managers (think web based versions of Finder or Windows Explorer). Tables are one of our most complex components, and are quite commonly used in some of our products. Our table implementation is a work in progress right now. It supports keyboard navigation, sections, sticky columns, multiple selection, infinite loading, drag…

That's good to hear! Here's another very important control: ComboBox. Data-intensive applications need powerful and flexible ComboBox with options such as dynamically supplying suggestions, ability to select multiple items (i.e., multi-select Combo which has checkboxes next to each option displayed in the dropdown), ability to search for an option in the dropdown (so the dropdown has a searchbox at the top) and so on…

Yep! ComboBox is also in progress/close. ;) https://github.com/adobe/react-spectrum/pull/421

Re: A React implementation of Spectrum, Adobe’s design system

#55

Post by ponker »

devongovett wrote: post #10
harel wrote: post #9

One of the things that I always find missing in these libraries/collections is a date/time picker. I know these are available via many separate projects, but it's nice if one picks a collection like that, that all inputs are homogeneous.

Our date picker is in progress right now actually. Should be available relatively soon. Date pickers are one of the most complicated components, especially due to internationalization/accessibility requirements.

Who is "our"?

Re: A React implementation of Spectrum, Adobe’s design system

#56

Post by ponker »

devongovett wrote: post #30
rp36 wrote: post #26

Earlier quoted context omitted.

Nice work. Questions: 1) What is the minified size of the library 2) Is there a kitchen sink app to review all features together?

1. Depends on how many components you use! Each component is a separate package, so you pay for only what you use. We also offer a monopackage containing all components, but it is fully tree shakeable so it should be equivalent to using the individual packages if you have a good build setup. 2. We're working on building some example apps, but for now, the docs are the best example. You can also try out the storybook…

You have to pay for this? Where is this on the page?

Re: A React implementation of Spectrum, Adobe’s design system

#59

Post by zelly »

wiradikusuma wrote: post #50

We should standarize these "UI themes" so that other frameworks don't get left out (e.g. easy for Angular/Vue to use this). In Java world, it's called SPI (Service Provide Interface), like API but the opposite.

It's called Web Components, a standard built into browsers for many years now which means it will be backwards-compatible in perpetuity.

Re: A React implementation of Spectrum, Adobe’s design system

#60

Post by crubier »

ponker wrote: post #56
devongovett wrote: post #30

Earlier quoted context omitted.

1. Depends on how many components you use! Each component is a separate package, so you pay for only what you use. We also offer a monopackage containing all components, but it is fully tree shakeable so it should be equivalent to using the individual packages if you have a good build setup. 2. We're working on building some example apps, but for now, the docs are the best example. You can also try out the storybook…

You have to pay for this? Where is this on the page?

I think he means to pay the cost in terms of package size, not dollars
Post reply on HN