MudBlazor VS Avalonia

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

You might also want to look at AvaloniaUI[0] for a cross platform .NET GUI library. It is similar to WPF but much nicer to work with.

[0] https://github.com/AvaloniaUI/Avalonia

Do you mean accessibility? I did notice disappointing non-native-like behaviours when I tried typing in an AvaloniaUI textbox but I'm hopeful they will manage to solve that and other issues.

For example, pressing a space will always introduce a new item in the undo/redo history [0] which isn't how native textboxes work.

[0] https://github.com/AvaloniaUI/Avalonia/blob/942901c624df73b7...

Production user here. There's no money gotchas. They're above reproach. In fact, I've received considerable free support from their devs on GitHub Issues [1].

The Avalonia business model is based on selling XPF, which runs WPF (Windows-only) apps on other platforms. That's very interesting to big corps with existing codebases.

See my comment [2]

[1] https://github.com/AvaloniaUI/Avalonia/issues

[2] https://news.ycombinator.com/item?id=39246988#39249128

Not my comment, but relevant here "The problem with compiling Skia to WASM is you'll lose any benefits of hardware graphics acceleration on the device."

(From https://github.com/AvaloniaUI/Avalonia/discussions/6831#disc... )

It's a bit of a hit and miss as of today. CLI, back-end and natively compiled libraries (think dll/so/dylib or even .lib/.a - you can statically link NAOT binaries into other "unmanaged" code) work best, GUI - requires more work.

Avalonia[0] and MAUI[1] have known working templates with it, but YMMV.

[0] https://github.com/lixinyang123/AvaloniaAOT / https://github.com/AvaloniaUI/Avalonia/ / honorable mention https://github.com/VincentH-Net/CSharpForMarkup

[1] https://github.com/dotnet/maui (try out with just true in csproj - it is known to work e.g. on iOS)

For desktop, Avalonia, hands down.

https://avaloniaui.net/

Open source, powered by Skia, backed by JetBrains, and quite battle-tested at this point for small to medium-sized apps. In theory perfectly capable for enterprise as well, since it's basically a spiritual successor to WPF, which has been an industry standard for about 15 years.

They're diving into mobile and WASM well, but that's more of a recent effort and I haven't tested that yet.

> I don't see any other way to go trully multi platform without making separate UI for Android and iOS.

https://avaloniaui.net/