Data storage is an essential feature for applications that wish to track user progress, facilitate login, or perform other important functions. There are many ways to store user information, but the best choice depends on the kind of problem you’re trying to solve.

Local storage is great for storing small amounts of data Data room for deal makers that don’t require instant sync, such as login and registration details for users. However, it is restricted by the size of the hard drive and is only accessible via client-side code (and cannot be modified through server-side scripts). Local storage can also be vulnerable to losing data when an application is deleted, or if the device is reset.

The database storage is perfect for storing large amounts of data that will need to be edited. You can keep track of the data of your users by saving an identifier that is unique and then referencing it when you access the database. This is more complex than other data storage options however, it can be an ideal choice for large or enterprise applications that require the storage of the user’s data across multiple sessions.

WebView2 utilizes UDFs to store information about the browser, including cookies permissions, cached resources. This data expires in accordance with the user’s Web and App Activity settings and can be cleared manually by the user via actions on Google. You must specify an UDF that has Write access to the WebView2 in order to save additional user data. See the WinUI 3.cs file in the WebView2Samples repo for an example of how to do this with ICoreWebView2Environment7.