What kind of data can be used in "Local Storage" in OutSystems Mobile apps?

In OutSystems Mobile applications, local storage is designed to manage data that should persist across app sessions, making it ideal for non-sensitive data such as user preferences, settings, or cached results. This type of data must remain available to the user even when the app is closed and reopened, thus necessitating a storage solution that retains information between sessions.

Using local storage for non-sensitive data allows for efficient app performance and user experience, as it avoids the need for continuous server communication for frequently accessed information. This technique helps to minimize load times and enhances the usability of the app for end-users. While local storage can technically hold a wide variety of data, it is geared toward this specific purpose of retaining user preferences and similar lightweight data effectively.

Other types of data, such as sensitive information requiring encryption, are better handled via secure storage mechanisms provided by the platform. Temporary data for session-specific tasks is typically managed in-memory, meaning it does not need to persist across app restarts. Finally, data requiring frequent real-time updates would be more effectively managed through persistent connections or APIs rather than local storage, which is not optimized for such dynamic requirements.