Material UI vs Polymer

Overview

Material-UI

Stacks2.7K

Followers3.7K

Votes445

Polymer

Stacks557

Followers463

Votes122

GitHub Stars22.1K

Forks2.0K

Material UI vs Polymer: What are the differences?

## Introduction

Key differences between Material UI and Polymer are outlined below.

1. **Design Philosophy**: Material UI follows Google's Material Design principles, focusing on creating clean, modern interfaces with consistent spacing and typography. In contrast, Polymer provides a set of web components for building elements with reusable code, enabling developers to create custom designs.
   
2. **Bundle Size**: Material UI tends to have a larger bundle size due to the extensive set of pre-built components it offers. On the other hand, Polymer's bundle size is generally smaller since it focuses on providing the building blocks for developers to create their own components as needed.

3. **Dependency Management**: Material UI is often used with React, a JavaScript library for building user interfaces, which can lead to additional dependencies in projects. In comparison, Polymer offers a more standalone approach with its web components, reducing the number of external dependencies required.

4. **Community Support**: Material UI has a larger and more active community compared to Polymer, resulting in frequent updates, bug fixes, and a wider range of resources and tutorials available. Polymer, while still backed by Google, may have a smaller community and fewer resources for support.

5. **Browser Support**: Material UI aims to provide consistent user experiences across different browsers by handling compatibility issues internally. In contrast, Polymer relies on web standards and may require additional polyfills or workarounds to ensure compatibility with older browsers.

6. **Customizability**: Material UI offers a high level of customization through theming and styling options, allowing developers to tailor the look and feel of components to suit their design needs. Polymer, while customizable, may require more effort in creating custom styles, as it focuses on providing the basic building blocks for components.

In Summary, the key differences between Material UI and Polymer encompass design philosophy, bundle size, dependency management, community support, browser support, and customizability.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Material-UI, Polymer

Kexin

Mar 4, 2021

Decided

I replaced Bootstrap with Material-UI during the front-end UI development, because Material-UI adopts a component-based importing style, making it suit well in a "React programming style". This makes me comfortable when programming because I can treat importing UI components as other React components I define.

281k views281k

Comments

Kabir

Nov 29, 2021

Review

I don't recommend that you use Vue but that is just my biased opinion for react against vue. If you want a better user experience, use Next.js server side rendering. You will need to use Web Assembly to compile your unity 3d game on the web. DO NOT use html, css and js for your game. I recommend you use a tailwind UI kit, Chakra UI or material UI.

16.2k views16.2k

Comments

Gericke

Jul 27, 2020

Needs adviceon

.NET Core

JavaScript

React

Hi,

I am looking into solutions for reusable components for an existing #MVC project which is build on .NET Core. Currently some functionality is being reuses via JavaScript. I have React experience so I know I can create React components and then reference it on the MVC app. The only problem is I do not know the full extent of it as the current app uses a lot of 3rd party libraries, not sure how that will effect React components. I am currently looking into WebComponents which is also another way for creating reusable components and it is compatible with any JavaScript library based on what I have seen on the website. Also to take in consideration that it should cause a re-write of the system.

So my question is, to future-proof reusable components, which will be best React or Web Components? And which will be more reliable to use with 3rd party libraries?

49.1k views49.1k

Comments

Detailed Comparison

Material-UI	Polymer
Material UI is a library of React UI components that implements Google's Material Design.	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.
Tables; Forms; Snackbars; Buttons; Theming	-
Statistics
GitHub Stars -	GitHub Stars 22.1K
GitHub Forks -	GitHub Forks 2.0K
Stacks 2.7K	Stacks 557
Followers 3.7K	Followers 463
Votes 445	Votes 122
Pros & Cons
Pros 141 React 82 Material Design 60 Ui components 30 CSS framework 26 Component Cons 36 Hard to learn. Bad documentation 29 Hard to customize 22 Hard to understand Docs 9 Bad performance 7 For editable table component need to use material-table	Pros 52 Web components 30 Material design 14 HTML 13 Components 5 Open source Cons 1 Last version is like 2 years ago? that's totally rad
Integrations
React Emotion Next.js styled-components Node.js	No integrations available

What are some alternatives to Material-UI, Polymer?

Bootstrap

Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web.

Foundation

Foundation is the most advanced responsive front-end framework in the world. You can quickly prototype and build sites or apps that work on any kind of device with Foundation, which includes layout constructs (like a fully responsive grid), elements and best practices.

Semantic UI

Semantic empowers designers and developers by creating a shared vocabulary for UI.

Materialize

A CSS Framework based on material design.

Material Design for Angular

Material Design is a specification for a unified system of visual, motion, and interaction design that adapts across different devices. Our goal is to deliver a lean, lightweight set of AngularJS-native UI elements that implement the material design system for use in Angular SPAs.

Blazor

Blazor is a .NET web framework that runs in any browser. You author Blazor apps using C#/Razor and HTML.

Quasar Framework

Build responsive Single Page Apps, SSR Apps, PWAs, Hybrid Mobile Apps and Electron Apps, all using the same codebase!, powered with Vue.

Nuxt.js

Nuxt.js presets all the configuration needed to make your development of a Vue.js application enjoyable. You can use Nuxt.js for SSR, SPA, Static Generated, PWA and more.

UIkIt

UIkit gives you a comprehensive collection of HTML, CSS, and JS components which is simple to use, easy to customize and extendable.

Tailwind CSS

Tailwind is different from frameworks like Bootstrap, Foundation, or Bulma in that it's not a UI kit. It doesn't have a default theme, and there are no build-in UI components. It comes with a menu of predesigned widgets to build your site with, but doesn't impose design decisions that are difficult to undo.

Related Comparisons

Material UI vs Polymer: What are the differences?

## Introduction

Key differences between Material UI and Polymer are outlined below.

1. **Design Philosophy**: Material UI follows Google's Material Design principles, focusing on creating clean, modern interfaces with consistent spacing and typography. In contrast, Polymer provides a set of web components for building elements with reusable code, enabling developers to create custom designs.
   
2. **Bundle Size**: Material UI tends to have a larger bundle size due to the extensive set of pre-built components it offers. On the other hand, Polymer's bundle size is generally smaller since it focuses on providing the building blocks for developers to create their own components as needed.

3. **Dependency Management**: Material UI is often used with React, a JavaScript library for building user interfaces, which can lead to additional dependencies in projects. In comparison, Polymer offers a more standalone approach with its web components, reducing the number of external dependencies required.

4. **Community Support**: Material UI has a larger and more active community compared to Polymer, resulting in frequent updates, bug fixes, and a wider range of resources and tutorials available. Polymer, while still backed by Google, may have a smaller community and fewer resources for support.

5. **Browser Support**: Material UI aims to provide consistent user experiences across different browsers by handling compatibility issues internally. In contrast, Polymer relies on web standards and may require additional polyfills or workarounds to ensure compatibility with older browsers.

6. **Customizability**: Material UI offers a high level of customization through theming and styling options, allowing developers to tailor the look and feel of components to suit their design needs. Polymer, while customizable, may require more effort in creating custom styles, as it focuses on providing the basic building blocks for components.

In Summary, the key differences between Material UI and Polymer encompass design philosophy, bundle size, dependency management, community support, browser support, and customizability.

Material UI vs Polymer

Overview