4 ms·

I find myself asking why this is so common. I guess this is welcome because it's based on something other than React? My last employer (or the company that acq

I find myself asking why this is so common. I guess this is welcome because it's based on something other than React? My last employer (or the company that acquired them, rather) had a team of ~8 working on a design system/component library , trying to encourage adoption across 5+ disparate apps. Our app used Angular. They used React for their implementation. No consideration for mobile whatsoever. While I understand the desire for consistency in UX (so that it's harder to tell 3/5 products were acquisitions...), for a company that was so focused on "becoming cash-flow positive" they seemed to have no qualms about reinventing the wheel in the UX space.

bradhe 4y ago
I think you inadvertently hit the nail on the head here. UX teams looooove to geek out about design systems. If leadership doesn’t understand design (which, let’s face it, they typically understand less than software engineering) the UX folks will get to run wild on this project. Couple that with the fact that in 2023 “good design” has a strong center of gravity and you end up with tons of these “systems” that look the same. And, by the way, most of these systems can’t be used outside the context of authoring teams’ apps anyway because there are tons of little specific integration points that aren’t included in the system itself!