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?
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.
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.
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.
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.
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?
I have used bulma in several projects. We could not customize with the websites very well. Also when we need "quick solutions" Bulma is not suitable (I mean basic animations, to-top buttons, transparent navbar solutions etc. For these solutions, you need extra js codes).
Everybody knows about Bootstrap (heavy but popular).
Now we start a new project with UI kit, I like it. Pros: It is fast and lightweight and imho it has very good UI. Cons: Small community. Documentation.
Check this link for kick-off. https://github.com/zzseba78/Kick-Off
Maybe it is helpful.
Been checking out Bulma, myself, and really dig it. I like that it's a great base level jumping off point. You can get a layout going with it, pretty quickly, and then customize as you want. It definitely sounds like it's the one you're leaning towards but a big factor would be who will be using it most? Your boss, yourself, others? Whichever you like best, you'll prob be most productive with but if in the end your boss says it has to be UIkit, then best to be open-minded and give it another shot. Sometimes you may not jive with new tools in your stack, at first, but then they can become tools you learn to love. Best to you in your decision! Take care & keep safe.
You can also check TailWindCss
I've moved away from the concept of UI kits. Not that many support CSS grid. A lot of the icons are easier to use in SVG. I've had success in the concept of design framework and design tokens. I build my brand identity in Figma, and extract in Diez. Then Diez integrates into React and SASS. Much easier because design is decoupled from software in a central authority, and software updates automatically from design changes.
Actually it really depends on your needs, there are 3 types of UI frameworks you can use:
A complete set of UI components like: https://react-bulma.dev/en/getting-started.
Having a lot of pre-built UI components saves a lot of time
need to learn the react framework and the bulma styles, and it's harder to customize to your needs
A pure css framework, like Bulma, where you write all the components yourself.
A lot of flexibility to build the components you need
You are bound to Bulma classes and markup.
Takes more time since you need to build the components
A utility class framework like: https://tailwindcss.com/.
Most flexible, mix and match classes as you like and build your own markup
Very easy to customize to your needs
Might take time to get used to and takes more time since you need to build the components
If you choose options one, then it's just a matter of deciding what style you like (material,ant, bulma) and go with the library that implements it If you go with pure css and build your own components, I can't recommend tailwind enough, I've been finding myself building entire pages without writing a single line of css.
And if later on, the designer wants to make a change to some color, or size, I just need to change one value in the config file, and the entire app is updated.
Ant Design offers the most components with JS and CSS taken care of. They look clean, professional, and usable.
We paired this with Bulma for making the containers and structure reactive. Bulma (for react) make it easy to just add a section, container, and content and have it work on all platforms.
We also use Geist UI, though not recognized by Stack share, for its simple and modern feel. Highly recommend Geist if you want modern components for complicated UI's
I replaced Bootstrap with Material-UI during the front-end UI development, because Material-UI adopts a component-based importing style, making it suit well in a "React programming style". This makes me comfortable when programming because I can treat importing UI components as other React components I define.
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.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Bootstrap?
What is Foundation for Apps?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Foundation for Apps?
Sign up to get full access to all the tool integrationsMake informed product decisions
We have been using it for the past 3 years and have no complaints
Good service with a good price, worth the money.
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.
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 use Semantic UI for our frotend. A heavily customised version of it, but still Semantic UI under the hood.
Used Semantic UI + Angular2 together with Spring or Node/Express for full stack web application development.