Quasar Framework

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:

https://quasar.dev/newsletter

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.

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.

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.