![quasar vue quasar vue](https://1.bp.blogspot.com/-eKDu5IJeExQ/XvSYAt2BCCI/AAAAAAAAKO8/cg_qCxw9UXoYqAwebD_FDaY-MmDoCZszQCLcBGAsYHQ/s1600/weather-app-vue-js-quasar.jpg)
![quasar vue quasar vue](https://forum.quasar-framework.org/assets/uploads/files/1604939490882-screen-shot-2020-11-09-at-16.19.17.png)
In those kind of projects I would strongly relied on the business goals, metrics, cta’s, content. The only drawback is initial loading thanks Anyway, the modern marketing sites are quite complicated beasts. SPA - if you need app functionalities, if you think about mobile app, if you consider using PWA then this is the way to go. SSR - wouldn’t go that way - there are too much quirks in integrations with 3rd party solutions It is extremely easy to integrate with anything “marketing” style I will give those 3 options points in scale 1-5 - more points better, always scaled to best option: front server with reverse proxy (nginx, openresty).I assume that every option will have a classic stack of: Lets evaluate 3 options for Quasar: UMD, SSR, SPA. Let’s choose some constraints for this marketing style site:Ģ- extremely easy integration with 3-rd party analatics, affiliates, ads, a/b testers, etc.ģ- live data - option 1 - the data are loaded with initial page opening and then no loadingĤ- live data - option 2 - the data are refreshed after user action (filter, select, click on chart)ĥ- live data - option 3 - the data are analyzed/displayed in real time (stock ticker, server load)ħ- easy and fast changes to structure of the site (links, navigation, etc.)Ĩ- app - option 1 - there is no need to login, authenticate, keep session for purposes other than analyticsĩ- app - option 2 - there is a need to authenticate users and show them personalized content/dataġ0.- … ok, there could be more criterions… especially organisational/logistics ones… but let’s stop here…