Need advice about which tool to choose?Ask the StackShare community!
What is Bootstrap?
What is Material-UI?
What is Materialize?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Bootstrap?
- Responsiveness1.5K
- UI components1.2K
- Consistent942
- Great docs763
- Flexible669
- Open source405
Why do developers choose Material-UI?
Why do developers choose Materialize?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Bootstrap?
What are the cons of using Material-UI?
What are the cons of using Materialize?
Sign up to add, upvote and see more consMake informed product decisions
What companies use Material-UI?
What companies use Materialize?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Bootstrap?
What tools integrate with Materialize?
Sign up to get full access to all the tool integrationsMake informed product decisions
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.
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.
I'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.

As 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.

As I've been applying Materialize, I've discovered some limitations.
The Glitter page: https://gitter.im/Dogfalo/materialize provided excellent support though. Kudos!
It is very easy to use. Very good community and documentation :P. Keep up the good work.

我们团队一直在使用bootstrap,非常简单易用,并且有帮助。支持也很到位,很喜欢!用了4年的时间,会持续的用下去,加油!!Bootstrap!!!
We have been using it for the past 3 years and have no complaints
Leanstack was on Bootstrap 2. Chose this because it is wildly popular, so it’s active, has been used a lot in production, and has a ton of features. Anything you need to do from a UI perspective, there’s likely a plugin for it already part of the library. Haven’t tried the others, but we're happy with BS.
For StackShare, we upgraded to Bootstrap 3. I don’t like that they changed the name of columns, essentially breaking the grid layout for Bootstrap 2 and below, so that was a real pain to update. I hope they don’t do that again. Once we have more bandwidth, we’re totally going to decouple our markup from Bootstrap.
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.
Bootstrap is a framework to help you design websites faster and easier. It includes HTML and CSS based design templates for typography, forms, buttons, tables, navigation, modals, image carousels, etc. It also gives you support for JavaScript plugins. Bootstrap's responsive CSS adjusts to phones, tablets, and desktops Bootstrap is compatible with all modern browsers (Chrome, Firefox, Internet Explorer, Safari, and Opera)
We started with a bootstrap based template and then completely rewrote it due to poor design of the template. Using boostrap properly was a great experience - once you learn it and use it properly, it's simple to use and very good at being responsive and adapting to the various screen view.
I simply bought a "job board" template for the website, which is written using Bootstrap 2. I'm hoping to upgrade the site to Boostrap 3 when I'll have a time.
Я просто купил шаблон для доски вакансий, написанный на Boostrap 2. Когда будет время перепишу все на Bootstrap 3.
With the advancement in CSS, Bootstrap is creating new milestones when it comes to minimising our CSS codes. So elegant and beautiful yet easy and convenient to use once you go through all the classes and its elements. In addition, its JS function is impressive too.
We like the pure simplicity of Google's Material UI. It is simply too much overhead today to design custom UI styles.