Once again facing that classic #designsystem conundrum: Theme and/or customize a 3rd party component library, or build one from scratch.
Actually, we need two component libs: A #WebComponent one for web products and a #ReactNative one for iOS & Android apps. We already have designs in #Figma and want to have parity in terms of design & naming across Figma, web & RN.
My gut and past experiences make me lean towards building from scratch.
@cirrus it depends on how differ your designs from some 3rd party libraries on the market.
I went throught the same dilemma and finished with latest MUI library for Figma. It has variables for light/dark themes now and it’s perfect. For RN applications, we extended the library with pop-ups, alerts and some input components adapted for mobile. The major part of mobile component are taken from web component library. Here is a link https://mui.com/store/items/figma-react/.
@texcut Interesting. Maybe I should give MUI another look. I've worked with an old version (v4) of their React lib in the past, but I guess a lot has changed since then.
Good shout on using their Figma lib too, though. I do believe if you're going to use a 3rd party lib, you should go all in. Trying to bend them to designs that were made independently can be the source of much pain IMHO
@cliftonlabrum I wasn't aware of Expo. Looks interesting, but not sure it would work for us.
We have many existing websites/-apps built with a variety of frameworks. My aim is therefore to produce UI components that they can all consume at their own pace, to gradually migrate their UI code. Hence why web components was chosen.
I presume (maybe incorrectly?) that a library of Expo components would not be consumable in non-Expo apps. Right?
Add comment