What is Material Design for Angular and what are its top alternatives?
Top Alternatives to Material Design for Angular
Material Design for Bootstrap
This Bootstrap theme is an easy way to use the new Material Design guidelines by Google in your Bootstrap 3 based application. Just include the theme right after the Bootstrap CSS and include the javascript at the end of your document, everything will be converted to Material Design (paper) style. ...
Material Design
Material Design is a unified system that combines theory, resources, and tools for crafting digital experiences. ...
Bootstrap
Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...
Animate.css
It is a bunch of cool, fun, and cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and general just-add-water-awesomeness. ...
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. ...
Material-UI
It is a comprehensive guide for visual, motion, and interaction design across platforms and devices. ...
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. ...
Semantic UI
Semantic empowers designers and developers by creating a shared vocabulary for UI. ...
Material Design for Angular alternatives & related posts
- Bootstrap16
- Light weight6
- Awesome and simple to use6
- Modern Looks4
- Google Material Design4
- Responsive4
- Open Source3
- Great angular compatibility3
- Not free for premo stuff2
related Material Design for Bootstrap posts
- They really set a new bar in design4
- An intuitive design3
- Simply, And Beautiful2
- Many great libraries2
- Composants0
- Sometimes, it can hang the browser1
related Material Design posts
I am a bit confused when to choose Bootstrap vs Material Design or Tailwind CSS, and why? I mean, in which kind of projects we can work with bootstrap/Material/Tailwind CSS? If the design is made up on the grid, we prefer bootstrap, and if flat design, then material design. Similarly, when do we choose tailwind CSS?
Any suggestion would be appreciated?
Bootstrap
- Responsiveness1.6K
- UI components1.2K
- Consistent945
- Great docs776
- Flexible677
- HTML, CSS, and JS framework466
- Open source410
- Widely used375
- Customizable368
- HTML framework241
- Popular76
- Mobile first75
- Easy setup75
- Great grid system56
- Great community49
- Future compatibility38
- Integration34
- Very powerful foundational front-end framework27
- Standard24
- Javascript plugins23
- Build faster prototypes19
- Preprocessors18
- Grids13
- Clean8
- Good for a person who hates CSS7
- Easy to setup and learn4
- Rapid development4
- Love it4
- Popularity2
- Community2
- Great and easy to make a responsive website2
- Sprzedam opla2
- Powerful grid system, Rapid development, Customization2
- Clean and quick frontend development2
- Easy to use2
- Great customer support2
- The fame1
- Easy setup21
- Painless front end development1
- So clean and simple1
- Numerous components1
- Material-ui1
- Geo1
- Boostrap1
- Pre-Defined components1
- Great and easy1
- It's fast1
- Reactjs1
- Great and easy to use1
- Responsive design1
- Design Agnostic1
- Provide angular wrapper1
- Recognizable1
- Intuitive1
- Love the classes?1
- Felxible, comfortable, user-friendly1
- Frefsd0
- Javascript is tied to jquery23
- Every site uses the defaults14
- Too much heavy decoration in default look11
- Grid system break points aren't ideal11
- Verbose styles7
related Bootstrap posts
Hello, I hope everyone is doing good and safe. I need advice on what to learn more, I have started learning HTML, CSS, Bootstrap, JavaScript, Node.js, ExpressJS, React. eventually will learn MongoDB too. I would like to be a Front End developer or full-stack developer. What else would be the suggestion to get a job and what things I need to focus more on as a fresher to make my skills better. Do I have to be good in Algorithms and Dynamic Programming to find a job for entry-level? Looking forward to hearing from you guys for suggestions.Â

























I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.
I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).
As per my work experience and knowledge, I have chosen the followings stacks to this mission.
UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.
Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.
Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.
Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.
Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.
Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.
Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.
Happy Coding! Suggestions are welcome! :)
Thanks, Ganesa
related Animate.css posts
- Responsive grid158
- Mobile first92
- Open source79
- Semantic75
- Customizable72
- Quick to prototype51
- Simple ui50
- Fast45
- Best practices44
- Easy setup39
- Neutral style6
- HTML, SCSS and JS6
- Professional5
- Accessibility support5
- Xy grid3
- Every new version is smaller, smarter & more efficient2
- Sass2
- Robust1
- Requires jQuery4
- Awful site4
related Foundation posts















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.
- React99
- Material Design67
- Ui components42
- CSS framework22
- Component16
- Looks great10
- LESS9
- Responsive9
- Open source6
- Good documentation6
- Code examples5
- Flexible5
- Ui component4
- JSS4
- Angular3
- Very accessible3
- Designed for Server Side Rendering2
- LADO2
- Supports old browsers out of the box2
- Fun2
- Interface1
- Asdasd1
- Easy to work with1
- 5550
- Hard to learn. Bad documentation22
- Hard to customize20
- Hard to understand Docs15
- For editable table component need to use material-table4
- Long Code4
- Bad performance4
- Extra library needed for date/time pickers4
related Material-UI posts
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.
Hi, I start building an admin dashboard with next.js and looking for a frontend framework ( components ready ). So I end up with Ant Design and Material-UI, but I never built a project with these two.
Here is a list of my requirements.
- Good documentation.
- easy CRUD ( date picker and date range picker bundled )
- built-in multi-lang feature or Great 3rd library support
- Admin dashboard template
- well code maintenance
Which is better for the long run?
- SSR35
- Automatic routes31
- Middleware19
- Hot code reloading18
- Static Websites15
- SPA15
- Easy setup, easy to use, great community, FRENCH TOUCH14
- Plugins13
- Code splitting for every page11
- Custom layouts9
- Automatic transpilation and bundling (with webpack and9
- Modules ecosystem7
- Easy setup6
- Vibrant and helpful community5
- Pages directory5
- Amazing Developer Experience4
- Bala7a1
related Nuxt.js posts
























Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:
- Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
- Vue Styleguidist as our style guide and pool of developed Vue.js components
- Vuetify as Material Component Framework (for fast app development)
- TypeScript as programming language
- Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
- ESLint, TSLint and Prettier for coding style and code analyzes
- Jest as testing framework
- Google Fonts and Font Awesome for typography and icon toolkit
- NativeScript-Vue for mobile development
The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:
- Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
- Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
- Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
- Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
- Large scaling. Vue.js can help to develop pretty large reusable templates.
- Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
Semantic UI
- Easy to use and looks elegant156
- Variety of components91
- Themes64
- Has out-of-the-box widgets i would actually use61
- Semantic, duh56
- Its the future44
- Open source42
- Very active development37
- Far less complicated structure31
- Gulp28
- Already has more features than bootstrap9
- Just compare it to Bootstrap and you'll be hooked8
- UI components7
- Clean and consistent markup model7
- Responsiveness6
- Elegant. clean. readable. maintainable4
- Because it is semantic :-D4
- Good-Looking4
- Great docs2
- Consistent2
- Is big and look really great, nothing like this2
- Modular and scalable2
- Jquery1
- Easy to use1
- Blends with reactjs1
- Outdated build tool (gulp 3))5
- HTML is not semantic (see list component)3
- Javascript is tied to jquery2
- Poor accessibility support2
related Semantic UI posts















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.