[corytheboyd]

In your experience, do you know if engineers implement the shared component libraries as such in the actual applications? This would be as opposed to engineers directly implementing the end result of work in Figma (Sketch, etc.) that utilizes said components. There is a big difference there, and I'm always curious to have more data points about how this actually happens at other organizations.

[emptysea]

Anecdote: at my current org the ideal we talk about is having a component library designed in Figma by the Designers and implemented by the engineers.

In reality Design doesn't use components and most pages end up being composed of a bunch of one-off components and we waste a ton of time.

As a side effect of this, the app design isn't consistent across pages because we aren't sharing components.

[gedy]

Ditto, we have a quite a few designers and they mostly seem to struggle with thinking in components. They use design system like a color guide, and we keep reimplementing patterns on many pages.

[corytheboyd]

Yeah that is the exact result I have observed before as well. I'm really curious to hear more examples about how this actually works out well in the end from others.

I recognize that my view of this is from the bottom up in terms of only really having worked for SV startups, but I want to learn more and see if I can't make it work a bit differently this time.

[davidivadavid]

Some do, sometimes relying on things like Storybook.js to do QA in the middle. There's more and more things to maintain consistency between Figma design and e.g. React components being built.