Need advice about which tool to choose?Ask the StackShare community!
Materialize vs Semantic UI: What are the differences?
Materialize: A modern responsive front-end framework based on Material Design. A CSS Framework based on material design; 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.
Materialize and Semantic UI can be primarily classified as "Front-End Frameworks" tools.
Some of the features offered by Materialize are:
- Speeds up development
- User Experience Focused
- Easy to work with
On the other hand, Semantic UI provides the following key features:
- Build Responsive Layouts Easier
- Self Explanatory
- Tag ambivalent
"Google material design", "Responsive" and "Easy to use" are the key factors why developers consider Materialize; whereas "Easy to use and looks elegant", "Variety of components" and "Themes" are the primary reasons why Semantic UI is favored.
Materialize and Semantic UI are both open source tools. It seems that Semantic UI with 45.7K GitHub stars and 4.83K forks on GitHub has more adoption than Materialize with 36K GitHub stars and 4.79K GitHub forks.
Snapchat, Create.It, and Reviewable are some of the popular companies that use Semantic UI, whereas Materialize is used by The3ballsoft, GeoLytix, and Avhana Health. Semantic UI has a broader approval, being mentioned in 77 company stacks & 50 developers stacks; compared to Materialize, which is listed in 46 company stacks and 53 developer stacks.
What is Materialize?
What is Semantic UI?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Materialize?
Why do developers choose Semantic UI?
- Themes56
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Materialize?
What are the cons of using Semantic UI?
What companies use Materialize?
What companies use Semantic UI?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Materialize?
What tools integrate with Semantic UI?
Sign up to get full access to all the tool integrationsMake informed product decisions
ReactQL
ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.
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.
styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <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.
MaterializeI've been using materialize and I'm really happy with it, in some months I'm sure it will become one of the best front-end frameworks around the internet, because it's easy and fast to use and to get started with it.
It also got a nice community of developers that help developing it and finding bugs, as well a translation team, looking to get materialize into the major countries.
My final review is that is one of the best front-end frameworks I've ever found and get used really fast and it's one of the most comfortable frameworks to use as well.
MaterializeAs I've been applying Materialize, I've discovered some limitations.
For example, the tabs require ids for the content divs. This makes is difficult to create content dynamically.
The documentation is not accurate.
To use materializecss, you will need to review the source code often.
MaterializeAs I've been applying Materialize, I've discovered some limitations.
The Glitter page: https://gitter.im/Dogfalo/materialize provided excellent support though. Kudos!
MaterializeIt is very easy to use. Very good community and documentation :P. Keep up the good work.
Semantic UIWe use Semantic UI for our frotend. A heavily customised version of it, but still Semantic UI under the hood.
Semantic UIUsed Semantic UI + Angular2 together with Spring or Node/Express for full stack web application development.
Semantic UIWe haven't yet, but we would like to integrate into our Web App.
Semantic UIIt's pretty. Used it once for MDST.
Materialize부트스트랩은 너무 흔해서 적당히 흔하고 좋은거 찾다가 발견
Semantic UIGrid, widgets, theming.