5 ms·
I've been doing a lot of research into design systems and one thing that's lacking in most of these documentation sites is examples build with the component lib
by thdxr 5y ago
I've been doing a lot of research into design systems and one thing that's lacking in most of these documentation sites is examples build with the component library. It's hard for me to get a feel for it without being able to click through a real application.
Also, paid managed services on the backend are super common. I want a paid frontend component library. There are very few of these and I think there's room for an all star frontend team to sell professionally maintained, always improving components. Even on day 1 of my company I'd be willing to pay $100s a month for this
- robertlagrant 5y agoThere are a few such as Tailwind UI that are paid-for component libraries. https://tailwindui.com https://tailwindui.com
- thdxr 5y agoI've been a subscriber to TailwindUI since it launched. Unfortunately it's not well suited for complex B2B SaaS products that have high information density UIs
- arcturus17 5y agoMany companies do that for enterprise components, especially graphs and tables. For more general use I guess it’s hard to compete with the likes of Material UI.
- radley 5y ago> one thing that's lacking in most of these documentation sites is examples build with the component library Check out their main site kiwi.com for examples. This is part of a trend with enterprise design teams of open-sourcing their design systems. In some cases, there are direct benefits to clients and partners. Otherwise, it's a status project / time-filler.