Material-UI vs Polymer: What are the differences?
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; Polymer: A new library built on top of Web Components, designed to leverage the evolving web platform on modern browsers. Polymer is a new type of library for the web, designed to leverage the existing browser infrastructure to provide the encapsulation and extendability currently only available in JS libraries. Polymer is based on a set of future technologies, including Shadow DOM, Custom Elements and Model Driven Views. Currently these technologies are implemented as polyfills or shims, but as browsers adopt these features natively, the platform code that drives Polymer evacipates, leaving only the value-adds.
Material-UI and Polymer can be categorized as "Front-End Frameworks" tools.
"React" is the primary reason why developers consider Material-UI over the competitors, whereas "Web components" was stated as the key factor in picking Polymer.
Material-UI and Polymer are both open source tools. It seems that Material-UI with 48.6K GitHub stars and 11K forks on GitHub has more adoption than Polymer with 21.1K GitHub stars and 2K GitHub forks.
DeveloperTown, Ratio, and Code Foundries are some of the popular companies that use Material-UI, whereas Polymer is used by AX Semantics, USERcycle, and Telemetry. Material-UI has a broader approval, being mentioned in 69 company stacks & 80 developers stacks; compared to Polymer, which is listed in 42 company stacks and 32 developer stacks.
What is Material-UI?
What is Polymer?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Polymer?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Polymer?
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.
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.
In process of Learning Technics- Studing to know more. I was introduced in a Google event.
Polymer is another Google offering that focuses on Web Components, an up-and-coming collection of technologies that provide web developers with the ability to create customer HTML elements.
Polymer is super future-focused and really great to build in. The biggest plus for us is how its component-focused approach keeps things modular and maintainable. It also makes it really easy to implement material design.
We like the pure simplicity of Google's Material UI. It is simply too much overhead today to design custom UI styles.