Data storage is an essential feature for applications that wish to track user progress, facilitate login or perform various other functions. There are many methods to store user data however the most efficient solution will depend on the problem you’re trying solve.
Local storage is great for storing small amounts of data that don’t require instant sync, like login and registration details for users. However, it is restricted by the size of the hard drive and is only access via client-side software (and cannot be modified by server-side scripts). Also, local storage is prone to loss of data if the application is removed or the device is reset.
The database storage is perfect to store large amounts of data that will need to be edited. It enables you to keep track of the data of your users by recording their unique identifiers into an existing database table, and referencing that identifier when accessing the database. This is more complex than other data storage options, but it can be a good fit for large or enterprise applications which require storing the user’s data across multiple sessions.
WebView2 stores browser data using UDFs. This includes cookies, permissions and cached resources. This data expires in accordance with the user’s Web and Application Activity settings. It can be cleared manually via Actions on Google. To store additional information about users, you must specify a custom 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.