This article describes the terms that you will encounter while using Progress AppManager or reading this documentation site.
The iOS App ID uniquely identifies an application with the Apple application services and lets you incorporate them in your app. The Apple application services include Push Notifications, In-App Purchase, Game Center, etc.
You can register an App ID in the iOS Dev Center only.
The bundle identifier is used to uniquely identify an iOS application. The bundle identifier is defined by the app author as a reverse URL that must be registered with Apple. It is used to recognize updates to an iOS app.
After you define the bundle identifier for an app, you cannot modify it.
The Unique Device Identifier (UDID) uniquely identifies an iOS device. You need to provide it when you register an iOS device to your Apple developer account. To manage your registered devices, go to the iOS Dev Center.
An Apple Watch bundle consists of three components—a host app running on your iOS device, a WatchKit extension which takes care of the communication between the iOS device and the Apple Watch and a watch app running on the Apple Watch. When you install an IPA that is an Apple Watch bundle, your iOS app has Apple Watch capabilities.
To code sign an iOS application, you need a public key certificate signed by Apple as the certificate authority. A public key certificate contains information about the developer identity and a public key to decrypt anything encrypted with the private key of the developer. To manage your certificates, go to the iOS Dev Center.
Development certificates are used to code-sign an application during development to be able to run it on an iOS device. You cannot publish apps signed with a development certificate in AppManager.
With a production certificate, you can code sign an app for publishing on AppManager and for distribution to specific testing devices. You can assign a production certificate to a distribution provisioning profile only.
Your certificates are embedded inside a provisioning profile.
The provisioning profile is stored as a
mobileprovision file. This file contains information about the identity of the app's author, the identity of the app, and its distribution purpose. To manage your provisioning profiles, go to the iOS Dev Center.
To publish an app to AppManager, you can use an ad hoc distribution provisioning profile or an in-house distribution provisioning profile.
An IPA file is an iOS App Store Package. If you extract it as a ZIP file, inside the archive, you will find an
.app folder which is the actual application.
The package identifier uniquely identifies an Android application. The package identifier is a user-defined reverse URL. For more information about package identifiers, see Android Manifest. Each part of the package identifier should start with a letter. The package identifier is used to recognize updates to an Android app.
APK file is an Android package file. APK files are used to distribute apps for the Android operating system. If you extract it as a ZIP file, you will find all app resources, including the Android Manifest file.
An APPX file is a Windows Phone package file. APPX files are used to distribute apps for Windows Phone 8.1 and later. If you extract it as a ZIP file, you will find all app resources.
A XAP file is a Windows Phone package file. XAP files are used to distribute apps for Windows Phone 8.0 and 8.1. If you extract it as a ZIP file, you will find all app resources.
To be able to distribute Windows Phone apps outside of the Windows Store, you have to obtain an Enterprise Mobile Code Signing Certificate. You will need to provide this certificate when you resign the AppManager Windows Phone Hub App and when you publish all your store apps afterwards. This certificate is intended for in-house distribution only.
The Application Enrollment Token or AET is a token file that is used to enroll devices for app distribution from a certain enterprise certificate. A user has to enroll his device with an AET to be able to install an enterprise Windows Phone app. If you have resigned the AppManager Windows Phone Hub App with your enterprise certificate, AppManager will automatically generate and distribute an AET for all published Windows Phone apps.
Windows Phone apps use an auto generated GUID like Product Id as an application identifier. This is what the Windows Phone OS tracks to identify apps and app updates. However, since iOS and Android are using package names as unique identifiers, AppManager uses the app Assembly Name to uniquely identify a Windows Phone app. AppManager needs both the Product Id and the Assembly Name to be the same to identify two apps as the same app. If the two apps have different versions, then AppManager will identify them as different versions of the same app.
The AppID is used to uniquely identify your application on a user's device. It is a part of the package file's manifest and is usually provided in the form of a reverse URL. In AppManager, AppID is the bundle identifier of an iOS app (and not the iOS App ID) or the package identifier of an Android app.
When distributing an app created in AppBuilder, the AppID must match the app's Application Identifier value.
A user is anyone who uses the AppManager mobile app to view and install the apps that you distribute through AppManager on their devices. In the context of AppManager, a user can also be referred to as group member in the context of distribution groups. To make someone a user of your AppManager account, you need to send them an invitation from App Distribution Portal.
Distribution groups are a way to give access to different users of your account to different apps. A distribution group is a group of users that have access to a defined set of applications. The App Distribution Portal administrator defines both the members of a group and the apps that are available to that distribution group.
The App Distribution Portal is the web back end of AppManager. After you open App Distribution, you can distribute apps and manage users of your AppManager account.
The AppManager mobile app is an iOS/Android/Windows Phone app that serves as a client of AppManager. Using it, users of your account will be able to download the apps that you distribute to them.
The AppManager web catalog is a mobile web app that serves as a client of AppManager. Your users can open it in their mobile browsers to view and install apps, or edit their profile information.
The AppManager email distribution is the default distribution method of AppManager. Every new account member receives an email containing all apps available to them along with links to their download pages. Furthermore, if a new app or app update is published in the account, all members who have access to it will receive an email with a link to the new app's download page.
Publishing an app in AppManager makes it available to members of all distribution groups who have access to the app, use compatible devices and have the AppManager mobile app installed. If you only add an app to AppManager but do not publish it, no one will be able to see it.