Table of Contents

Adjusting the performance of offline-enabled mobile apps


Only available versions of this content are shown in the dropdown

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.

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.
  • Improving the synchronization of offline-enabled mobile apps with large data pages

    Ensure a smooth user experience at run time and improve the speed of synchronization after your offline-enabled mobile app reestablishes connectivity by configuring the app to synchronize only new or altered data.

  • Caching data in offline-enabled mobile apps

    Help users begin their work without unnecessary delays by enabling caching in offline-enabled mobile apps and including the cached data in the app executable files. By caching common rules and storing them in the app bundle, you ensure that the app starts faster when users launch it for the first time.

  • Disabling processing of attachments and signatures in offline mode

    Improve the performance of your offline-enabled mobile app by disabling the processing of attachments and signatures. For example, if you know that your app users do not need to work with any attachments in offline mode, you can disable attachment support.

  • Limiting offline packaging to data from the user's worklist

    Decrease the duration of data synchronization and limit the amount of data that the offline-enabled mobile app downloads, by implementing optimistic packaging for offline-enabled case types during data synchronization. With optimistic packaging, the app only packages and downloads the current flow that is active on the user's worklist.

  • Disabling server-side postprocessing in offline cases

    Avoid redundant processing of actions and increase app performance by disabling server-side postprocessing in offline-enabled cases.

Did you find this content helpful?

Have a question? Get answers now.

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