4 ms·
Creating a style guide and UI components is definitely a solid foundation! I also highly recommend the Design Systems Handbook (https://www.designbetter.co/desi
by enhdless 6y ago
Creating a style guide and UI components is definitely a solid foundation! I also highly recommend the Design Systems Handbook (https://www.designbetter.co/design-systems-handbook https://www.designbetter.co/design-systems-handbook).
The engagement model should be a bit of both:
- Designers who maintain the design system are like the architects, and advocate for other developers to use the system patterns. They should also partner with developers to ensure that the UI components are opinionated.
- You still need to consider your web app's overall UX flows though, so designers are still needed to mock up new features for the developers to implement. Even with a robust design system, there are many ways to easily create unintuitive or messy designs. A designer should be assigned to each team and be in charge of mocking up the team's work and ensuring that the team is properly using the design system.
- petespeed 6y agoThanks for the handbook link. For your second point (on UX flows), what stage in product iterations do you think those decisions should be made? I feel those decision belong more to product management and designers, and after they are finalized, designers need to communicate them properly e.g. via design reviews of new artifacts with developers before start of development, and/or document screen flows properly. In either case, to my original question, the interaction is not really "pairing" with developers. Agree? Disagree?