Decide if we should buy a UI component library for React and/or Vue
Closed this issue · 2 comments
DU has compared TailwindUI and FlowBite as possible libraries that can be used to speed up the design phase when creating webapps. Both have a cost of about 800$ with a major limitation on publishing a derivative component library.
Major benefit we want is a simpler design process. We are all using TailwindCSS, but since this repo has React and Vue apps the story gets a bit complicated. TailwindUI and Flowbite both support React and Vue. React have transitioned to "natively" support serverside components (RSC). This transition has made many popular component frameworks for React obsolete, as they must support server-side rendering whenever possible.
Creating a shared UI package necessitate good tooling. Storybook.js is a great tool for for developing components in isolation, but does not support multiple frameworks (React, Vue) in the same UI package, without creating tow separate Storybook.js "workbooks".
If a share UI package that exports React and Vue components can not be achieved there is less efficiency "released".
Currently i believe creating a React library from shadcn/ui would be the quickest solution. Resulting in two separate ui packages, i guess.
I have tested shadcn/ui for react now, and i love it. I am back to the "chakra" feeling, but with more control. It is tied to Radix primitives. Its ok. No problem using other "headless" component libraries, by the way.
I think we are all happy on this front now? Closing.