Answer the question
In order to leave comments, you need to log in
Should You Use Material UI in React?
I am currently working on a large application (React / Sass / TS etc.) and faced the fact that some developers have started rewriting components.
At some point, 1 of the developers started adding POC application elements to Material UI. After that, it was decided to start styling the Material UI and score on those components that were written by hand.
Recently, Styled Components have been used to document custom components and material sharpenings.
Now the application has about 50 screens, the number of which is growing, in this regard, it is logical to use Material UI for some components. But to finish it in the flesh to the pixel, given the fact that there are a lot of components that have no analogue in Material UI, it does not look logical and long. I don’t understand why use a Material button and sharpen it for a non-Material design.
Share your thoughts and experience with Material UI in React on large apps, what are the pros and cons?
Is it worth using it at all if you have to do non-Material design on top of it?
Answer the question
In order to leave comments, you need to log in
If you don't have enough developer resources or need to get your project up and running quickly, you can use M-UI.
I had to work with this library, I will say from myself, I would not use it because As the project grows, chaos, anarchy and component mutations begin.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question