MudBlazor VS fast

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/

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

If you are generally interested in how to write components that can be used by many frontend libraries (react/vue, etc), you should take a look at https://github.com/microsoft/fast. I was tangentially involved with porting an existing component library to it and the end result was pretty framework agnostic and well made.

Could not have articulated it better, especially when compared to other MS project sites like https://www.fast.design/. Maybe the dev or someone on the team downvoted me :/

I know FAST is not used that much but I wanted to cover it as it seems to be the only library that reflects attributes by default. By default it won't do any type coercion unless you use the mode: "boolean", which works almost like an HTML boolean attribute, except an attribute present but with the value "false" will coerce to a property value of false!

This doesn't mean you are required to write vanilla JavaScript web components either. If you are familiar with using Fast or Lit to write web components you can include those libraries in you Enhance application. However, with the introduction of Enhance base classes for the light and shadow DOM you can get the same DX improvements where you write less boilerplate web component code while enabling the sharing of a render method between the SSR and CSR rendering.

You could take a look at FAST https://www.fast.design/. I know it is not what you asked but ...

FastUI from Microsoft? https://github.com/microsoft/fast

I want to use Fast Components, so I've added the Microsoft.Fast.Components.FluentUI NuGet package and added the relevant CDN script tag to index.html.

fast- (Fast components from Microsoft8)