Comment by Slim on "Ask Anything UI/UX and Design Systems to this group of Amazing Devs"

Hi, First of all thanks for your time to answer our questions.

1- What are the important things that you take into consideration when you design a new system?

2- Do you combine or mix some business rules when you develop the frontend part of the apps or you try to make a module or service that is responsible for that and trying to create components that are reusable whenever a new feature will be added later and independant of the business?

3- What are the best practices or tools that you follow in order to create an optimized UI for your apps and guarantee a short response time ?

4- What do you recommend for developers or team to take into consideration or to avoid when they will design a new UI for a project?

Hi slim, I'm not a designer but from a developer's point of view, here are my takes :)

When designing a new system, it depends on the scale of the relevant projects - is it going to be used across different projects? What frameworks or languages are used (like TypeScript, React, Vue etc) in these projects? And most important, what are the use cases for each component of the system (how generic it should be etc)
Not sure I understand your question. Can you elaborate a bit?
I normally go with Sketch/Figma to understand the style guides (color, font size, padding, etc), then use utility framework (TailwindCSS or Tachyon) to create the default variables for the basic style guides together with CSS, then use Storybook to start creating and testing the component in different use case. Of course the best practice is to understand if there is a possibility of expanding the functionality / use case of a certain component. Discussion with designer is always a good thing to do :)
Never assume the cases given by designer are everything and never create any component just because it is simple to do so :).

Search Hashnode