If the go/no go is not given by the development team then you can find yourself in a situation where the developers have to give feedback to the designers because they have too many uncertainties about what they have to develop. Involving developers also allows them to give an opinion on whether the design-system is ready enough to start developing. Never forget to ask the developers if they consider the design-system ready for development After that our designer had to review all the designs using text (in other words all the designs). At the beginning our designer had created the mobile and tablet models without using all the correspondences between the two. This allows us to be more responsive but also to keep a good overall consistency of the design which improves the user experience. Therefore we designed our applications to have correspondence between mobile and tablet (web), in this way when we use the font: LabelSmall it will call the right font size depending on the type of the device/plateform. And we have developed this application to be as responsive as possible. We had already developed an application for mobile devices but also for tablets and web browsers. Let me put you back the context of my project and show you another way that mistake can unfortunately impact the project.
After that we, the developers, had to do a study on the existing calendar components and how they are customizable, then the designer could choose one and customize it within the limits offered by the component. Therefore it is much more pragmatic to try to make the design stick with something existing and trying to customize it to make it your own.
Design system designer code#
In this world we can find constraints related to the architecture of the code or even technical dependencies requiring the use of certain designs (framework, libraries…).Īs an illustration our designer had designed a calendar component unfortunately at the code level designing a calendar component from scratch can be complex and time consuming, enough that other developers have already dedicated time to compose this kind of component in the form of a library. There is a world between the theory of the design system and the practice at the level of the code. Not involving the developers in the conception of the design-system, can be a mistake, even more so if you are starting with an already existing application.
Design system designer how to#
Mistakes I have encountered and how to avoid them Always involve developers in the creation of a design-system Templates: the general content structure without the content,.Atoms: the basic elements (theme, small components.),.One of the most popular methodologies was theorized by Brad Frost with Atomic Design. The design-system is a great tool to improve the quality of the product (both at the level of the code and at the level of the result) but one must keep in mind that every design-system is an ambitious project, that requires rigor and methodology. it must be able to be reusable, adaptable and therefore it has to be platform agnostic: it must have HMI ergonomics rules and design standards so that it is reusable and adaptable to technologies (Smartphone, web, other HMIs).
0 kommentar(er)
