Term | Explanation |
Android Styles | An Android style is a collection of attributes that specify the appearance of a View object. It can be modified in the ASL Editor. Android styles have the file extension themes.asl and are stored in your_project/model/resources/themes.asl. For more information, see https://developer.android.com/guide/topics/ui/look-and-feel/themes. |
App Icons | The app icon is the icon displayed when an application starts. It can be modified in the App Icon Editor. App icons have the file extension app.icons and are stored in your_project/model/resources/app.icons. |
Application Model | The application model describes the content of your mobile application, including user interface, services, data model, and localisation. It is visualised in the Outline Editor. Application models have the file extension .aml and are stored in your_project/model. |
Asset | An asset describes the composition and style of an icon. Exporting an asset creates multiple .png icons for the desired platform to fit any screen resolution. An asset is edited in the Asset Editor. Asset files have the file extension .asset and are stored in your_project/model/resources. |
Data Model | A data model describes the entities to be used in your mobile application. It also enables an entity-to-JSON mapping. A data model can be edited in the EML Editor. Data models have the file extension .eml and are stored in your_project/model/entities. |
Jenkins Build | A Jenkins build is a Mobile Designer multi-build that is run on a Jenkins server. |
Keystore | For a description of the Android keystore, see https://developer.android.com/training/articles/keystore. |
Mobile Project | In Software AG Designer, the Package Explorer element containing all required files to build an application is referred to as a mobile project. |
Multi-Build | Building a mobile project to create the platform-specific artefacts for iOS and Android is referred to as a multi-build. |
Provisioning Profile | A provisioning profile is required to install and run an iOS application on physical devices. It is bundled within the application to provide information about the app id and development team being used as well as the devices the app is allowed to be tested on. Manage and download provisioning profiles for your projects and apps at https://developer.apple.com/account/ios/profile/. |
Sources | The Java classes, graphical, and text resources required to build the mobile application are referred to as sources. |
Target | Describes the resulting artefact type when doing a multi-build. There are the following types for Android:  Debug (Only use for debug and test purposes on your devices. The source code will not be obfuscated.)Release (Use to publish the final build. The source code will be obfuscated.)There are the following types for iOS. AppStore (Use for distribution in Apple's App Store. The final build can be uploaded to the App Store.)Enterprise (Use for inhouse distribution. The final build can be distributed within your organization.)Ad Hoc (Use for inhouse distribution for testing. The final build can be installed on a limited number of registered devices.)Dev Release (Use for testing. The final build can be installed on test devices.)Sim Release (Use for testing in a simulator. This target does not require a provisioning profile.)XCode project (Only an Xcode project will be created. Use this target if you want to use Xcode to debug an application in a simulator). |