Design request center
Create within the case → Send us request
→ We will work out it → Final review
Use right tokens for right platform!
If you use RN tokens to build designs for web, developer will face the problems with recognition of them because web-developer can’t use RN tokens. RN & Web code base are separated and isolated by different repositories.
Learn more about design
What you should do as a designer?
In terms of DS there are few possible ways.
Flow on the product design side:
- On the design side, make sure that none of the current organisms are suitable for solving the case (It is advisable to do this before starting a request for creating a new component)
- It is necessary to synchronize with the DS team, perhaps the solution can be found at this stage (For example, it will be enough to add a new variation and modify what is already there).
- If it turns out that the component is necessary, the designer works it out within the case.
- Then sends it to the DS team (branch, designs, etc.) , which prepares the component for production, checks consistency, finalizes all the necessary states, describes the documentation
- Review by the initiator designer
Flow of creating a request for a component:
Interaction with the DS team will be built on a ticket system.
- A request to add a component is created immediately after the need arises, before any syncs and interactions (in other words - Ticket is the entry point into the process).
- Within the framework of the ticket we sync/ decide to add a component/ search among ready-made solutions.
- After making a decision to add the component to the task body, the designer attacks the developments within the case and transfers the task to the DS team.
- After the component is worked out in the DS team, the designer is reviewed
- After the review stage, the component is sent to the producer and gets into the storybook
Think in advance
Please, come with your requests at the earliest stage of feature preparation. That will help save your time by excluding overthinking the problem area.
Learn more about design
This process includes anything related to modifying existing components. Adding a new variation, fixes of variation faults and auto-layouts.
- A Ticket is started on the DS board, which describes the essence of the change.
- Perfect if you will
- The DS team sits down with the initiator and makes edits
- The DS team sits down with the developer and notifies him of the changes made.
- Developers take the Ticket with changes into work.
Process of creating new libraries / refactoring existing libraries
Controlling the number of libraries is a prerequisite for proper scaling of DS. To avoid uncontrolled overrides in the layout, it is important to formalize the process of creating libraries and make it under control.
- The decision to create a new library is made by the DS team
- Creation of a new library must be justified, so if such a request comes from outside, a justification is needed
- A request to create a new lib is entered in ticket format on the team board in Jira.
- After the request is made we will start the process of creation
Everything would be done in sycn with product team.
The process of adding new icons
Product icons are realized by product designers. Icons should be created according to certain rules described in the guides. Check the icon guide →
After completion of development within the framework of concepts, when the icon is sent for prolongation, the DS team is tasked with adding the icon to Storybook, and then to the product. Adding an icon to Storybook can be done by both product developer and DS developer using our Icon Tool →
- The icon is drawn within the framework of the case and its scope of application is formed
- The icon is coordinated with the product lead
- The task to implement the icon in Storybook is set.
- After implementation in Storybook, the icon can be implemented in the product interfaces.
Contact us in case of question
We are welcoming you to share with us any possible feedback or ask any question related to the product development process using Design-system! Feel fre to write me in DM - d.krikunov@mu.se.
In case of questions
These channels will help you to find an answer on any question somehow connected to the DS or around it. Please welcome with your ideas and problems here:
Channels:
#ug-design-system
#ug-design-system
#mu-design-system
#au-design-system
Your DS team
Dmitrii Krikunov
Design-system architect
d.krikunov@mu.se
Vitaliy Kapustyanov
Senior Designer
v.kapustyanov@mu.se
Alexander Komarov
Senior Frontend
a.komarov@mu.se
Azamat Dzebisov
Senior Frontend
a.dzebisov@mu.se
Peter Dorozhkin
Senior Frontend
p.dorozhkin@mu.se
Andrey Yakobchuk
Head of Frontend
a.yakobchuk@mu.se