you’re right for Pug, I forgot it was automatic
Great! Right now I’m customizing the build.extendWebpack function of quasar.conf.js to add loaders to my Vue single component files. I guess the documentation will talk about that.
The beauty of quasar is deploying to multiple platforms form a single codebase.
Regarding PWA caching: all this does is keep in memory the static assets that make up an SPA, so you can access those offline. In other words, a PWA does not help with user initiated server interactions. So if you want your app to work offline and still register user actions somehow, you need to figure it out on your own.
Main problem with dynamic changing the theme at runtime is webpack related. Can’t manage CSS since webpack is doing it. Once you import some CSS it is there to stay. Before switching to webpack + vue-router, Quasar had its own build system and dynamic theme switching was possible. It actually detected if you’re on an Android or iOS device and delivered the according theme. Looking forward to a solution with webpack if anyone has time for this. I’m currently working on v0.15 goodies and I’m 200% overloaded. Any help on theme switching is greatly appreciated.
Quasar is a front-end framework. What you are looking for or rather where you should be looking is within the API or backend, which Quasar currently doesn’t have. There are two API wrappers in the works. One for a REST API based on FeathersJS and another for a GraphQL API based on Apollo. They should get you a lot closer to what you are looking for.