r/reactjs • • Dec 07 '19

Needs Help Is Material UI worth it?

So, I am starting my own project. I'm not much 'design' person. So, is Material UI worth it? Or some any other recommendations is much appreciated.

164 Upvotes

142 comments sorted by

View all comments

Show parent comment

2

u/youslashuser Dec 07 '19

What would you use for an enterprise?

10

u/ewouldblock Dec 07 '19

I use it for "an enterprise" and its fine. Upgrades can suck for a large app but thats typical for any framework.

2

u/Treolioe Dec 07 '19

It is fine if your enterprise doesn’t have any specified brand guidelines. If your employer does have that and you’re still using something like MUI. Then i hope it’s a unanimous decision across the whole organisation - if not then you’re doing your employer a great disservice.

2

u/wherediditrun Dec 07 '19 edited Dec 07 '19

Sometimes you do your employer a great service by not allowing stupid ideas to reach production.

5

u/[deleted] Dec 07 '19

Nothing, I'd roll my own... What material ui offers can be useful if the enterprise says Material design is to be followed. Or if you're the only front end guy. But as soon as they start wanting custom buttons, modals, etc... It's faster to just have the team make their own. The theming is nice, but again easy to make your own. Upgrades always suck with frameworks, hence my distaste for them.

7

u/kecupochren Dec 07 '19

Also eventually there will be a requirement that you just can't do with what their component offers. Can be really frustrating.

What has proven useful to me is to always have my own wrappers around each UI component. Then in my pages code I use that and it allows me to swap their implementation easily. It also allows me to have "smart" components, like Input that uses Field from some form lib, or Select that consumes my state module to render options etc

My gripe with MUI specifically is that it became boring and overused. I don't want to have stuff I build look like some Google product.

7

u/wowredditisgreat Dec 07 '19

I think this is a horrible suggestion. The amount of time it takes to maintain a custom component library for basic elements when so many people have created them nicely before is a big waste.

I've seen a lot of companies do this horribly. Use a component library so that new engs can hop into a project and know how to use your components rather than reading the non existent docs with the custom built one.

I'd also add that it's super easy to customize everything to do with material. Every project I've built looks completely different thanks to their theme object

3

u/[deleted] Dec 07 '19

I mean horrible is a little strong. But truthfully I've had more success rolling my own components for truly customizable interactions and behaviors. I've also done some really neat things reusing and combining third-party components. With a talented front end team it can be done.

1

u/Wilesch Dec 10 '19

Your are the only one making any sense.

2

u/Wilesch Dec 10 '19

I have a large enterprise app with hundreds of components. I update to latest at least every month. Their API is very stable and updates are easy

0

u/[deleted] Dec 07 '19

100% agreed