Packaging and Publishing Hybrid Mobile Applications

Use the Oracle JET framework and third-party tools to package and publish your hybrid mobile application to Google Play, Microsoft Store, or Apple App store.

Packaging Hybrid Mobile Applications

Use the grunt build:release command to package your hybrid mobile application. You must also sign the application before you can deploy it.

Perform the following tasks for each platform that your hybrid mobile application supports.
  1. Create a buildConfig.json file to specify how to code sign your application.

    The steps to code sign your application and create the buildConfig.json file vary by platform.

  2. Change to the root directory and issue the grunt build:release command with the desired platform type and specify the path and name of the buildConfig.json file.
    grunt build:release --platform={ios|android|windows} --buildConfig=path/buildConfig.json

    The command will take some time to complete. When it’s successful, you’ll see the following message: Done, without errors.

    The command will also output the name and location of the unsigned application in hybrid/platforms/android , hybrid/platforms/ios, or hybrid/platforms/windows.

  3. To verify that the application still works as you expect, run grunt serve with the release option.
    grunt serve:release --platform=ios|android|windows [--browser --server-port=server-port-number --livereload-port=live-reload-port-number --destination=emulator-name|device] --buildConfig==path/buildConfig.json

    The command takes the same options that you used to serve the development version of your application with two exceptions:

    • You must specify the path and name of the buildConfig file.

    • Live reload is disabled by default in release mode, and you do not need to pass in a flag to disable it.

Publishing Hybrid Mobile Applications

The steps you take to publish your hybrid mobile application depend upon your target platform. In all cases, follow the vendor’s documentation for instructions.