Material-UI vs Semantic UI: What are the differences?
What is 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.
What is Semantic UI? A UI Component library implemented using a set of specifications designed around natural language. Semantic empowers designers and developers by creating a shared vocabulary for UI.
Material-UI and Semantic UI belong to "Front-End Frameworks" category of the tech stack.
"React" is the primary reason why developers consider Material-UI over the competitors, whereas "Easy to use and looks elegant" was stated as the key factor in picking Semantic UI.
Material-UI and Semantic UI are both open source tools. Material-UI with 48.1K GitHub stars and 10.7K forks on GitHub appears to be more popular than Semantic UI with 45.7K GitHub stars and 4.83K GitHub forks.
According to the StackShare community, Material-UI has a broader approval, being mentioned in 67 company stacks & 77 developers stacks; compared to Semantic UI, which is listed in 77 company stacks and 50 developer stacks.
What is Material-UI?
What is Semantic UI?
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 Semantic UI?
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
ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling
import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.
React Helmet was chosen to handle
<head> content, because it works universally, making it easy to throw back the correct
<title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.
<style> tags when using #StyledComponents.
React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.
Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.
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.
We like the pure simplicity of Google's Material UI. It is simply too much overhead today to design custom UI styles.
We use Semantic UI for our frotend. A heavily customised version of it, but still Semantic UI under the hood.
Used Semantic UI + Angular2 together with Spring or Node/Express for full stack web application development.