Need advice about which tool to choose?Ask the StackShare community!
Tailwind CSS vs Vuetify: What are the differences?
What is Tailwind CSS? A utility-first CSS framework for rapid UI development. Tailwind is different from frameworks like Bootstrap, Foundation, or Bulma in that it's not a UI kit. It doesn't have a default theme, and there are no build-in UI components. It comes with a menu of predesigned widgets to build your site with, but doesn't impose design decisions that are difficult to undo.
What is Vuetify? Material Component Framework for VueJS 2. 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.
Tailwind CSS and Vuetify can be categorized as "Front-End Frameworks" tools.
"Highly customizable" is the primary reason why developers consider Tailwind CSS over the competitors, whereas "Wide range of components and active development" was stated as the key factor in picking Vuetify.
Tailwind CSS and Vuetify are both open source tools. It seems that Vuetify with 20K GitHub stars and 2.32K forks on GitHub has more adoption than Tailwind CSS with 12.9K GitHub stars and 586 GitHub forks.
According to the StackShare community, Vuetify has a broader approval, being mentioned in 37 company stacks & 36 developers stacks; compared to Tailwind CSS, which is listed in 11 company stacks and 19 developer stacks.
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?
I don't know about material design.
You would go with Bootstrap if you want to prototype / build something without bothering about the design at all and you are OK if everything looks kinda template-y, using bootstrap out of the box components.
Go with Tailwind if you need a sleek design, a user interface where building with components will be important (because tailwind strongly favors component-based UI), and you know you will need to extend the built-in classes with your own (because tailwind is very easy to extend)
I would personally recommend tailwind over bootstrap any day of the week.
If you need minimal work to be done from your end and like most of the components / design available out of the box - go with Bootstrap. This is the oldest and has the widest adoption and a whole range of components built out by others.
If you like Material design, this is a good choice too. Please note that Bootstrap also has a Material theme, though it is not as native.
Both of these above frameworks are bulky and has more than what you may need.
If you like to build micro-components in a elegant way, TailwindCSS is the way to go.
Tailwind is great you don't have to mess with naming things and it is so much more flexible than the cookie cutter bootstrap, but I don't know about material UI. I recommend tailwind it's super simple to learn and has great code snippets.
Put simply, you should use Tailwind regardless. It is a great addition to whatever you use because it removes the hassle of writing CSS.
I am planning to redesign my entire application, which is currently in Bootstrap. I heard about Tailwind CSS, and I think its really cool to work with. Is it okay if I use Bootstrap and Tailwind together? I can't remove Bootstrap altogether, as my application is using the js dependencies of Bootstrap, which I don't want to disturb.
Factually talking about systems, we gotta make two bold headlines about each one: Bootstrap has been around for a while, has a vast community and much probably will not be gone in a while. Tailwind in the other hand, is the trendy framework starting from the past year. Referring to UI, I really prefer Tailwind, however I can't ignore the fact that a lot of libraries that emerged felt short in the end after a few years (a point where Bootstrap kept his status).
You are able to use both them together but I advise you — it will be a mess. And you gotta hope that you won't have any kind of conflicts between class naming and other general styling.
My recommendation would be to use one and only one. Perhaps rebuild the UI with a specific framework in mind, otherwise you will start to workaround things of both frameworks to contradict each other - and your team (if you work with one) will hate you.
You might have heard about bootstrap 5. Bootstrap is now totally jQuery free. i have tried foundation and bulma too. but eventually fall again for bootstrap, as it is most convenient and stable. i use bootstrap with less or sass.
I use both of these regularly. If you're going to have to use Bootstrap due to your js dependencies, stick with Bootstrap. I actually prefer Tailwind, but trying to use both of them and make them "play nice" feels like making things more complex with no real benefit.
EDIT: Sorry for the late response, I just noticed how old this is. StackShare sent me this in an email for some reason so I assumed it was relatively fresh.
We are re-modifying the existing portal to the new one. Looking out for a CSS framework where over-rides are possible, the performance of page loading, extendable, etc Please suggest between tailwind, UIkit and bootstrap frameworks explaining in detail on different factors. I request your help on the same.
I'm a big proponent of Tailwind and I personally use it whenever I get the chance, mostly because it's not really a UI-kit, but it sounds like in this case a UI-kit like Bootstrap with pre-defined components is more what you are looking for. Bootstrap is (relatively) extendable and overridable and makes it really simple to make a decent looking UI using a handful of pre-defined classes, whereas with Tailwind you configure the classes and create your own components. My main reason for replacing Bootstrap in my workflow is that it feels like the component creation has become so abstracted from the developer that any meaningful customization becomes a chore, resulting in many websites having the generic "Bootstrap-look". Nonetheless, it is effective for creating a pleasant and responsive UI. Though, I don't have any experience with UIkit.
Hey Sai, My thoughts on UIkit - It's beautiful, it's fast and it has good animation too. Why would I choose it ? Nothing other than giving the internet a new look .
My thoughts on Bootstrap - it's beautiful, if used well. It's very fast and has clean class naming convention unlike Uikit.
Why I would choose it ? It's been tested and trusted, I can find a whole lot of resources and a community around it. Also with the type of project you working on I bet Bootstrap would do the job .
My thoughts on tailwind - classic, difficult to set up and clean utilities. I wouldn't think of tailwind the way I would to Bootstrap or UIkit. What do I mean ? Tailwind is more like a tool set to create your own design flow rather than giving you a pre-designed button it gives you the ability to design yours.
My final thoughts.
If you have the time , setup and use tailwind it will give you a great chance when it comes to extending and performance.
As our team will be building a web application,
CSS3 are one of the standardized combinations to implement the structure and the styling of a webpage.
Material-UI comes with all sorts of predesigned web components such as buttons and dropdowns that will save us tons of development time. Since it is a component library designed for React, it suits our needs. However, we do acknowledge that predesigned components may sometimes cause pains especially when it comes to custom styling. To make our life even easier, we also adopted
Tailwind CSS. It is a CSS framework providing low-level utility classes that will act as building blocks when we create custom designs.
I do prefer to write things from scratch however when it came to wanting to jump-start the frontend, I found that it was taking me a lot longer hence why needing to use something very fast.
Bootstrap was the boom when it came out, I didn't like it, to be honest, set in its way and a pain to over-ride and in addition, you can tell from a distance if you're using boostrap and as everything looks the same.
I came across Tailwind CSS as I wanted more dynamic features, you could say, I've been now doing it for a few days and I love it a lot. I've been practising with the full stack part installed but I an't we wait until I do a new project, and I'll e able to select exactly what I want. Much faster.
Pros of Tailwind CSS
- Highly customizable42
- Quick setup31
- Utility first styles, its amazing29
- Great docs22
- Very light11
- Open source11
- Easy Tree shaking with Tailwind CLI1
Pros of Vuetify
- Enables beauty for graphically challenged devs29
- Wide range of components and active development23
- New age components18
- Easy integration13
- Material Design11
- Open Source10
- Awesome Documentation6
- Not tied to jQuery5
- Awesome Component collection5
- Best use of vue slots you'll ever see4
- Not tied to jQuery2
- Active Community2
Sign up to add or upvote prosMake informed product decisions
Cons of Tailwind CSS
- Cluttered html structure5
Cons of Vuetify
- It is heavy19
- Not Vue 3 Ready (Alpha-Version)3