People have been asking this question forever since Bootstrap just came out and with every other CSS framework, sense it.

So today I'm gonna break down this question and answer once and for all, whether you should be using bootstrap or not.

Well, welcome back, toe webbed.

A simplified.

My name's Kyle, and my job is to simplify the Web for you so you can start building your dream project sooner.

So that sounds interesting.

Make sure you subscribe to the channel for more videos just like this, not to get started.

I want to break down a little bit what bootstrap is, since some people who maybe never heard of it.

And bootstrap is just a CSS framework.

Anesthesia says Framework is just a collection of different CSS styles that have been all brought together into a style sheet that you can import into your project lots of times.

They have styles for buttons, drop down menus.

They have styles for grids, rose forms, all these common things that you use in your application.

These frameworks air going to include, and they're going to also include a bunch of things you probably will never use such a scare cells, for example.

But it has just a bunch of features in it to make working with styling things so easy, and you don't really need to know CSS In order to use these frameworks, you just need to know the framework.

So now that you know what bootstrap is, should you actually be using boot strap on your project?

And unfortunately, it's not a very easy yes or no question that actual depends on quite a few things.

And the first thing that you should ask yourself is what your project is.

Four.

Is this a project that's for a really cool front and design that you're working on?

Or maybe you're just doing a simple front end to go along with a really complex back in that does a lot of cool things compiling data.

Or maybe you're working for a project for a client that needs to have a really cool front end thes different questions are going to determine whether or not you use boot shop or not.

In the first example, I said, if you're making a really cool, unique front end with a lot of cool, you, I and you ex designs.

Bootstrap is a terrible idea.

You're gonna spend more time working against Bootstrap trying to make it look like you wanted to, rather than actually using it for the things that helps you with.

But like I said in my second example, if you're just making a really simple front end site with a really complex back end, and you don't care so much about how the front end looks, you just wanted to look good enough and function then Bootstrap is great for you because you don't have to spend a bunch of time working with CSS and styling.

You just throw in some bootstrap classes and it just works.

And you're not gonna really tweak the Stein way too much.

So you don't have to worry about messing with bootstrap and trying to make it look like you want, because you're just gonna use the bootstrap styles and it's going to work how you want it to.

Another thing you need to consider is the timeline of your project.

If you're working for a client Burke company, lots of times, you're gonna have a deadline set on you when your project needs to be finished by And if it's a short deadline and the U I doesn't matter too much, it just has to be good enough then.

Bootstrap is probably a great option for you, because while I am not a huge fan of bootstrap myself, it's gonna save you tons of time by just throwing bootstrap into your project, putting in the classes that bootstrap gives you and just having a functional you.

Why?

Because without that, you have to manually create all of your own styles.

And while you'll probably get a better looking result in the end, it's time consuming.

And it's not as easy as just throwing in the bootstrap classes.

So if you have a very short time frame or you're constantly changing your product so your product goes through lots of it orations, it's constantly changing.

Using bootstrap is great for getting up and running with those changes, but if you have a longer timeframe or your project doesn't change as much, maybe you're not in a startup situation.

Then doing your own CSS is gonna be great because it gives you more control and it's going to look better in the end, even though it's gonna take a little bit longer.

Another thing to consider is why you're building project.

So, for example, if you're doing this project to learn which a lot of you I'm sure doing, and it's a great way to learn.

If you're building a project toe learn and your main focus of learning is on.

Know Js, for example, something on the back end, then sure used bootstrap.

Go right ahead.

You don't need to worry about the styling because you're focusing on learning the back end.

So if you're focusing on learning the back end, you shouldn't make yourself struggled through all the CSS required to make a good looking front end.

But if your focus is on learning front and technologies were groaning, CSS, then bootstrap is a terrible idea.

If you want to learn CSS, don't use bootstrap.

It's going to make it hard to learn CSS because you have to learn bootstrap CSS, which is so much different than just normal.

CSS.

And it makes you do so many extra things toe work around bootstrap.

So if you're doing this project toe, learn CSS toe, learn how to style to learn how to design, definitely, definitely do not use any CSS framework and go from scratch with your own CSS.

Now, most of these are pretty self explanatory reasons to use or not use the CSS framer.

But something many people forget about is what parts of the framework you're gonna be using.

For example, if you're just using bootstrap for the grid system, the rows and columns, you'd be much better off just using flex box and CSS cred to make your own custom styles.

It's gonna be easier than using bootstrap, because you can make it exactly like you wanted to.

And it's not gonna bring all the bloat of bootstrap, since if you'd use bootstrap, you have to download all the booze.

Draft CSS.

If you make your own grids, all you have to do is download.

Just do a little bit of CSS that makes that grid, so if you're doing just that really simple CSS grid and that's all you're using bootstrap for Make your own grid.

It's so much easier with CSS cred, and it's gonna look a lot better also, if you're only using bootstrap for the buttons, maybe, or the colors, or maybe even the table thes air things that are not that hard to make on their own.

So if you only need a few parts of bootstrap such as these buttons and grid or the buttons table in grid, you'd be better off just spending a couple hours making your own system unique to your specific use case.

So you don't have to worry about working around bootstrap, and in the long run, it's gonna save you time, which is great.

But if you want all of bootstrap, all the buttons, all the colors, all the tables, all the classes, although alerts all the headers, everything that bootstrap has and you're okay with your sight having that bootstrapped look, then definitely go a bootstrap.

It's just gonna make it easy for you to get started with.

Later.

You can change out Boonstra and use your own style is if you want, it's gonna be a little difficult and cumbersome, but it is possible to take out bootstrap and put in your own styles.

But I recommend generally, if your plan in the long run is to use your own styles and your own custom.

Look, just start with your own styles because then you don't have to go through the struggle of removing bootstrap and then implant in all of your own styles over top of it.

It's not a fun process.

Trusted.

The last thing to consider when thinking about whether you want to use bootstrap or not is going to be the job.

A script portion of bootstrap.

Now many of you may not realize, but Bootstrap has a lot of JavaScript components.

They have Accordions, collapsed toggles.

They have pop ups, drop down to all these different things, use JavaScript and behind the scenes there, using J Query.

And now you may love or hate J.

Crew.

It doesn't really matter, but in the end, Jake worries fairly large library to download and install inside of your application.

Also, if you're doing something with like react, for example, or a front and framework, J.

Quarry and react don't play very nicely together.

It's a real pain to use them together, so having to support bootstrap and react at the same time is just not fun, in my opinion, and I'd recommend not going with bootstrap if you're gonna be doing heavy front end work or utilizing these JavaScript components of bootstrap with a framework like react Now if your application is fairly light on front and JavaScript than having these extra components is great because you don't have to do the work to make these drop downs or collapsed menus.

It was built in there for you, and it works.

So that's a really nice thing with Bootstrap.

But obs are.

If you're watching this channel, you probably enjoy thinking around in the front end with front and frameworks, and you're not going to really enjoy bootstrap as much as if you were just doing it straight with no Java script.

So in the end, it really depends whether or not you should use bootstrap.

I generally would say not to use bootstrap unless you have a good reason to use it.

Most people default to using boots drug unless they have a reason not to.

And I personally think that is kind of a backwards way to think.

I'd almost always say, Don't use bootstrap unless you absolutely have a good reason to.

So with out of the way, thank you very much for watching this video check on my other videos linked over here and subscribe to the channel from more videos just like this one.