EstEID.Blazor VS MudBlazor

If I understand correctly you can have make a class that gets initialized on startup. For singleton the constructor can have a task that wont resolve which isnt ideal but will work. How many queries you make to the database then is your own to implement. For example lets say we use entitiyframework. You can make a permarunning task in a singleton class constructor that will just keep some data in memory. Then that Task calls the savechanges() every one hour. If there is a power outage obviously you will have hour lost of data but thats not the question. That class will get initialized on program startup and will keep running until you shut it down. I did long ago a tool to read data from Smart Cardsthat utilized a singleton class to fire events and then blazor to use as UI. The idea is that since there is ever only 1 instance of that class the events fired will propagate to every subscriber. This way you can have a client to display data, a client to say log info etc. Similar approach can be used to handle data in your case. You can attach several "screens" through browser to make same data be displayed in several locations etc. The public bit i can share as an example is here: https://github.com/elraito/EstEID.Blazor. It is trivial to track when something gets initilized or fires since we do have console.writeline() :)

I don't think that new Identity pages will work with MudBlazor out of the box. Take a look at this GitHub issue: https://github.com/MudBlazor/MudBlazor/issues/7805

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/

I'm creating a Blazor MAUI project using MudBlazor, and I'm looking for a way to refresh a page on Android using the pull to refresh feature. By now the best result I've found is to surround all the with a tag as shown here but this would mean refreshing the whole content on the page, NavMenu included. I've also tried to implement the BcdLib/PullComponent: with this one I can refresh only the body of the page but I can't achieve a smooth refresh animation like in the first method.

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/