You are here: Building an Application
Building and Viewing an Application
Quantum Visualizer gives you different ways of building and viewing your app, depending on your needs. In Kony Visualizer Classic, you can build your app either from the Product menu, or from a command line. And you can view your built app either by previewing it on a mobile device, or by using device emulators and simulators that you configure.
For a smooth build in Kony Visualizer Classic, you'll want to ensure that the following issues have been addressed:
- Ensure that Quantum Fabric is set up in Quantum Visualizer and that you have selected a default Quantum Fabric environment to publish to. For more information, see Connect to the Quantum Fabric Console.
- Be prepared to provide your Quantum Visualizer licensing information the first time you build an application.
- You can choose to not generate print statements during either or both Debug Mode builds and Release Mode builds. For more information, see Disable Print Statements in Builds.
- For Android, ensure you have set the minimum SDK version to between 4.0 and 4.4. To change this setting, on the File menu, click Settings. Click the Native tab, and then click the Android sub-tab. The Minimum setting is located in the SDK Versions section of the dialog box. After changing the setting, click Finish.
- For Android, ensure you have set the location of the Android SDK. To do so, on the Window menu, click Preferences. In the left pane, double-click Quantum Visualizer, and then click Build. If it hasn't done so already, at this point Quantum Visualizer auto-detects the Android SDK and asks if you would like to use the path that it has discovered as the Android Home. If you wish to, click OK. If Quantum Visualizer did not auto-detect the Android SDK, in the Android Home text box, enter the path to the Android SDK packages. To ensure you don't introduce errors into the path that you type, you may want to click the accompanying Browse button, navigate to the Android SDK's location, and then click OK.
- For Android, ensure you have set the SDK home environment variable for your computer. To do so, see Set the Android SDK Home Environment Variable.
Important: If your app contains deprecated widgets, it's possible that their skins may make reference to the Helvetica font. If you are not explicitly using Helvetica in your app, you should verify your app's configuration and manually remove references to Helvetica before submitting it to the store. The following topics are covered with regard to building an app using Quantum Visualizer.
Build an iOS Application
Build an Android Application
Build a Universal Application
Build a Windows 10 Application
Build an Adaptive Web Application
Build a Native App on a Local machine
Disable Print Statements in Builds
Perform a Headless Build
Publish a Project to KonyFabric
Preview an App on a Device
Monitor an App's Performance
View an Application on an Emulator
iOS Build Automation
Open Webapp and Build Folders
While developing any application on Visualizer, you must undertake certain steps such as testing the application and building the binaries multiple times. For every change that you make in the app, the whole project needs to be built each time; thereby, increasing the build time.
To ensure that there is a faster turnaround, a new feature, Incremental Build is introduced in Quantum Visualizer V8 SP4 release.
When an app is built for the first time, a full build is performed. The subsequent builds are incremental. In an incremental build, the previously built state of the project is used and only those resources that are changed since the last build are regenerated.
The following are the scenarios where the build is always a full build.
If controllers that interact with the NFI are modified.
If controllers that interact with third-party libraries are modified.
If any changes are made to the property window. For example, SDK/iOS deployment.
If a Temenos Forge component is added into the Visualizer project.
If a new app module(group) is added into the Visualizer project.
If any changes are made to plugins like Sketch and Adobe Photoshop.
- If the following project settings are modified:
- Accessibility Config
- Enable Cordova
- Enable Action Bar (for Android native platform)
- Enable Responsive Web (for Desktop Web platform)
- Enable i18n Layout Config
- Enable designer/ developer actions
You do not have to perform an incremental build and a full build separately. Visualizer will automatically decide whether to perform a full build or an incremental build based on the changes made.
If you add an external asset or library to the Visualizer project after a full build, you must clean up the project using the Clean menu. The Clean menu erases files that were generated during the previous build and makes the project ready for the subsequent build. Once the project is cleaned, Visualizer will perform a full build the next time you trigger a build.
If you do not clean the project and perform a build, Visualizer will not take into consideration the assets and libraries added while performing the build.
Note: The Incremental build is supported only by the regular build.
|| © 2020 Temenos. All rights reserved.