When I first started working with Vue.js, I didn't need an SSR-based project at that time. When I needed a Vue application on the server side, I did a little research. After some exploration, I encountered two alternatives. The first one was Nuxt.js, the Vue counterpart of Next.js. Nuxt.js's advanced router structure, enabling the deployment of a server-side Vue-based application for the web, was sufficient for me.

Although the framework uses Vue, you can still face some annoying changes for such tasks. For instance, having different variations on link structure and router within Nuxt, and the necessity to create many different structures, can slightly spoil the development experience. The overall structure is understandable, and there is no direct alternative anyway. However, as I recently worked on an e-commerce infrastructure, I also needed a structure that could compile an application for mobile when necessary, along with the web side.


Quasar JS

It was at this point that I got acquainted with Quasar. I can say that Quasar was a revolution for me both on the front-end side and on the mobile platform, where I hadn't yet deep-dived. Let's delve into the features that Quasar offers.


Key Benefits


  • All Platforms in One Go

    • You really have a compilable application for all platforms. You can target the platform you want and create an application. It supports SSR, PWA, Native Web Apps, Electron-based desktop applications, and more.

  • Web Components Infrastructure

    • With support for many platforms, it comes with a powerful web component structure and many utilities, making it a robust foundation. Its extensive component library provides a predictable and easily scalable development process throughout many parts of the application.

  • Best-Practice Application Structure Integrated by Default

    • To elaborate on this feature, since the framework is well thought out in many aspects, it allows you to directly benefit from the technical infrastructure and configurable features provided by the application before finding a solution for almost all scenarios. Additionally, having robust documentation containing many details is another plus feature.


I've covered the key features that matter to me so far. You can find more details at the following link.

https://quasar.dev/introduction-to-quasar#best-practices-integrated-by-default


Cross-platform Features

Desktop Application

You can compile with Electron on the desktop side. When developing an application, you can simultaneously develop it for mobile and web, excluding Electron. However, in the Vue part, you need to carefully identify the areas that Electron needs to interpret and isolate the client-based portions.


Web Application

On the desktop side, you can switch between two different rendering modes: SSG and SSR. Personally, I do not recommend SSR if your applications are working heavily under load for the SSR part. However, it can be useful if you have a project like a Single Page Application.


Mobile Application

I previously experimented with Android using Cordova and achieved successful results. I can say that it is successful in rendering Native Applications in web-based development.


Conclusion

I haven't worked with React.js for a long time, and I don't know if there is such an alternative on the native side for mobile. However, I think Quasar should not be considered only as Vue. Thanks for reading.