What is Quasar Framework?
Who uses Quasar Framework?
Quasar Framework Integrations
Here are some stack decisions, common use cases and reviews by members of with Quasar Framework in their tech stack.
I use Quasar Framework because it saves me a ton of time and effort. I'm also not the greatest front-end dev and the mix of Vue templates and the supremely made components and build system puts front-end development at a level where I don't need to worry about the finer points of "doing-it-right". Quasar does it right for me.
Vue.js vuex Quasar Framework Firebase Firebase Authentication Cloud Firestore Electron Apache Cordova
I'm developing my new project with the Quasar framework on the front end and Firebase services on the backend.
I use Quasar Framework because it offers more functionality out of the box than anything else I evaluated (Angular, React, Vuetify, Bootstrap-vue, etc) for my current project. The API is concise and well documented, commitment to security, active development and user communities, and the controls look good and work as documented.
Quasar Framework is easy to learn and use. Rich set of components. Web, mobile and desktop with only one source code.
One client ask me to get his spa to the play store, so I recently came across google's wpa and make one with vue but I couldn't make it to the store, so I begin to look for an alternative and found Quasar Framework , I'm really happy with it, I think it's easy and powerful, and the fact that it works on top of Vue.js makes it perfect! I highly recommend it
Vue.js vuex Vue Router Quasar Framework Electron Node.js npm Yarn Git GitHub Netlify My tech stack that helps me develop quickly and efficiently. Wouldn't want it any other way.
Here are some stack decisions, common use cases and reviews by companies and developers who chose Quasar Framework in their tech stack.
Quasar Framework FeathersJS Node.js Vue.js SendinBlue Zeit Now GitHub
It was almost too easy to build a complete Feathers Rest API combined with Quasar SSR and reactive form that we are serving through an i-frame within our main site for serving our newsletter signup and opt-in page. Total time: 15 hrs. Check it out:
I'm building most projects using: Server: either Fastify (all projects going forward) or ExpressJS on Node.js (existing, previously) on the server side, and Client app: either Vuetify (currently) or Quasar Framework (going forward) on Vue.js with vuex on Electron for the UI to deliver both web-based and desktop applications for multiple platforms.
The direct support for Android and iOS in Quasar Framework will make it my go-to client UI platform for any new client-side or web work. On the server, I'll probably use Fastly for all my server work, unless I get into Go more in the future.
Update: The mobile support in Quasar is not a sufficiently compelling reason to move me from Vuetify. I have decided to stick with Vuetify for a UI for Vue, as it is richer in components and enables a really great-looking professional result. For mobile platforms, I will just use Cordova to wrap the Vue+Vuetify app for mobile, and Electron to wrap it for desktop platforms.
Coming from a non-web development environment background, I was a bit lost a first and bewildered by all the varying tools and platforms, and spent much too long evaluating before eventualy deciding on Laravel as the main core of my development.
But as I started development with Laravel that lead me into discovering Vue.js for creating beautiful front-end components that were easy to configure and extend, so I decided to standardise on Vue.js for most of my front-end development.
During my search for additional Vue.js components, a chance comment in a @laravel forum , led me to discover Quasar Framework initially for it's wide range of in-built components ... but once, I realised that Quasar Framework allowed me to use the same codebase to create apps for SPA, PWA, iOS, Android, and Electron then I was hooked.
So, I'm now using mainly just Quasar Framework for all the front-end, with Laravel providing a backend API service to the Front-end apps.
I'm deploying this all to DigitalOcean droplets via service called Moss.sh which deploys my private GitHub repositories directly to DigitalOcean in realtime.
Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.
This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!
But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?
I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.
Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...
I built a project using Quasar Framework with Vue.js, vuex and axios on the frontend and Go, Gin Gonic and PostgreSQL on the backend. Deployment was realized using Docker and Docker Compose. Now I can build the desktop and the mobile app using a single code base on the frontend. UI responsiveness and performance of this stack is amazing.
Starting a large project is always a daunting task so I sat down to plan. I didn't discover Quasar Framework until quite late on in this process - in fact, I had already built a huge portion of my app.
I knew from the outset I wanted to use Vue.js because of it's simplicity and ease of use. Once that decision had been made I decided to look at Bootstrap style components already written for Vue and there were a great many BUT non of them ticked all the boxes so it was this that lead me to Quasar. I was actually looking for a calendar component and someone pointed me to Quasar in a stack overflow comment - I fell in love. I even called my wife in to show her this beautiful component I just found - I'm still not sure she shared my enthusiasm...
This was just the beginning for me with Quasar. At the time Quasar was v0.0.15 and since then it has grown from strength to strength. I have live apps on the App Store, Play Store and available online. Given it will soon handle browser extensions, this means Quasar can do anything your imagination would want.
Why did I choose Quasar Framework - because there is nothing like it on the market. Not that offers such a diverse build system using it's home brewed CLI, none that build SPA, PWA, SSR, Browser all from the same code base, none that have the same amazing community to help you when you're stuck and none that have a team that work hard to achieve the common goal Quasar Framework has - to make the development experience for everyone easier and better.
That's why I made the decision to use Quasar Framework.
Quasar Framework's Features
- SPAs (Single Page App)
- SSR (Server-side Rendered App)
- PWAs (Progressive Web App)
- Mobile Apps (Android, iOS, …)
- Full RTL Support
- Persian Calendar
- Material Design 2
- Complete Documentation
- Unit Test Ready