Manage Applications
Digital.ai App Management supports a wide variety of mobile apps. To make an app available to users in your enterprise App Catalog, you add it to your company's account. Once the app is available in the Admin Portal, you can use a variety of features to secure, distribute, manage, and update it for your entire organization.
Supported Application Types
The following table describes the types of apps you can manage with Digital.ai App Management.
Type | Description |
---|---|
Native Apps | A native app is an app built for a certain mobile device platform and must be downloaded and installed directly onto the device. For a list of supported devices, see Supported Platforms. |
Hybrid Apps | A hybrid app delivers a web app as part of a native iOS or Android app. Like any other native app, users will need to download and install the app on their devices before they can run it. The web app will display in an embedded web view that provides access to the app functionality without all the features of a fully developed browser. For example, users will not see an address bar that reviews the URL of the web app. Because a hybrid app is a native iOS or Android app, you can apply policies to it, sign it with Digital.ai App Management, and perform any other functions available for native apps. For more information, see Hybrid Apps (Delivering a Web App as a Native App). |
Public Apps | Public apps include the following: - Web App: An app accessed through the mobile device's web browser. A web app does not need to be downloaded and installed on the device. - Native apps and web apps available from the following public app stores: - Apple App Store: An iOS app available for download from the Apple App Store. - Google Play: An Android app available for download from Google Play. - Microsoft Store: A Windows app available for download from the Microsoft Store. |
Config | A config app is an iOS config file built with the iPhone Configuration Utility. |
You also use Digital.ai App Management to manage your App Catalog apps. Every Digital.ai App Management account comes with an web App Catalog which is automatically added to your account when you register your organization. For more information, see Add or Update an App Catalog.
Associating Screenshots and Media Files
When you add an app, you can upload up to five screen shot images that will display in the App Catalog when the user displays details about the app. You can also upload any number of media files to support the app. For example, you can upload a training guide in PDF and a training movie file in M4V format. Media files will be streamed when viewed by users. For a list of the suggested media file types, see Media File Types.
Specify Custom Metadata
When you add an app of any type, you specify standard metadata about the app such as its name, version, version notes, and a short and long description. Your organization can be configured so that you can also specify custom metadata about each app. For example, say your organization is a university and you manage multiple apps for students and faculty. You can use custom metadata to store values for School, Major, Year of Study, Campus, and so on.
In order to specify custom metadata, first you define a custom metadata template on the Settings page. Once that template is defined, a Custom Metadata section will display on both the Add New Application and Edit an Application pages so you can specify the metadata when adding/editing apps. You will also be able to view any custom metadata associated with an app on the app's details page in the Admin Portal.
For more information, see Application Custom Metadata.
Controlling Access to Applications
With user groups, you control the apps to which each of your users has access. For example, if an app is assigned to the Sales group, only members of the Sales group will have access to that app in the App Catalog. If you are supporting multiple mobile platforms, Digital.ai App Management determines which apps are appropriate for the user's device. For example:
- You add three "Expense Account" apps to your account; one to support each of these mobile platforms: iOS, Android, and Windows 10.
- Members of the Sales group are authorized to use all three of the Expense Account apps.
- A user in the Sales group installs the App Catalog on his iPhone. From the App Catalog, he can install the Expense Account app for iOS devices. From his device, he does not have access to the Android or Windows 10 versions of the app.
- Another user in the Sales group installs the App Catalog on his Android tablet device. From the App Catalog, he can install the Expense Account app for Android devices. From his device, he does not have access to the iOS or Windows 10 versions of the app.
- A third user in the Sales group logs in to the web App Catalog on his Windows device. From the App Catalog, he can install the Expense Account app for Windows devices. From his device, he does not have access to the iOS or Android versions of the app.
You can temporarily disable an app so that it does not display in the App Catalog for any users. This is useful when, for example, an inspection of the app is pending and you do not want users to access it until it has been deemed safe and reliable.
Managing Multiple Versions of an Application
You can manage multiple versions of a single native app. Digital.ai App Management stores a new version whenever you upload a new app file. With iOS and Android hybrid apps, Digital.ai App Management stores a new version whenever it builds the hybrid app (which it does when the hybrid app is first added or any time you edit the app and specify the Rebuild option). Digital.ai App Management can store up to 10 versions of the same app.
Typically, you will want your App Catalog users to have access to the "latest and greatest" version of an app—but there are times when you may want to assign a previous version, or assign different versions to different users. For example, if you have a new beta version of an app, you can get it into the hands of your Test group only while continuing to provide all other users with the previous "production-ready" version. For more on other typical use cases and guidelines for working with multiple versions, see Application Versions.