App Maker is the website that enables creating and publishing mobile applications. This document explains the product’s functional capacity by using partner, developer, and brand terminology.
Latest deployments and changelogs are displayed in this section.
You can create projects for more than one brand on the App Maker.
To create a new project, access the product and click “Projects” on the drop-down menu to the left. This screen lists all the projects of the Partner.
To create a new project, click the Add New Project button.
To create a new project for a Partner, an authorized user needs to follow the steps of adding a project. Initially, the user should fill in the related fields on the project details page.
- Project Name: The name of the brand can be used. Should be unique.
- Project Type: Select a project for your application from among the automatically listed application types.
- Product: Select a type for your application from among the automatically listed application types.
- Description: Enter detailed information about your project.
Then click the Create button. You will be directed to the Projects screen.
The user makes the necessary configurations by proceeding to the details of the created or current project. Configurations are divided into four categories: Integration Maps, Static Files, Static Text Maps, and Application Settings.
Enables the definition of endpoints with Omnitron backend.
Enables the editing of many fields within the application such as icon, font, logo, or splash screen image upload.
Static Text Maps
Provides access to the pages within the application. The language translations of the static texts on this page are entered here.
To configure, switch from Master to Dev mode. Click the “+” icon next to the area to be edited. Enter the code for the language to be added and press Enter. Write/edit the content based on its equivalent field. When finalized, click the Save button.
Enables the management of modules and packages within the application.
Difference Between Dev/Master
In Master mode, Project Configurations are seen as read-only. In order to make changes in the configurations, switch to Dev mode.
An IMPORT button is displayed to edit a Json Field.
Click the IMPORT button to import JSON on the displayed modal.
An Edit button is displayed to edit a File Field.
Click the Edit label and upload the file with the Upload button.
A Milestone Toggle Field is edited with a switch button. Click the Save button when editing is complete.
Functions of Act / Tag / Doc Buttons
The Act button lists the changes in that field. This field behaves the same way in Dev and Master modes.
The Tag button displays the tags defined in Master mode and enables the addition of new tags in Dev mode.
The Doc opens the documentation modal defined to that field.
Project Management is divided into five categories: Project Packages, Config Packages, Available Versions, Branch Changes and Legacy Versions.
If there's a new project package uploaded, will be displayed in this section.
This is the field where the project’s config files are downloaded manually.
If there’s a more up-to-date version of the project, an Upgrade Version button is displayed and can be clicked to update. If there are any unmerged changes, the user needs to merge those first before upgrading the version.
If any new changes are made, a Merge button is displayed and can be clicked to merge.
This is the field where you can view older versions in read-only mode and manually download the config files of older versions.
The filtering area on the Project Credentials page selects Production/Staging and iOS/Android. The items listed based on filtering selections are edited.
Open the upload modal for file upload.
Open the input field modal for value change.
Select the related rows on the table to add extension. Select Add Extension in the Selection Action field under Credentials, and click Apply. Fill in the relevant fields on the displayed modal, and click Save.
This page enables creating a new build, viewing the details of the current build, creating code push for a build, and publishing force update.
If a config value is changed under Configuration, the user needs to click the BUILD PACKAGE button under Management before creating a new build. This step is required to recreate platform configs with new configs.
To create a new build, click the Create New Build button. If Production is selected on the displayed modal, no Target Branch change can be made. It only retrieves the ones from the Master branch. If a build is to be created for Staging, Target Branch can be selected both as Master and Dev.
A new version number is entered based on the latest version in Store Version under the App App Store Connect->My Apps->Testflight tab. This will be the app version on stores.
Fill in the related fields, and click the Create button.
The iOS ve Android builds are listed on the Deployments page based on the selected Production and Stating information. Click the Create button to display a new build with the Pending status. This status is then updated based on the outcome of Success/Failed. Click the Deployment detail to access related logs. Here, the user can download the IPA file for iOS and the APK file for Android.
How to Send the IPA File to Testflight
The Transporter application is used to send the IPA file, downloaded via App Maker to Testflight. Drag and drop the IPA file into this application. Click the Deliver button to upload the file to Testflight. Please visit the link https://testflight.apple.com/ to see the flows to test on device via Testflight and to send build to review.
Steps to Follow After Publishing the Application on Store
The store status of a successful build is updated based on whether the build has been sent to the store.
Codepush can be made for builds with the store status of success. Click the Make a Code Push button. Fill in the fields on the displayed modal, and click Create.
Mandatory OFF: When the user opens the application, the application visits the akinon servers in the background and checks whether there are any new updates. If there are, the application downloads the update and, next time, opens with the new bundle. If the mandatory field isn’t activated when making a codepush for a customer on the App Maker platform, the created codepush will run in silent mode.
Mandatory ON: When the user opens the application, the application visits the akinon servers in the background and checks whether there are any new updates. When the new update is downloaded, it displays an alert to the user, with Cancel and Update buttons available.
- If the user kills the application and reopens it, it opens with the latest update.
- If the user clicks the Update button, the application restarts with the update complete.
- If the user clicks the Cancel button, the device shuts down without being updated. When the application is reopened, the new update is complete.
The reason for the Cancel button is that Apple’s App Store Review Guidelines stipulates not to force users to access the contents of the application.
Apps must not force users to rate the app, review the app, download other apps, or other similar actions in order to access functionality, content, or use of the app. If the mandatory field is activated when making a codepush for a customer on the App Maker platform, the created codepush will run in mandatory mode.
2. Force Update
After making a build on a new version and switching its store status to success, a force update can be made for the old build. The codepush that is sent when force updating older versions automatically works in mandatory mode. For this, select the older version in the Selected Version field, enter the build detail that is published, and click the Force Update button. Fill in the fields on the displayed modal, and click Create.
Click the Users menu item to add new users or to edit current ones.
The user list displays the current users in the system. The general user information is displayed in a summary table. Click the Edit icon to edit a user.
Click the Add User button on the list screen to add a new user. Fill in the required user information on the page, and assign a role to the new user. You can view role-based authorization on the Privileges table.
The roles assigned to a new user are defined on this page. The Roles page lists all the roles that have been added. Click the Edit icon to edit a role.
Click the Create Role button on the list screen to create a new role. Fill in the required user information on the page, and assign authorization to the new role.