News for hackers. Stuff that matters.
Re:Ask HN: How soon should we have a Design System? by ponyous on Thursday September 29, 2022 @07:14AM (#33018969)
> - Do you think it's too soon during the early days?

No, but you can just take one off the shelf and adjust colors / fonts.

- How do you manage product consistency without it?

You'll need experienced designer that knows how to gradually build it. Otherwise I can't see a way without.

- Do frontend engineers complain about not having one?

No, because we have one, but they complain when components could be used but something slightly different was designed.

A friend runs a consultancy and we recently spoke about it. They build e-commerce type of websites, they start with a simple mockup, once they are ready they build style guide/components. All other pages are just assembled from these components - don't think this works for completely bespoke software, but it demonstrates that in some cases it's integral to the rest of the process.

Re:Ask HN: How soon should we have a Design System? by Rafsark on Thursday September 29, 2022 @08:44AM (#33019776)
We build a DS from scratch since the beginning, and we feel we saved a lot of designing and engineering time. Releasing new features has been pretty smooth thanks to it. It took about 2 weeks to implement with basic components and it gives us consistency when designing/specifying a feature. But I totally understand what you say. It's not necessary to build a startup reaching PMF.