3 ms·
Depends on your people and what you define "design system" as. For most startups I'd highly recommend using off the shelf component libraries so that you don't
by gedy 4y ago
Depends on your people and what you define "design system" as. For most startups I'd highly recommend using off the shelf component libraries so that you don't waste time reinventing the wheel, and have your ux designers use those to assemble bigger patterns that can be reused. (Here's how we list things out, here's our tables, etc). Pick a framework that can easily use your branding colors and fonts, boring tech like Bootstrap, etc can go a long way here.
Developing a "Design System" can be a time sink in the wrong hands though, your people shouldn't be more interested in making that vs your product.
- ch_sm 4y agoI absolutely agree with everything said here, and want to add this: building a design system + component library is much harder than it looks, and a very significant time sink and working with a bad design system and component library is extremely inhibiting, especially when you want to scale. Definitely use a full-featured existing library (Material UI, Vuetify or similar) and customize to your needs.
- michaelponrajah 4y agoFully agree at 100%, this is exactly what we did at Lago, use Material UI as a library, customised the CSS to make Lago-branding friendly. In that case we're not reinventing the wheel, we're using it and it helped us to go faster. I think it's just a matter of definition and our System is way far from ones you can see at Adobe, Shopify etc. Goal is to go fast and having this base, this language between Front and Design is important to have sooner than later.