LiveCharts2 VS Avalonia.FuncUI

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

For those interested in .NET languages with alternative compilation targets, Elmish (https://elmish.github.io/elmish/) is pretty unique.

We use F# on the front end (instead of TS), and thanks to the Fable compiler (which transpiles F# to JS, Python, Dart, PHP and Rust), most of the benefits of an Elm-style model in the UI can be ported to all sorts of different outputs languages. The rust target is in beta, but its promising because the WASM bundle size stands to be dramatically lower.

While the default is reactivity library for Elmish is React, you can swap in Avalonia/FuncUI (https://github.com/fsprojects/Avalonia.FuncUI) pretty easily as well.

The code to declare/build the widgets is quite nice. Modifying widgets by hand on certain signals or manually re-wiring all the signals seems a bit outdated to me.

Wonder if something like FuncUI [1] could be built on top of it.

[1] https://github.com/fsprojects/Avalonia.FuncUI

OTOH, if desktop really is the primary focus, and if you can drop the idea of reusable UI code, then Avalonia is a great choice for F# as you can use a Avalonia.FuncUI and/or Elmish.Avalonia.

And one more MVU for you https://github.com/fsprojects/Avalonia.FuncUI

You might want to check out Avalonia.FuncUI, which lets you use F# and the cross-platform Avalonia framework to build desktop applications with an Elm-like architecture: https://github.com/fsprojects/Avalonia.FuncUI#example-using-...