Best practices for updating mobile apps
New releases of Pega Mobile Client are as backward-compatible as possible. However, an update to the latest Pega Platform versions adds new features and enhancements to the low-code prescriptive authoring environment, in which you can develop your app. The following best practices ensure that your apps work correctly after the update.
- Follow all recommended UI and mobile app guidelines. For more information, see Designing applications for mobile use and Designing applications for offline mode.
- Update legacy mobile channels that reuse web portals to Pega Mobile Client-based channels. For more information, see Updating mobile channels that reuse web portals.
- In the UI of your application, consider replacing harnesses that include repeating dynamic layouts with mobile list pages that you can author in the mobile channel. For more information, see Authoring mobile list pages.
- Reuse the required harnesses by selecting them from the list of pages in the
navigation configuration in the mobile channel. For more information, see Adding items to the menu bar.
Note: Only components that are marked as relevant records are available for reuse as pages. For more information, see Marking a record as relevant.
- Build the navigation of your app in the mobile channel, instead of manually configuring navigation rules. For more information, see Adding items to the menu bar.
- Use SAML, OpenID Connect, or basic authentication type services instead of custom authentication services. For more information, see Authentication services.
- Define the branding and theme of your app directly in the mobile channel instead of uploading branding assets or modifying skins in your application. For more information, see Customizing the theme of mobile apps.
- Contrary to earlier Pega Mobile Client 7 versions, in new releases of Pega Mobile Client, user data is cleared when another user signs in to the app.
- In Pega Mobile Client, the app displays push notifications first on the banner at the top of the screen of the mobile device, even if the app is in the foreground.
Previous topic Updating mobile channels that reuse web portals Next topic Best practices for updating offline-enabled mobile apps