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

But I think some of this stuff is already handled in Avalonia ecosystem like https://github.com/Mapsui/Mapsui, https://github.com/beto-rodriguez/LiveCharts2 and few others...

As far as Uno Platform goes, one can use components from WinUI and Windows Community Toolkit (WCT); so you have hundreds of UI components to work with out of the box, including some must-haves like Data Grid in WCT. Some bigger component vendors have put out their betas i.e. https://www.infragistics.com/products/uno-platform or https://www.syncfusion.com/blogs/post/syncfusions-first-control-for-uno-platform-charts.aspx . I do agree this 3rd party ecosystem eventually needs to get more love from bigger vendors, or other new ones will also step in - i.e. Live Charts has support for Uno Platform https://github.com/beto-rodriguez/LiveCharts2 or MapsUI https://mapsui.com/documentation/getting-started-uno.html

It is beta now, but should be ready for production soon, The library will also provide multiple ready-to-go themes and a high-performance package.

LiveCharts2 is a charting library completely written in C# and it is a full rewrite of LiveCharts, now LiveCahrts can run everywhere MAUI, Uno Platform, Avalonia, Xamarin, WPF, WinForms, WinUI, console and on the server side.

Apex charts will definitely do the job This is one alternative I found while digging yesterday: https://github.com/beto-rodriguez/LiveCharts2

Live charts is a cross platforms charting library .Net, to get started go to https://lvcharts.com and take a look at the instalation guide of your target platform the web site contains all the samples provided in this repo, docs and more.

try version 2! https://github.com/beto-rodriguez/LiveCharts2

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.