MaterialUI may be overkill for such a simple project, you're right. So I'm recommending both tools in this StackShare form.

But if it's planned to increase the project, consider migrating it to MUI in advance. Among its pros I can name: - brilliant TS support - all popular use cases covered - well documented - backed by sponsors == will live and be maintained

I recommend Material-UI for a couple reasons. 1. It’s very easy to throw MUI into React. You can essentially just import the components you need in place of yours. Effectively, for a button, for example, you can swap out <button for MUI’s <Button and you can be done if that’s all you want. Looks great, no hassle, and they have simple guides to help you make good UI decisions on top of that. 2. It’s pretty up-to-date, and it has great docs. I use MUI all the time, and if I were doing a simple, small user-base app, I would definitely use it for the sake of convenience and speed of development.

I've used material UI and had great success with it on React projects. Semantic UI is also another great option https://semantic-ui.com/.

When you say its "overkill", I would think long term. I do a lot of small projects not only for the purpose of the project, but also for learning, future projects and to use professionaly. It's a long-term investment.

Material-UI looks great and is easy to use. Highly recommended, my favourite UI framework for React.

Much more modern in terms on support for css in js. But go for v5 not v4 as material-ui is going through a transition in term of its own implementation

Material-UI is the good choice for a small project. It's fast for development, maintenance, and is ready to use. It HaveMaterial-UI is the good choice for a small project. It's fast for development, maintenance, and is ready to use. Has an excellent documentation with pratic examples.

Chakra UI seems like the perfect fit in my opinion. It has a much powerful design system, all the necessary components and it is dead simple to learn. And pretty easy to customize too.

It's totally the design decision if you like to follow bootstrap design then you should go for reactstrap. But if you want to follow google material design then you should go for material ui.

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.

Hi Ashish,

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.

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.

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.

Honestly - pick whatever you are the most comfortable with. You can achieve almost the same effects with different tools, so why not use something I like using?

Actually it really depends on your needs, there are 3 types of UI frameworks you can use:

1. A complete set of UI components like: https://react-bulma.dev/en/getting-started.

   Pros:

   Having a lot of pre-built UI components saves a lot of time

   Cons:

   need to learn the react framework and the bulma styles, and it's harder to customize to your needs

2. A pure css framework, like Bulma, where you write all the components yourself.

   Pros:

   A lot of flexibility to build the components you need

   Cons:

   You are bound to Bulma classes and markup.

   Takes more time since you need to build the components

3. A utility class framework like: https://tailwindcss.com/.

Pros:

Most flexible, mix and match classes as you like and build your own markup

Very easy to customize to your needs

Cons:

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.

I used UIKit and Bootstrap many times. I love Bootstrap for fast, easy layouts to web apps. Clean code, easiest and fastest way to write layouts for front end if you learned something before about Bootstrap. Now in React I use React-Boostrap too. About UIKit I can say its nice idea. It's easier than Bootstrap. This is good option for trainee developer to learn how u should create layout of your website, but for me UIKit have not enough functions. If you need to create something complicated, u have an error in your mind. You must create amazing code combinations for UIKit where in Bootstrap in the same ideas you have easy solutions.

Hey Sai, My thoughts on UIkit - It's beautiful, 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 .

Now, considering Tailwind, it's seen as a classic, simple-to-set-up tool with 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. Tailwind allows you to build unique design elements, offering you a level of customization that may be unmatched by the other frameworks.

My final thoughts.

If you have the time , setup and use tailwind it will give you a great chance when it comes to customization and performance.

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.