Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why use the library when you are not interested in Material Design? #23502

Closed
1 task done
fatso83 opened this issue Nov 13, 2020 · 2 comments
Closed
1 task done

Why use the library when you are not interested in Material Design? #23502

fatso83 opened this issue Nov 13, 2020 · 2 comments

Comments

@fatso83
Copy link

fatso83 commented Nov 13, 2020

It is mentioned as a oneliner here and there that Material UI can be used to build your own design system. I think this deserves a few pointers for the people who are wondering what Material UI brings to the table if you are not really interested in using Material Design. If at all! Maybe you guys think it best to start from scratch in that case?

  • I have searched the issues of this repository and believe that this is not a duplicate.

Motivation 🔦

We have been using the basic components all along, but they are always being styled with different colors, removing shadows, making them "flatter", etc. I find it hard to know how to use Material UI in the intended fasion when we do not have use for 20 different predefined font types and various pallettes. They all relate to some Material Design thing, and it's hard to relate this to our world. There is a lot of value here and there, but I think we are not using it in the intended fashion, as there is not very much "birds eye perspective" type of documentation. Having some articles that did not just touch upon the details, but had some discussion on why and how would be good.

@fatso83 fatso83 added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Nov 13, 2020
@oliviertassinari
Copy link
Member

oliviertassinari commented Nov 13, 2020

Maybe you guys think it best to start from scratch in that case?

I would personally never start from scratch. Material-UI is a great option among others.

A quick simplification of the value proposition

v4

  • Start from a word-class React design system
  • Customize Material Design to match your use cases

v5

In the version we are actively working on, we try to provide better answers to the above:

  1. Unstyled components: Provide a version of the components without any styles #6218. Our progress so far: https://next.material-ui.com/components/slider/#unstyled-slider
  2. sx prop: Use @material-ui/system in the core components  #15561. Our progress so far: https://next.material-ui.com/system/basics/
  3. A comprehensive set of components. Consistency. The ones that the open-source model can't sustain are paid, e.g. advanced date grid. We have a survey running.
  4. Built-in accessibility: [material-ui][docs] Create ADA compliance documentation #14187. We plan to have a full audit.

Future

Things that we will keep exploring once the above is more mature:

@oliviertassinari oliviertassinari added discussion and removed status: waiting for maintainer These issues haven't been looked at yet by a maintainer labels Nov 13, 2020
@oliviertassinari oliviertassinari changed the title Why use Material UI if you not interested in Material Design Why use the library if you not interested in Material Design? Nov 13, 2020
@oliviertassinari oliviertassinari changed the title Why use the library if you not interested in Material Design? Why use the library when you not interested in Material Design? Nov 13, 2020
@fatso83 fatso83 changed the title Why use the library when you not interested in Material Design? Why use the library when you are not interested in Material Design? Jan 5, 2021
@jemmaengz1202

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants