LocalStorage VS MudBlazor

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

Blazored LocalStorage - for Tokens and Authentication Stuff

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

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

To begin, let's note that the localStorage API is a JavaScript API, and isn't directly available to be called by our Blazor code. We need to either write our own JSInterop code to interact with localStorage, or we can take advantage of a library somebody else has already written. I'm going to use the excellent Blazored.LocalStorage.

The Blazor Server application uses the open source component MudBlazor, which I recommend to C# oriented developers. To keep the application simple, all data is stored in JSON files.

You could use Mudblazor and Codebeam Mud extensions.

Look up some Blazor UI / Component Libraries.Awesome-Blazor lists the more popular ones. The two I recommend are Mudblazor and Havit Blazor because the documentation is built using Blazor and the repos are open source on GitHub.

and you can use mudblazor components for free. https://mudblazor.com/

The load times and lighthouse score for the MUD Blazor site has put me off of Blazor entirely for anything public facing:

https://mudblazor.com/

If you want to consider using .Net MAUI Blazor Hybrid for your app MudBlazor is a free Material port (https://mudblazor.com/).

Try navigating to the site for the Blazor material design library, MudBlazor, on a mobile browser:

https://mudblazor.com

As much as I want Blazor to work out well, those load times are too abysmal for me to seriously consider Blazor outside of internal apps.

MudBlazor - For Styling