DnetIndexedDb VS LocalStorage

Blazor WASM was the first, original version. I wanted an app that can work offline, so I decided to save user data in IndexedDB. My first choice for an IndexedDB NuGet was https://github.com/Reshiru/Blazor.IndexedDB.Framework because it was recommended by Steve Sanderson in https://blog.stevensanderson.com/2019/08/03/blazor-indexeddb/ - and it was the worst mistake in the whole project. The NuGet loads all the data from IndexedDB into memory every time you open a connection. That made the app unusably slow after one year of use. I made a few improvements in my own version https://github.com/Jinjinov/IndexedDB.Blazor but I never solved the loading problem. I decided to rewrite the whole project from scratch, using the much better IndexedDB NuGet https://github.com/amuste/DnetIndexedDb . The original project is available at https://github.com/Jinjinov/TheLastTime and as a PWA https://old.ididit.today/ as a lesson on what mistakes to avoid.

https://github.com/amuste/DnetIndexedDb - 62 stars - 5 contributors - last commit on Jun 25, 2021

I created and 6 offline first WASM apps that are in production use now and quite complex. They all use this Library. I designed my own Sync System around it using .Net Core API CRUD but they have a fully supported Signal R WASM Client now also if you want to try it for yours. https://github.com/amuste/DnetIndexedDb/blob/master/README.md

if its like less than 30 items u can just use https://github.com/Blazored/LocalStorage

You store the token in local storage. This is a library that will give you access to that. Blazored

Blazored LocalStorage - for Tokens and Authentication Stuff

The library make use of Blazored LocalStorage for storing cache data.

I use a library called Blazored LocalStorage for the WASM project to store client side data like preferences and auth stuff. This, it seems, is not supported in MAUI. Although MAUI starts a web server, it does not store data in the 'browser'. Instead it uses an API called "Preferences" (Which is a pretty sweet interface, props MS) but now I find myself struggling how I can use one, or the other depending on the project.

I've built a few Blazor WASM apps and use Blazored LocalStorage to access it.

For Blazor, you need to either use a third-party library to set up INPC, or do this yourself. I do the latter. For example, I have a settings class. I use https://github.com/blazored/LocalStorage to store the settings in the browser, and set them up as a singleton.

If you only need key/value, I've been using this one. https://github.com/Blazored/LocalStorage