Quasar CLI makes it incredibly simple to develop or build the final distributables from your source code.
Before we dive in, make sure you got the Cordova CLI installed.
$ yarn global add cordova
$ npm install -g cordova
$ quasar dev -m cordova -T [ios|android]
You can develop with any Quasar theme, regardless of the platform you are building on (Android, IOS, …).
In order for you to be able to develop on a device emulator or directly on a phone (with Hot Module Reload included), Quasar CLI follows these steps:
- Detects your machine’s external IP address. If there are multiple such IPs detected, then it asks you to choose one. If you’ll be using a mobile phone to develop then choose the IP address of your machine that’s pingable from the phone/tablet.
- It starts up a development server on your machine.
- It temporarily changes the
/src-cordova/config.xmlto point to the IP previously detected. This allows the app to connect to the development server.
- It defers to Cordova CLI to build a native app with the temporarily changed config.xml.
- Cordova CLI checks if a mobile phone / tablet is connected to your development machine. If it is, it installs the development app on it. If none is found, then it boots up an emulator and runs the development app.
- Finally, it reverts the temporary changes made to
If developing on a mobile phone/tablet, it is very important that the external IP address of your build machine is accessible from the phone/tablet, otherwise you’ll get a development app with white screen only. Also check your machine’s firewall to allow connections to the development chosen port.
$ quasar build -m cordova -T [ios|android]
You can build with any Quasar theme, regardless of the platform you are targeting (Android, IOS, …).
These commands parse and build your
/src folder then overwrite
/src-cordova/www then defer to Cordova CLI to trigger the actual native app creation.
You may ask yourself. So where’s the .apk or .app? Watch the terminal console to see where it puts it.