Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adjusting the performance of offline-enabled mobile apps

Updated on February 23, 2022

Take advantage of several mechanisms that optimize the performance of your offline-enabled mobile apps.

You can use the optimization mechanisms to deal with large amounts of data that are transferred when users log in for the first time and when the mobile client synchronizes with the server after a longer period without a network connection. Additionally, you can ensure that the data that is already available on the device is accessible by the app in a way that guarantees robust and optimal performance.

For example, you can make data synchronization in your offline-enabled app more efficient by configuring data sources for your app as large data pages. Then, the mobile client pulls only the data that has changed since the last synchronization instead of the whole content of the page.

Remember: Configure service-level agreements or Wait shapes in your case flow to pause the process and guarantee that the preceding process steps do not conflict with the data synchronization's replay of the last user action. For more information about using service-level agreements and Wait shapes, see Completing work on time and Pausing and resuming processes in cases.
  • Previous topic JavaScript API for scheduling any activity in offline mode
  • Next topic Improving the synchronization of offline-enabled mobile apps with large data pages

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us