LocalStorage VS Blazor.FileSystemAccess

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

I would say the short answer is no. On desktop Chromium, you can use the File System Access API, and that's easy enough to use from Blazor, but on Firefox, Safari, and mobile Chromium, that API won't give you the real file system but rather a sandboxed one.

GitHub: https://github.com/KristofferStrube/Blazor.FileSystemAccess Demo: https://kristofferstrube.github.io/Blazor.FileSystemAccess/MemeGenerator

Repo: https://github.com/KristofferStrube/Blazor.FileSystemAccess