Configuring Cordova

We’ll be using Quasar CLI (and Cordova CLI) to develop and build a Mobile App. The difference between building a SPA, PWA, Electron App or a Mobile App is simply determined by the “mode” parameter in “quasar dev” and “quasar build” commands.

There are two configuration files of great importance to your mobile apps. We’ll go over each one.

config.xml

The most important config file for your mobile app is /src-cordova/config.xml. The /src-cordova folder is a Cordova project, so please refer to Cordova documentation in order to understand what each file from there does. But for now, have a few moments to read about config.xml.

Some properties from this file will get overwritten as we’ll see in next section.

quasar.conf.js

Quasar CLI helps you in setting some properties of the mobile Apps automatically (from config.xml): the Cordova “id”, app version, description and android-versionCode. This is for convenience so you’ll be able to have a single point where, for example, you change the version of your app, not multiple files that you need to simultaneously touch which is error prone.

For determining the values for each of the properties mentioned above, Quasar CLI:

  1. Looks in /quasar.conf.js for a “cordova” Object. Does it have “id”, “version”, “description” and/or “androidVersionCode”? If yes, it will use them.
  2. If not, then it looks into your /package.json for “cordovaId”, “version” and “description” fields.

Other options you can configure:

return {
  framework: {
    config: {
      cordova: {
        iosStatusBarPadding: true/false, // add the dynamic top padding on iOS mobile devices
        backButtonExit: true/false // Quasar handles app exit on mobile phone back button
      }
    }
  }
}