Background of project component library creation We often encounter such work scenarios in our work: Designer A: Designer B, send me the design draft of your xx project, I will use one of the components in it. Designer A: Designer C, why are the colors in your design draft executive email list inconsistent with mine? Which one is the main one? Designer C: Go ask the supervisor which is the main one. Head of Product Department: Director, why are all project components not unified? executive email list Product Manager: This time the requirements have not changed much from the last time.
Many components can be reused. Why does the designer take so long to evaluate? Front-end engineer A: Why is the style, color, and components of the design draft different executive email list every time, and I have to write a new style sheet, which will definitely not be completed in 2 days. Development Engineer B: Why did you change the components again? The function is not ready yet executive email list ... Such dialogue scenes are all too common. Everyone is shirking their responsibilities.
The product complains that the designer’s design progress is too slow. The designer complains that the communication was not good in the early stage. This series executive email list of problems keeps recurring, forcing us to find solutions. 2. What is a component library Component design is through the disassembly, induction, and reorganization of elements in executive email list function and visual expression, and based on the purpose of being reused, to form standardized components, and to construct the entire design scheme through multi-dimensional combination, and organize these components together.