Ant Design vs Material-UI: What are the differences?
Ant Design: A set of high-quality React components. An enterprise-class UI design language and React-based implementation. Graceful UI components out of the box, base on React Component. A npm + webpack + babel + dora + dva development framework; Material-UI: React components for faster and easier web development. Build your own design system, or start with Material Design. React components for faster and easier web development. Build your own design system, or start with Material Design.
"Polished and enterprisey look and feel" is the primary reason why developers consider Ant Design over the competitors, whereas "React" was stated as the key factor in picking Material-UI.
Ant Design and Material-UI are both open source tools. It seems that Material-UI with 48.1K GitHub stars and 10.7K forks on GitHub has more adoption than Ant Design with 47.8K GitHub stars and 16.8K GitHub forks.
According to the StackShare community, Material-UI has a broader approval, being mentioned in 67 company stacks & 77 developers stacks; compared to Ant Design, which is listed in 22 company stacks and 33 developer stacks.
What is Ant Design?
What is Material-UI?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.
A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.
In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.
If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.
Really simple to install and works as you expect it to out of the box.
Ant Design has a lot of different components to choose from, and they looks fantastic. Very enterprise, very polished. This isn't Twitter Bootstrap.
A great thing about a lot of the components is that they take other React components as children. So you can nest, and mish-mash the content to your hearts content.
If you're building something, take a look at Ant Design - it may increase your output speed significantly and make your app not look "MVP".
Material UI provides Cloudcraft.co with a clean, professional looking and very easy to use set of UI components build with React. The few issues we've reported to the developers have been quickly fixed each time. I highly recommend using Material UI for both consumer and enterprise web apps. The styling system in particular is very nice to work with, and allows you to easily add your own brand's look and feel throughout the UI.
We like the pure simplicity of Google's Material UI. It is simply too much overhead today to design custom UI styles.
best practice standardization within the team on a very promising GUI standard design for client development