HI, I will give you the counter argument. I selected Vuetify over Quasar. Here’s why.
I was initially drawn to Quasar because I wanted to write one code base and have web and native mobile come out the back end without much effort. I can’t afford to re-write my entire code base to get native mobile apps and I definitely can’t do it three times to support web, iOS and Android. So found Quasar and thought that was going to be the perfect solution.
I started building my app with Quasar. Then I realized that native app support was just using cordova and I realized that there were many solutions to putting a Vue app into cordova. So at that point it took away my perception that Quasar had the native platform advantage. Since then, I have decided that I would use NativeScript for my native apps.
So I re-evaluated Vuetify vs Quasar. I ended up selecting Vuetify. They seemed to have a very similar set of UI components. Neither really won on that front. I made sure that the UI elements I would need were available on both. They were.
I had already spent a month or two in the Quasar world and on their discord server. It was here that I realized they are a very small team trying to do a huge amount of stuff. They need way more help to do everything they are trying to do. Hopefully the team will grow and they will get there. This was the first strike against them. And with Vue 3 coming out, I wonder how long it will take them to fully support.
To me Vue 3 is critical. I do everything in Typescript and Vue 2 + Typescript sucks. Vue 3 + typescript is quite nice. So as soon as I can get on to vue 3 proper and off the composition API plugin the better.
The second strike against Quasar was unit testing. They don’t (or didn’t at the time) have unit testing of their library. I am a firm believer in the benefits of unit tests. The app I am porting has around 7000 unit tests for the front end alone and another 10,000 on the backend. Vuetify has unit tests for their components. I have gone and looked at them and stolen some ideas of how to unit test my components from them.
The third strike against Quasar was its divergence from Vue. Since they are trying to be a complete framework, they encourage you to use the Quasar CLI instead of the Vue CLI and I think that will bite people in the end, especially when Vue comes out with new versions. I think this coupled with the small team of Quasar will cause this to be an issue.
So given all that, I chose to go with Vuetify. Now I really hope that Vuetify comes out with a Vue 3 version within weeks of Vue 3 becoming officially released.
I admire the Quasar guys for building something great. For me, building a commercial product, I wanted something I could trust a bit more.