Data storage is a vital function for applications that want to monitor user progress, enable login or perform various other functions. There are a variety of methods to store user data, but the best solution depends on the type of problem you’re trying to solve.

Local storage is a fantastic way to store small amounts of information, such as login and user registration details that don’t require instant syncing. However, it is limited by the size of the device’s hard drive and is only accessible via client-side code (and cannot be modified through server-side scripts). Local storage is also susceptible to losing data if an application is removed, or if the device is reset.

The database storage is perfect to store large amounts of data that will need to be edited. You can keep track of the data of your users by storing an identifier that is http://www.virtuadata.net/how-to-service-your-own-computer unique and then referencing it when you access the database. This approach is more complicated than others, but is a great option for large enterprise applications or large apps that need to store user data over multiple sessions.

WebView2 uses UDFs to save information from the browser, like cookies permissions, cached resources. This data expires in accordance with the user’s Web & App Activity settings. It’s also possible to be manually cleared by the user using actions on Google. To store additional information about users it is necessary to define an appropriate UDF location which has Write access to the WebView2. See the WinUI 3.cs file in the WebView2Samples repo for an example of how to do this with ICoreWebView2Environment7.