Difference between React MD & Material UI

[deadcoder0904]

I think creating this issue here would make it visible to everyone who has the same question. So sorry for not asking on the Slack. Also Google will index this rather than putting it up on Slack.

I love both React MD & Material UI & choosing between them is going to be tedious work. Both use Material Design Specification.

How is this different from Material UI ?

[mlaursen]

The biggest difference between these two libraries is the styling methodology. I haven't really kept up with material-ui's development process, but the first version of material-ui was created with inline styles and now it appears to have transitioned to JSS. All the styling in this project is done via Sass/SCSS and an opt-in mixin based approach of including styles. I personally prefer having styles in a separate file which is the main reason for this to begin with though. A majority of the styles can be overridden by setting variables before including the styles and then props for exposing style and className have been integrated into each component as well to help with additional custom styling.

The next biggest difference is that I have been trying to keep components up-to-date with accessibility standards and conventions to help with screen readers, keyboard users, and other disabilities. It does look like the next version of material-ui has started implementing this as well, so it might not be a big selling point any more.

I also think my documentation is a bit easier to navigate and see live examples but that might be because I made it.

Finally, I'd choose one of these two based on how quickly you'd like updates to appear. I am the only main maintainer for this, so my releases and newer features might come a bit slower compared to material-ui. I normally try to answer questions and PRs as quickly as possible, but some times other things come in the way.

Hopefully this was informative and helps you and people in the future choose one of these :)

[MikeLimeRocket]

Thanks Mikkel for the background. Last time I checked React-MD was a small build size and seem to perform better on mobile (based on my tests) so there is also that selling point. Cheers, Mike. *Founder & CEO - BuzzyTV * Connect on LinkedIN <https://au.linkedin.com/in/mrmikeg> Create & Play Kits now available for your School Library. <http://buzzytv.com/for/schools> <http://buzzytv.com/for/schools> Twitter <https://twitter.com/buzzytvgames> | Facebook <https://www.facebook.com/buzzytv/> | Instagram <https://www.instagram.com/buzzytv/> | Snapchat <https://www.snapchat.com/add/buzzytv>

…

On Wed, Oct 4, 2017 at 9:02 AM, Mikkel Laursen ***@***.***> wrote: The biggest difference between these two libraries is the styling methodology. I haven't really kept up with material-ui's development process, but the first version of material-ui was created with inline styles and now it appears to have transitioned to JSS <https://github.com/cssinjs/jss>. All the styling in this project is done via Sass/SCSS and an opt-in mixin based approach of including styles. I personally prefer having styles in a separate file which is the main reason for this to begin with though. A majority of the styles can be overridden by setting variables before including the styles and then props for exposing style and className have been integrated into each component as well to help with additional custom styling. The next biggest difference is that I have been trying to keep components up-to-date with accessibility standards and conventions to help with screen readers, keyboard users, and other disabilities. It does look like the next version of material-ui has started implementing this as well, so it might not be a big selling point any more. I also *think* my documentation is a bit easier to navigate and see live examples but that might be because I made it. Finally, I'd choose one of these two based on how quickly you'd like updates to appear. I am the only main maintainer for this, so my releases and newer features might come a bit slower compared to material-ui. I normally try to answer questions and PRs as quickly as possible, but some times other things come in the way. Hopefully this was informative and helps you and people in the future choose one of these :) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#555 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABxCEmNoYPu4KpDx0MV3QQ_MZInjoXoeks5soq8FgaJpZM4PoWuS> .

[stickfigure]

I think you overestimate how quickly material-ui advances...

[deadcoder0904]

I also think my documentation is a bit easier to navigate and see live examples but that might be because I made it.

Nope. It is easier & concise.

Thank you for your hard work @mlaursen ❤️

The explanation was crystal clear.

Its so good that I didn't knew which one to choose of the two 😂

I'll leave this open if anyone wonders. Close it if u want.

[dandv]

Also,

• This library implements autocompletes, while Material-UI requires using 3rd party autocomplete libraries.
• This library implements editable tables, tables with dynamic content, and tables with menus. Material-ui does not.
• This library has a demo for an app bar with search field, while Material-UI does not.

On the other hand, Material-UI has a monetization strategy with Patreon backers and premium themes.

[nebrelbug]

I love how react-md is way simpler. With material-ui, you have to export withStyles() everything and it seems like nothing works without tons of extra styling.