An "App" is a basic unit used in the App Builder for building apps. You should create an App to build new apps. Moreover, you can change or delete an App in the App Builder. You can build Android, iOS and macOS apps depending on how you configure an App.
Create App
Select the menu [App > Create App] in the App Builder to open a dialog for creating a new App. Create a new App by setting its name, which cannot be changed later. The name is used only for managing the list of Apps inside the App Builder without affecting the actual app build process.
App Info
Clicking the Create button takes you to the App Info stage where you can fill in the information about the new App, which will not be created before you click the Save button.
Category | Description | |
|---|---|---|
1 | General | Basic information about the apps to build |
2 | Build configuration | Sets options for building apps |
3 | Authority | Authorization to use the App |
4 | Target OS | Selects OSes for which apps will be built |
5 | Nexacro application resource | Manages resources used for apps |
General
Description | ||
|---|---|---|
1 | Package Name | Name of the package |
2 | Version | Version of apps to build |
3 | App Title | Name of apps to build |
A package name is used as the identifier of apps to build. Normally, a package name is created by writing a domain name in the opposite way.
eg) com.nexacro
If you create a package name with only one word, an error may occur in the build process.
If you include iOS as a target OS, you must use the same package name as the one that you entered when requesting a provisioning profile.
Build configuration
Description | ||
|---|---|---|
1 | Nexacro Project URL | This is the URL where the Nexacro Platform-based app is located. The last slash in the URL must be omitted. |
2 | Build mode | Selects the build mode. If you choose "debug", you can perform debugging by using Android Debug Bridge (adb). |
3 | Detail Error Message Output | Determines whether to expose the error messages that come out during the loading process |
4 | Nexacro Mobile Library | Selects a Nexacro Platform mobile library. You must choose the library of the same version as the one used in developing the app. |
Authority
Description | ||
|---|---|---|
1 | Owner | Designates the owner of the App (The account holder who has logged in the App builder will be designated as the owner automatically.) |
2 | Access | Authorization to use the App. The items of the App List varies according to the authorization. - share: designated users can use the App. - public: all users can use the App. - private: only the owner can use the App. |
Regardless of the settings of the Access option, those who are authenticated as administers can use every App.
Target OS
Select OSes for which apps will be built. You can configure detailed settings for each selected OS. If you attempt to upload resources directly from the management console rather than Nexacro Studio, you should register appropriate JSON files (start_[OS name].json). Then the Nexacro application resource category will print necessary resources, allowing you to upload those resource files.
Clicking the detail button opens a table showing the contents of the JSON file.
Nexacro application resource
If you attempt to upload resources directly from the management console rather than Nexacro Studio, you should register appropriate JSON files (start_[OS name].json) in the Target OS category. Then this category will print necessary resources, allowing you to upload those resource files. If you have built an App by connecting the App Builder from Nexacro Studio, this category will show you a list of the resource files you registered in Nexacro Studio.
Items in the table can be in orange-like color, which indicates changed data. Specifically, the color means that those items are newly-registered resource files or that their versions are different from those of the resources defined in the JSON file.
Android platform
Category | Description | |
|---|---|---|
1 | Project Modification | Based on the created App, you can export a project that can be edited in Android Studio. By contrast, you can import a project that has been edited through Android Studio. |
2 | Build configuration | Selects a target software development kit (SDK) and designates an icon and splash images |
3 | Signing Info | Selects a signature |
4 | User Library | Selects user libraries |
5 | Android Permission | Selects device API permissions |
Build Configuration
Category | Description | |
|---|---|---|
1 | Target SDK Version | Selects the Android API level of the app to build. The minimum required level is Android 4.4.2 (API Level 19) |
2 | Icon Image File | Designates the image file of the app's icon. If you designate nothing, Nexacro Platform's default image will be applied. You can designate either one compressed file (ZIP format) that contains multiple image files or each image file separately. |
3 | Splash Image File | Designates the file of app's splash image, which appears at the launch of the app. If you designate nothing, Nexacro Platform's default image will be applied. You can designate either one compressed file (ZIP format) that contains multiple image files or each image file separately. |
If you designate a compressed file, you should name the directories and files in the compressed file as defined in the below table.
ic_launcher.png: icon image file
splashimage_phone_landscape.png: splash image file for the landscape orientation
splashimage_phone_portrait.png: splash image file for the portrait orientation
If directories and files are named falsely, the build process may fail. Even if the build process is completed, the app may fail to work properly.
Directory | file name | Image Size(px) |
|---|---|---|
drawable-hdpi | ic_launcher.png | 72x72 |
splashimage_phone_landscape.png | Changing in response to screen sizes | |
splashimage_phone_portrait.png | ||
drawable-ldpi | ic_launcher.png | 36x36 |
splashimage_phone_landscape.png | ||
splashimage_phone_portrait.png | ||
drawable-mdpi | ic_launcher.png | 48x48 |
splashimage_phone_landscape.png | ||
splashimage_phone_portrait.png | ||
drawable-xhdpi | ic_launcher.png | 96x96 |
splashimage_phone_landscape.png | ||
splashimage_phone_portrait.png | ||
drawable-xxhdpi | ic_launcher.png | 144x144 |
splashimage_phone_landscape.png | ||
splashimage_phone_portrait.png | ||
drawable-xxxhdpi | ic_launcher.png | 192x192 |
splashimage_phone_landscape.png | ||
splashimage_phone_portrait.png |
Signing Info
Select a signature out of the list defined in the Signing option of App Builder. The selected signature will be used in building the app.
User Library
Select libraries out of the list defined in the User Library option of App Builder. The selected libraries will be used in building the app.
Android Permission
Select permissions for Nexacro Platform device APIs. By clicking the + button, you can open the whole list of the device APIs. After selecting necessary permissions, click the OK button.
You must enter keys additionally when you use the Map and X-PUSH APIs. When you select the permissions for the X-PUSH APIs especially, you must attach a Firebase Android config file (google-services.json).
iOS platform
Category | Description | |
|---|---|---|
1 | Project Modification | Based on the created App, you can export a project that can be edited in Xcode. By contrast, you can import a project that has been edited through Xcode. |
2 | Build configuration | Selects a target software development kit (SDK) and designates an icon and splash images |
3 | Signing Info | Selects a signature |
4 | User Library | Selects user libraries |
Build configuration
Category | Description | |
|---|---|---|
1 | Minimum SDK | |
2 | Icon Image File | Designates the image file of the app's icon. If you designate nothing, Nexacro Platform's default image will be applied. You can designate either one compressed file (ZIP format) that contains multiple image files or each image file separately. |
3 | Splash Image File | Designates the file of app's splash image, which appears at the launch of the app. If you designate nothing, Nexacro Platform's default image will be applied. You can designate either one compressed file (ZIP format) that contains multiple image files or each image file separately. |
You should name the icon and splash image files as defined in the below table.
file name | Image Size(px) | Description |
|---|---|---|
Icon.png | 57x57 | Home screen on iPhone/iPod touch (iOS 6.1 and earlier) |
Icon@2x.png | 114x114 | Home screen on iPhone/iPod Touch with retina display (iOS 6.1 and earlier) |
splashimage_pad_landscape.png | 1024x768 | Splash image file for the landscape orientation in iPad. |
splashimage_pad_portrait.png | 768x1024 | Splash image file for the portrait orientation in iPad. |
splashimage_phone_landscape.png | 960x640 | Splash image file for the landscape orientation in iPhone. |
splashimage_phone_portrait.png | 640x960 | Splash image file for the portrait orientation in iPhone. |
splashimgae_phone5_landscape.png | 1136x640 | Splash image file for the landscape orientation in iPhone. |
splashimgae_phone5_portrait.png | 640x1136 | Splash image file for the portrait orientation in iPhone. |
Signing Info
Select a signature out of the list defined in the Signing option of App Builder. The selected signature will be used in building the app.
User Library
Select libraries out of the list defined in the User Library option of App Builder. The selected libraries will be used in building the app.
macOS platform
Category | Description | |
|---|---|---|
1 | Project Modification | Based on the created App, you can export a project that can be edited in Xcode. By contrast, you can import a project that has been edited through Xcode. |
2 | Build configuration | Selects the minimum software development kit (SDK) and designates an icon and splash images as well as an Apple Disk Image (DMG file). |
3 | Signing Info | Selects a signature |
Build configuration
Category | Description | |
|---|---|---|
1 | Minumum SDK | |
2 | Icon Image File | Designates the image file of the app's icon. If you designate nothing, Nexacro Platform's default image will be applied. The extension of the image file is ".icns". |
3 | Splash Image File | Designates the file of app's splash image, which appears at the launch of the app. If you designate nothing, Nexacro Platform's default image will be applied. |
4 | Dmg Image File | Designates the file of an image that appears at the installation of the app. If you designate nothing, Nexacro Platform's default image will be applied. |
If the dots per inch (DPI) of the designated DMG file is not 72X72, the background image may appear distorted in macOS 10.7 or later.
Signing Info
Select a signature out of the list defined in the Signing option of App Builder. The selected signature will be used in building the app.
If you select "none", the app will be built without a signature. Although the app is successfully built, you should change the security-related settings after installing and launching the app.
Project Modification
If you need functionality that is not supported by App Builder, you can export a created App in the form of a project so that you can add necessary features or edit the project through development tools of each OS. Access the menu [Project Modification] to export the current App as a compressed file or import a project that was edited through another development tool.
Button | Description | |
|---|---|---|
1 | Export | The current App project will be exported as a compressed file. |
2 | Import | A user-modified project will be imported and added to the current App project. |
3 | Revert | The state of the current App project will return to the data saved in App Builder. |
If you click the Import button, the below dialog will appear to prompt you to select either Yes or No. Your selection will decide how to import a modified project.
Selection | Description | |
|---|---|---|
1 | YES | Maintains the state of the imported project, which has been edited through another tool. - Deactivates the configuration windows of each platform of the project. - While you can change the common configuration, the changed settings will not apply to the platform of the imported project. |
2 | NO | Does not maintain the state of the imported project, which has been edited through another tool. - Activates the configuration windows of each platform of the project. - Apps are built with the configuration specified on the console screen of App Builder applied to the imported project. |
Build App
If you try to build apps with a newly created App, the "Start to build" button will appear. When the button is clicked, App Builder starts to build apps for the selected OSes.
When the build operation finishes, results will be displayed. If App Builder successfully builds an app, a link will be created to enable you to download the created app. App Builder allows you to re-build all the apps of selected OSes by clicking the "Rebuild All" button or to re-build a specific app among them.
Description | ||
|---|---|---|
1 | Download | Allows you to download the installation file of the built app. |
2 | QRCode | Displays a URL and QR code that allow you to download the installation file of the built app. |
3 | rebuild | Re-builds the app of the relevant OS. |
4 | view log | Allows you to check the logs of the process of building the app. |
5 | Last Build Time | Displays the time when the app was last built. |
6 | Success of the build | Displays whether the build is a success or fail. "O" indicates a success while "X" means a fail. |
If you change settings in the management console, you should click the Save button before building apps. Otherwise, the unsaved change will not be applied when apps are built.
Installation files are named according to the below rules. The "App Tile" and "Build mode" options are set in the App Info stage.
Android: [App Title]-[Build mode].apk
iOS, macOS: [App Title].ipa
eg) sample-debug.apk, sample.ipa
App names displayed on mobile devices follow just the value of the App Title option.
You may face a problem if users try to download your app through Google Chrome by scanning a QR code provided by your app. When users scan the QR code to enter the URL for downloading your app, "downloadFile.do" or "downloadFile.htm" is written in the address bar of Chrome. However, the download will not be performed. The below measures are solutions to such a problem.
- Clear cache in Google Chrome
- Update Google Chrome to the latest
Upload Resources onto Deployment Server
Once app build is done successfully, the "Deploy" button will appear at the top right side of the management console. This button enables you to deploy resource files through a server other than the App Builder server by allowing you to upload resource files onto the other server.
This section explains a case in which you designate another server for the Nexacro Project URL option in the Build configuration stage.
If you click the Deploy button, you can see the list of the deployment servers designated by the administrator. After you select one of them and click the Ok button, the resource files will be uploaded onto the selected server. Afterward, a result message will be printed about whether the upload has been successful.