Generating native mobile apps
After you have successfully developed the mobile app in Pega Platform™, you generate an installation package for the native mobile app that you can then test and distribute. The first step in this process is to obtain native platform certificates that sign the app. With the certificates, you can install the app on your device and, for example, enable push notifications.
- Android certificate set
A certificate set defines certain parameters of the mobile app for Android that you are creating.
- iOS certificate set
A certificate set defines certain parameters of the mobile app for iOS that you are creating.
- Mobile certificates page
From the mobile certificates landing page, you can view all the defined certificate sets for the Android or iOS mobile platform. You can edit a certificate set by clicking it. You can also create a certificate set from this page by clicking Add certificate set.
- Generating installation packages
Convert your application into an app that users can install on their mobile devices. You can generate both Android and iOS apps, which helps you meet the needs of a wide array of mobile users.
- Exporting an unsigned iOS app
After you build a Pega Platform application, you can export a mobile app in a form of an unsigned xarchive.zip file. This way, you can sign your mobile app locally in a development environment of your choice. When you sign your mobile app locally, you do not upload a signing certificate to Pega Platform, and therefore do not violate your company's security policies.
- Selecting a specific client version
When you build a mobile app for the Android or the iOS platform from the Channels and interfaces form, you can select a specific version of the client, for example, to avoid compatibility issues with the devices that are used in your organization, or to test unreleased functionality offered by future releases of the client.
- Setting up an alternative host
In the advanced settings for a mobile app, you can set up the app to connect to a specific URL that points to the same instance of the Pega Platform servlet, or an identical copy of the servlet. This way you can distribute the workload between servers or redirect users from different regions or subsidiary companies to URL addresses that correspond to their location.