Need advice about which tool to choose?Ask the StackShare community!
Bootstrap vs PrimeNg: What are the differences?
Both Bootstrap and PrimeNg are popular frameworks used for front-end development. Let's explore the key differences between Bootstrap and PrimeNg.
Responsive Design: Bootstrap is built with a mobile-first approach, offering a responsive grid system that automatically adjusts according to the device's screen size. PrimeNg also provides responsive design features, but it requires manual customization to ensure full responsiveness.
Component Library: Bootstrap offers a comprehensive set of ready-to-use components, such as buttons, forms, navigation bars, modals, and more. PrimeNg, on the other hand, provides a larger component library with a wide range of UI elements, including advanced components like charts, data tables, and calendars.
Theming and Customization: Bootstrap provides a customizable and easy-to-use theming system, allowing developers to quickly modify the overall look and feel of their applications. PrimeNg also supports theming, but it requires more effort and has a steeper learning curve compared to Bootstrap.
Rich User Experience: Bootstrap focuses on simplicity and ease of use, providing a clean and straightforward user experience. PrimeNg, on the other hand, offers a more feature-rich experience with advanced components and functionalities, making it suitable for complex enterprise applications.
Dependency Management: Bootstrap is a standalone framework that can be easily integrated into any project, regardless of the technology stack. PrimeNg, on the other hand, is specifically designed for Angular applications and heavily relies on Angular's ecosystem, making it less flexible for projects with different frameworks.
Community and Support: Bootstrap has a massive community and extensive documentation, making it easy to find resources, tutorials, and help from other developers. PrimeNg also has a supportive community, but it is relatively smaller compared to Bootstrap, which may result in slower response times and fewer available resources.
In summary, Bootstrap is a versatile and widely adopted framework known for its simplicity and fast development process, while PrimeNg offers a larger component library and more advanced features, making it suitable for enterprise applications.
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.
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.
But we have to decide on a CSS framework for the UI. I'm partial to Bulma because I love that it's all about CSS (and you can use SCSS from the start), that it's rather lightweight and that it doesn't come with JavaScript clutter. One of the things I hate about Bootstrap is that you depend on jQuery to use the JavaScript part. My boss loves UIkIt, but when I've used it in the past, I didn't like it.
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.
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:
-
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
-
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
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.
We are building a PWA using AngularJS targeting Mobiles, Tablets, Laptops and Desktops. Like for smaller to larger screens. This is our first PWA and my first project in Angular. We are confused between PrimeNg and Bootstrap. I read in an article that PrimeNg has got Bootstrap implemented in it from 5.x.x version. Which is the best Framework for this?
For a new project with angular use angular.io, not angularjs. Angular has pwa ready to go functions, ngrx data to optimise data loads and store management. PrimeNg is a powerful library but angular material gives you enough power. Take good care adding such libraries because of compatibility issues on uograde. Look at what you can do with angular material, and then add primeNg if you have no choice.
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.
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.
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.
Fonts and typography are fun. Material Design is a framework (developed by Google) that basically geeks out on how to assemble your typographical elements together into a design language. If you're into fonts and typography, it's fantastic. It provides a theming engine, reusable components, and can pull different user interfaces together under a common design paradigm. I'd highly recommend looking into Borries Schwesinger's book "The Form Book" if you're going to be working with Material UI or are otherwise new to component design.
https://www.amazon.com/Form-Book-Creating-Printed-Online/dp/0500515085
Pros of Bootstrap
- Responsiveness1.6K
- UI components1.2K
- Consistent943
- Great docs779
- Flexible677
- HTML, CSS, and JS framework472
- Open source411
- Widely used375
- Customizable368
- HTML framework242
- Easy setup77
- Popular77
- Mobile first77
- Great grid system57
- Great community52
- Future compatibility38
- Integration34
- Very powerful foundational front-end framework28
- Standard24
- Javascript plugins23
- Build faster prototypes19
- Preprocessors18
- Grids14
- Good for a person who hates CSS9
- Clean8
- Easy to setup and learn4
- Love it4
- Rapid development4
- Great and easy to use3
- Easy to use2
- Devin schumacher rules2
- Boostrap2
- Community2
- Provide angular wrapper2
- Great and easy2
- Powerful grid system, Rapid development, Customization2
- Great customer support2
- Popularity2
- Clean and quick frontend development2
- Great and easy to make a responsive website2
- Sprzedam opla2
- Painless front end development1
- Love the classes?1
- Responsive design1
- Poop1
- So clean and simple1
- Design Agnostic1
- Numerous components1
- Material-ui1
- Recognizable1
- Intuitive1
- Vue1
- Felxible, comfortable, user-friendly1
- Pre-Defined components1
- It's fast1
- Geo1
- Not tied to jQuery1
- The fame1
- Easy setup21
Pros of PrimeNg
- Complete6
- Wide range of components4
- Easy to use3
- Already 17+ version up1
- Modern UI components that work across the web1
Sign up to add or upvote prosMake informed product decisions
Cons of Bootstrap
- Javascript is tied to jquery26
- Every site uses the defaults16
- Grid system break points aren't ideal15
- Too much heavy decoration in default look14
- Verbose styles8
- Super heavy1
Cons of PrimeNg
- Components are hard to customize4
- Easy to use3
- Need to buy themes3
- Hard to understand2
- No documentation2
- Functionality differs for all components2