blazor-wasm-maui-winforms-wpf-template VS MudBlazor

Next I decided to make a Windows desktop version using WebView. I also made a template https://github.com/Jinjinov/blazor-wasm-maui-winforms-wpf-template that is now somewhat obsolete. The biggest problem is loading the data from IndexedDB before the app starts. Blazor WASM allows you to use JsInterop right from the moment you register your services in dependency injection, so you can access IndexedDB immediately, load the user settings and then start the app. WebView doesn't allow you to use JsInterop before Blazor is initialized. This means that if the user chooses a dark UI theme and you save that choice in IndexedDB, the app will load with the default light UI theme, you will read the IndexedDB on the first render and then apply the dark UI theme. The app will flicker for a second.

I made a template for a cross platform Blazor project: https://github.com/Jinjinov/blazor-wasm-maui-winforms-wpf-template But it is a bit outdated now.

Our website is updated as well: MudBlazor - Blazor Component Library

Though I can't develop beautiful UI and good UX even if my life depended on it. I can write a functional front-end, but don't expect it to be pretty. I usually ask for assistance regarding that from our UX designers instead where they essentially layout the whole UI (either on figma or Photoshop) so I just need to make it functional. Component based frameworks these days (JS, and Blazor) really helps at least. The UX guys usually make sharable base components that the company needs (buttons, grids, etc...), which includes all the styling and animations and we use those instead to create decent looking UI. For personal stuff I use MudBlazor which kinda does the same, but I do know a bit of css to customize when needed.

There are a ton of component libraries out there. I like the mudblazor library. https://mudblazor.com

There are grid controls from the usual commercial vendors like Radzen and Telerik. I used them briefly during a free trial. It has a funny name, but MudBlazor [1] has been the MIT licensed library I have been using lately. I have been using their Table control, which may be what you are looking for in a data grid. [2] Check it out and see.

[1] https://mudblazor.com/

[2] https://mudblazor.com/components/table#api

It seems to be a known issue a known issue. By default, external libraries such as MudBlazor are not trimmed

I recommend Mud blazor if you're going for Material design. For other design languages Andt Blazor's pretty polished and there's Blazorise as well if you want to be flexible (it supports Antd, Bulma, Bootstrap and Material via configuration).

The ones I've used that's pretty good are MudBlazor (Material Design), Antd blazor (Antd), and Blazorise (Multi design support via configuration). There's also the newly announced Fluent UI for Blazor at MS build that's from MS themselves but I haven't tried it yet.

There's Uno that's been talked about by MS community standups if you wanna use UWP XAML to do the Job. If you wanted to use Blazor though, you'll have to at least learn a bit of CSS and Html. Luckily you can find really nice component libraries like mudblazor that does a lot of the nitty gritty html + styling for you. So you'll just have to use their components most of the time and with little to no JS required (depending in your usecase).