LiveCharts2 VS Interactive Data Display for WPF

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

A short story / cautionary tale of the last time I had to add a chart to an old application: I had a project that needed to make use of Microsoft's Interactive Data Display [formerly Dynamic Data Display or 'D3']. I don't recall what feature it was that was specifically being asked for, but D3 did it and was the only real option outside of springing for one of those massive/pricey component libraries. If you want to talk about how silly it is to create an entire separate process to wedge a WPF control into a WinForms app as a MDI child, that communicated via pipes, I've got notes. In short: the tech may be dated, but I always welcome more WinForms controls.