LocalStorage VS BlazorWithFluxor

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

Note: For demonstration purposes I have hooked in the Blazored.Toast component to pop up a Toast message whenever the CounterState is saved or retrieved, as demonstrated in the previous post in this series. For brevity's sake I'm not including that code in this post, but you can find it all in the project's repository on github.

After all of these steps, the solution should look like this branch of the demo repository.

Before we begin: The code for this blog series can be found on github as shown below. To check your progress for this step of the series, view the 002_Add_Fluxor_Libraries branch.