Need advice about which tool to choose?Ask the StackShare community!
Quasar Framework vs UIkIt: What are the differences?
Key Differences Between Quasar Framework and UIkit
Quasar Framework and UIkit are two popular options for building websites and user interfaces. While they share some similarities, there are several key differences that set them apart. Here are six important distinctions:
Design Philosophy: Quasar Framework follows a Material Design approach, which focuses on clean, modern aesthetics and smooth animations. On the other hand, UIkit emphasizes a lightweight and modular design, allowing developers to pick and choose specific components based on their needs.
Component Library: Quasar Framework offers a comprehensive set of UI components out of the box, covering almost every aspect of building an application. UIkit, on the other hand, provides a smaller but still versatile collection of components, with a focus on modularity and customization.
Integration and Ecosystem: Quasar Framework is built on top of Vue.js, a popular JavaScript framework. It integrates seamlessly with Vue's ecosystem, allowing developers to leverage the vast Vue ecosystem and community. UIkit, on the other hand, is framework-agnostic and can be used with any JavaScript framework or even without one.
Development Approach: Quasar Framework follows a principled approach to development, providing a standardized and opinionated structure for building applications. UIkit, on the other hand, offers more freedom and flexibility in terms of structuring and organizing code.
Size and Performance: Quasar Framework, being a more comprehensive framework, comes with a larger bundle size compared to UIkit. However, Quasar's modern build system allows for tree-shaking and code-splitting, resulting in optimized performance. UIkit, with its modular design, offers a smaller footprint and can be more suitable for projects with strict size constraints.
Community and Support: Quasar Framework has a growing and active community, with regular updates and maintenance. It also provides comprehensive documentation and support channels. UIkit, while also having an active community, may have a smaller user base and support network compared to Quasar.
In summary, Quasar Framework and UIkit have different design philosophies, component libraries, integration approaches, development approaches, sizes, and community support. Choosing between them depends on project requirements, preferences, and the desired balance between customization and convenience.
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 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.
Pros of Quasar Framework
- Excellent documentation59
- Deploy one codebase to web, desktop, mobile, and more44
- Lots of UI components40
- Extensive collection of components39
- Being able to bundle for almost all platform is awesome33
- Quasar App Extensions27
- Excelent performance27
- Great community25
- Open Source20
- Attention to Security16
- Material Design15
- It is easy because of vue11
- 1 Cross Platform Android, IOS and Desktop10
- Cross Platform Andriod, IOS and Desktop10
- SSR8
- Vue 3 Support7
- Active and helpful community6
- Treeshaking4
- Simple to use3
Pros of UIkIt
- Complete GUI39
- Easy modify29
- Practical27
- Easy to learn24
- Functional24
- Intuitive22
- Free21
- Simple16
- Lightweight15
- Easy to use15
- Modular5
- Because I can create amazing things with little effort5
- Modern look5
- Responsiveness4
- Small but Active Community3
- Convenient JS Components2
- Based on Flexbox2
- No requires jquery2
- Responsive grid2
Sign up to add or upvote prosMake informed product decisions
Cons of Quasar Framework
- Stackoverflow 1.5k Questions4