{"id":123,"date":"2018-01-30T07:50:41","date_gmt":"2018-01-30T15:50:41","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/implementing-offline-capability-in-your-app\/"},"modified":"2025-06-11T08:10:02","modified_gmt":"2025-06-11T15:10:02","slug":"implementing-offline-capability-in-your-app","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/implementing-offline-capability-in-your-app\/","title":{"rendered":"Implementing Offline Capability In Your App"},"content":{"rendered":"

Do you want to build offline capabilities in your PowerApps app because your app users need to access some data or save some data even when they don’t have the internet connection? This blog provides an example of building these offline capabilities in your PowerApps app. This article assumes that you already know the basic concepts of PowerApps like screens, controls, events, attributes, navigation etc. We’ll will use all these concepts in this tutorial.
\n\u00a0<\/p>\n

Note<\/b><\/h3>\n

The offline feature area is still under development and is not optimized for every offline scenario today. The functions to SaveData() to a local device and LoadData() from that device work best in their current implementation over relatively small quantities of data (e.g., dozens of text records in a table) that generally do not exceed 2MB. This is useful for some basic \u201coffline\u201d scenarios as well as to increase the startup performance of canvas apps by caching data locally. However, using this feature to save large amounts of data (e.g., saving thousands of rows in a table, or caching large images or videos) may cause errors or unexpected behavior with the current implementation and should be avoided. Also, the functions do not automatically resolve merge conflicts when a device returns to connectivity from offline \u2013 configuration on what data is saved and how to handle reconnection is up to the maker when writing expressions. We are working to expand the capabilities of offline apps to increase stability and size limits, and in the future to automatically handle decisions about what to save and how to handle conflicts. Stay tuned here and on the PowerApps blog for updates when they become available.\u00a0<\/em><\/p>\n

\u00a0<\/p>\n

Offline Requirements Of An Example Issue Reporting App<\/h2>\n

For this tutorial, let\u2019s assume we have to build a simple Issue Reporting App with the following requirements:<\/p>\n