However, before I get into the details, let me back up a little and tell you my story.
A few years ago, I was where many of you are right now — working in a big corporate world — being tired of petty internal politics and infighting …
I became increasingly troubled by the splurge of conflicting corporate tools … battling interoperability inconsistencies … and longed for a simpler life, where I could flex my programming skills and complete meaningful and rewarding projects that somehow made a difference in the world.
Back in 2015, I was using constantly new and different software tools to create all the separate types of projects that have become necessary in our modern world … iOS apps, Android apps, web apps, websites, Windows Desktop apps, Apple Desktop apps, PWAs …
Each separate flavor of app required a specific and unique group of tools for designing, deving and building, but I still dreamed of a single tool that would replace them all …
I longed for a single framework that would remove all the complexity and produce all these different flavours of apps … from a SINGLE codebase.
Unable to locate such a mythical tool, I decided to build it.
It was a mammoth undertaking. Starting from scratch I knew that I needed to base it on a powerful core framework that could be easily be extended and enhanced to produce the comprehensive system I was envisaging …
Around this time, VueJS was coming to prominence. After reviewing its structure, development path and extensibility, I decided it would provide the perfect basis for the new framework I planned to construct … and save vast amounts of time during the development cycle.
This was the exact moment that the Quasar Framework was born.
The concept of the Quasar Framework is to be a comprehensive set of components used to construct modern apps … from simple basic components like dialogs, buttons, inputs, tabs, panels, tooltips, toolbars, badges, date pickers, color pickers, icon pickers, cards, avatars, banners, tooltips, spinners and more … all the way through to much more advanced components like chat message boxes, activity timelines, datatables, calendars, video players, wysiwyg editors, fly-in panels, ribbon bars … and much more …
These components are all based on top of VueJS… making their use completely familiar to all the many Vue developers looking for an easy extensible component system to expand their projects.
As of today’s release of the all-new Version 1, Quasar includes 123 components … and that number is constantly increasing due to an inbuilt system for custom component creation …
Quasar also provides the build system necessary to create production ready apps … all from one single simple command line …
After installing one global dependency and creating a project, literally one line of code is all that’s required to build a production ready iOS app, Android app, Web app, Windows Desktop app, MacOS Desktop app or Linux Desktop app … from your one single codebase …
$ quasar build
Forget the complexities of Webpack and Babel … tree-shaking … and other bundle optimisation techniques … that’s all wrapped up, hidden behind the scenes and handled automatically for you — all the while retaining the complete ability for you to step in and customise the process should you feel the need.
This is power and extensibility wrapped up in a way that simplifies and speeds up your development process like you have never imagined before.
Early versions required many changes — often breaking changes — which I’m sure annoyed many of our early adopters, but they were necessary growing pains as we iteratively developed this extensive system.
Versions 0.13, 0.14, 0.15, 0.16 up to 0.17 were used to refine the framework, and by version 0.17 there was finally a suitable structure that could form a stable foundation that could grow and expand without the need for future breaking changes.
So, we took the decision to freeze development and undertake a complete refactoring to organise and optimise what we had created.
Notice, I say “we” … because, by this time, I had realised what a massive undertaking this was becoming … and understood it could never be achieved single-handedly, so I began recruiting a core team to collaboratively manage the development.
First one developer joined … then a second … and a third … until we’ve reached our current level of eight members in the core development team. Each a seasoned, experienced developer with skillsets complementing those of the others.
They’re backed up by a further level of additional volunteer staff members who handle customer support, documentation, media, and more …
And there’s also an active community of friendly developers … all willing to share and contribute their knowledge and advice to help everyone grow and develop together.
I like to think of this as our extended family — all gathered around a common goal of helping each other and pushing each other to new exciting levels of achievement.
Our Discord chat server in particular is a vibrant active community that never seems to sleep … there’s always ongoing conversations about a massive range of topics … and helpful advice being willingly exchanged by excited developers.
Version 1 has been a massive development … a major investment of time and effort by the team and all of the amazing open source contributors.
Since our decision to freeze development of the Version 0.* branch … over 4000 development hours have been invested in the production and rewriting of Quasar.
Also, our hyper-engaged user community have been actively involved in perfecting the code throughout our 5-month open beta and release candidate process … so that we could publish a battle-tested version …
Today’s release of Quasar v1 Stable is a major milestone in the Quasar story … but only a stepping stone for the greater things we have planned for the future …
This release has been designed with flexibility and extensibility in mind … but we already have a significant roadmap in place for where Quasar goes from here, which includes several major new build targets like Browser Extensions, Webview and Capacitor.
Our re-write required major systems and processes be put in place that would enable Quasar to grow and remain relevant for years to come … without the need to make significant future breaking changes …
So, if you’re a Vue developer (or even a non-Vue developer) who wants to:
then this latest Quasar release is one you simply cannot ignore.
This article has only scratched the surface of the power and capabilities of the Quasar Framework.
There are many features and important aspects that I haven’t had the time to mention here, so over the next few weeks, I’m going to be issuing a series of articles detailing the individual features and concepts of the Quasar Framework … watch out for them.
In the meantime, we have an active and friendly community on both our Forum and Discord chat group to welcome you with open arms …
There’s detailed documentation and examples to get you started …
A massive pool of quality components ready for dropping directly into your existing or new projects today …
Great ways to share your code, like preconfigured CodeSandbox, jsFiddle or Codepen …
And an easy to use build process, fully configurable (although in 99% of the cases you won’t even need to touch it) … that follows all of the latest and greatest best web practices …
Jumpstart a SPA, PWA, SSR, Mobile App or Desktop App in 30 seconds … (yes, it’s that easy to get you started!)
So, come on over, give Quasar a shot … join our family … enjoy the support of our team and the community of enthusiastic and friendly fellow developers who love using Quasar each and every day …
More info: https://quasar.dev
Newsletter: https://quasar.dev/newsletter
Getting Started: https://quasar.dev/start
Chat Server: https://chat.quasar.dev/
Forum: https://forum.quasar.dev/
Twitter: https://twitter.com/quasarframework
Donate: https://donate.quasar.dev
Thankyou!
Razvan Stoenescu: https://github.com/rstoenescu
Repo: https://github.com/quasarframework/quasar