What is Vuetify and what are its top alternatives?
Top Alternatives to Vuetify
Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...
Bulma is a CSS framework based on Flexbox and built with Sass
Vuesax is a framework of components based on vue js, it is a framework that is designed from scratch to be incrementally adoptable. The framework is focused on facilitating the development of applications, improving the design of the same without removing the necessary functionality. we want all the components to be independent in colors, shapes and design for a freedom that we like all front-end but without losing the speed of creation and production. ...
- Bootstrap Vue
Build responsive, mobile-first projects on the web using Vue.js and the world's most popular front-end CSS library — Bootstrap V4. ...
It is not focused on Mobile development, mainly because it lacks responsiveness on mobile WebViews. ...
Element is a Vue 2.0 based component library for developers, designers and product managers, with a set of design resources. ...
Material UI is a library of React UI components that implements Google's Material Design. ...
Vuetify alternatives & related posts
- UI components1.2K
- Great docs779
- HTML, CSS, and JS framework472
- Open source411
- Widely used374
- HTML framework242
- Mobile first77
- Easy setup77
- Great grid system58
- Great community52
- Future compatibility38
- Very powerful foundational front-end framework28
- Build faster prototypes19
- Good for a person who hates CSS8
- Rapid development4
- Love it4
- Easy to setup and learn4
- Great and easy to use3
- Clean and quick frontend development2
- Provide angular wrapper2
- Great and easy2
- Powerful grid system, Rapid development, Customization2
- Great customer support2
- Great and easy to make a responsive website2
- Sprzedam opla2
- Easy to use2
- Not tied to jQuery1
- Design Agnostic1
- So clean and simple1
- Numerous components1
- Love the classes?1
- Felxible, comfortable, user-friendly1
- Pre-Defined components1
- The fame1
- Easy setup21
- Painless front end development1
- It's fast1
- Responsive design1
- Every site uses the defaults16
- Grid system break points aren't ideal15
- Too much heavy decoration in default look14
- Verbose styles8
- Super heavy1
related Bootstrap posts
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.
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! :)
For Etom, a side project. We wanted to test an idea for a future and bigger project.
What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.
You kind of need a map to work as a proxy between the software and Google Maps API.
We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.
Thanks to all the people behind Create React App it's easier to start any React application.
We also chose a module called Reactstrap which is Bootstrap UI in React components.
An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to
Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.
- Ease of integration into an existing project4
- Small and lightweight4
- Rich components1
- Not supported by a well known company2
related Buefy posts
- Easy setup11
- Easy-to-customize the sass build6
- Community-created themes6
- Great docs5
- Easy to learn and use4
- Not yet supporting Vue 32
related Bulma posts
I'm building, from scratch, a webapp. It's going to be a dashboard to check on our apps in New Relic and update the Apdex from the webapp. I have just chosen Next.js as our framework because we use React already, and after going through the tutorial, I just loved the latest changes they have implemented.
What do you think we should use? Maybe you have another suggestion?
- Fresh design compare to well known Material Design6
related Vuesax posts
- Open Source7
- ARIA Accessibility out of the box4
- Nuxt.js Integration3
- Customizable via SASS variables3
- Not tied to jQuery3
- Active development3
- Easily themable3
- Bootstrap v4.x3
related Bootstrap Vue posts
I'm migrating from pure Laravel with Bootstrap project to a kind of Laravel + Vue.js. Which one should I use for the UI?
We are considering bootstrap version 4. Still, which of these 3 should I choose? Pure bootstrap, Vuetify, or Bootstrap Vue?
- Avaliable for other frontend frameworks too6
related ElementUI posts
I just want to have a simple poll/vote...
If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:
1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.
2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.
Your advice would help a lot! Thanks in advance :)
- Very complete solution3
- Buggy in parts2
related Element posts
- Material Design80
- Ui components56
- CSS framework26
- Looks great13
- Good documentation10
- Open source7
- Ui component6
- Code examples6
- Supports old browsers out of the box3
- Very accessible3
- Designed for Server Side Rendering2
- Easy to work with1
- Hard to learn. Bad documentation30
- Hard to customize25
- Hard to understand Docs19
- Extra library needed for date/time pickers6
- Bad performance6
- For editable table component need to use material-table5
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.
My React website is a simple 5-pager that attaches to a database to store and display registrations and other data. The user (small user base) can change any form elements, but I don't need theme-ing, though that would be fun for the user. reactstrap/react-bootstrap built on Bootstrap 4 sounds dated. I am familiar with reactstrap, but a friend said to try Material-UI. The thought of learning it is interesting, but somehow I think it might be overkill. So... reactstrap, react-bootstrap, or Material UI, which should I use?