What is Bootstrap Vue and what are its top alternatives?
Top Alternatives to Bootstrap Vue
Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...
Vuetify is a component framework for Vue.js 2. It aims to provide clean, semantic and reusable components that make building your application a breeze. Vuetify utilizes Google's Material Design design pattern, taking cues from other popular frameworks such as Materialize.css, Material Design Lite, Semantic UI and Bootstrap 4. ...
It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. ...
It is not focused on Mobile development, mainly because it lacks responsiveness on mobile WebViews. ...
Bootstrap components built with Vue.js
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. ...
Material Design for Angular
Material Design is a specification for a unified system of visual, motion, and interaction design that adapts across different devices. Our goal is to deliver a lean, lightweight set of AngularJS-native UI elements that implement the material design system for use in Angular SPAs. ...
MUI (formerly Material-UI) is the React UI library you always wanted. Follow your own design system, or start with Material Design. ...
Bootstrap Vue alternatives & related posts
- UI components1.2K
- Great docs778
- HTML, CSS, and JS framework466
- Open source411
- Widely used375
- HTML framework241
- Easy setup76
- Mobile first75
- Great grid system56
- Great community50
- Future compatibility38
- Very powerful foundational front-end framework28
- Build faster prototypes19
- Good for a person who hates CSS7
- Easy to setup and learn4
- Rapid development4
- Love it4
- Great and easy to use3
- Great and easy2
- Provide angular wrapper2
- Powerful grid system, Rapid development, Customization2
- Great customer support2
- Clean and quick frontend development2
- Easy to use2
- Great and easy to make a responsive website2
- Sprzedam opla2
- It's fast1
- Pre-Defined components1
- Not tied to jQuery1
- Responsive design1
- Design Agnostic1
- Love the classes?1
- Felxible, comfortable, user-friendly1
- The fame1
- Easy setup21
- Painless front end development1
- So clean and simple1
- Numerous components1
- 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.
- Enables beauty for graphically challenged devs26
- Wide range of components and active development22
- New age components15
- Easy integration12
- Material Design10
- Open Source9
- Awesome Documentation5
- Not tied to jQuery5
- Awesome Component collection4
- Best use of vue slots you'll ever see3
- Not tied to jQuery2
- It is heavy18
related Vuetify posts
Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:
- 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.
I'm building most projects using: Server: either Fastify (all projects going forward) or ExpressJS on Node.js (existing, previously) on the server side, and Client app: either Vuetify (currently) or Quasar Framework (going forward) on Vue.js with vuex on Electron for the UI to deliver both web-based and desktop applications for multiple platforms.
The direct support for Android and iOS in Quasar Framework will make it my go-to client UI platform for any new client-side or web work. On the server, I'll probably use Fastly for all my server work, unless I get into Go more in the future.
Update: The mobile support in Quasar is not a sufficiently compelling reason to move me from Vuetify. I have decided to stick with Vuetify for a UI for Vue, as it is richer in components and enables a really great-looking professional result. For mobile platforms, I will just use Cordova to wrap the Vue+Vuetify app for mobile, and Electron to wrap it for desktop platforms.
- Simple and easy to start with275
- Good documentation216
- Simple the best123
- Simplified AngularJS95
- Intuitive APIs69
- Changed my front end coding life45
- Configuration is smooth40
- Easy to learn28
- So much fun to use25
- Virtual dom17
- Faster than bulldogs on hot tarmac13
- It's magic9
- Best of Both Worlds8
- Without misleading licenses7
- Application structure7
- Elegant design7
- Intuitive and easy to use6
- Light Weight5
- Easy to integrate to HTML by inline-templates4
- Good command line interface4
- Small learning curve3
- Like Angular only quicker to get started with3
- Customer Render ending eg to HTML3
- One-way data flow2
- Single file components2
- Lots of documentation2
- Component based2
- Bridge from Web Development to JS Development2
- Concise error messages2
- Logicless templates2
- Supports several template languages2
- High performance2
- Less Common Place6
- YXMLvsHTML Markup3
- Don't support fragments1
- Only support programatically multiple root nodes1
related Vue.js posts
I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.
It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.
I find using Vue.js to be easier (more concise / less boilerplate) and more intuitive than writing React. However, there are a lot more readily available React components that I can just plug into my projects. I'm debating whether to use Vue.js or React for an upcoming project that I'm going to use to help teach a friend how to build an interactive frontend. Which would you recommend I use?
- Avaliable for other frontend frameworks too3
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 :)
- Bootstrap v3.x1
- Easy setup1
- No longer maintained1
- No disable option for datepicker1
- Limited styling1
related VueStrap posts
related Animate.css posts
- Ui components119
- Backed by google62
- Backed by angular51
- Open source34
- Easy to learn31
- Quick to develop28
- Easy to start8
- Flexbox Layouts4
- Great community3
- I like its design3
- Great extensions2
- It's the best looking out of the box1
- Seamless integration with AngularJS but lack of docs1
- Progressive Web Apps - to learn0
- No practical examples4
related Material Design for Angular posts
- Material Design76
- Ui components48
- CSS framework25
- Looks great12
- Good documentation10
- Open source7
- Code examples6
- Ui component5
- Supports old browsers out of the box3
- Very accessible3
- Designed for Server Side Rendering2
- Easy to work with1
- Barev Arman1
- Hard to learn. Bad documentation27
- Hard to customize22
- Hard to understand Docs18
- Bad performance6
- Extra library needed for date/time pickers5
- For editable table component need to use material-table5
- Long Code5
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?