awesome-avalonia

WPF and Xamarin dev here who wrote a new (not ported) codebase on Avalonia. - Avalonia has a guide just for people like you and me [1]. - Avalonia's flavor of XAML has small divergences from WPF that will have you hitting their docs often. There are some nice quality-of-life improvements, for example you can bind a Button click handler directly to a method without ICommand. The major concepts are the same e.g. data binding, dependency properties. - Coming from WPF, it's possible you've used MVVM and dependency injection. You'd be going against a strong cultural grain to not use them in Avalonia. But I would be surprised if your WinForms app is architected like that, so it may be a design challenge extracting coherent ViewModels and properties from the ball of mud that many WinForms apps become. - For macOS, read up on notarization [2] and

.NET is big for mobile app development, particularly when you include Unity. It's really one of the best solutions for writing Android + iOS apps, where you can share a significant amount of code and still have native-looking apps. You don't need to depend on clunky electron which makes your apps huge. .NET apps are smaller and faster than electron based apps. Swift is probably a common choice these days, but wasn't an option a few years ago. Unity is used by a huge number of mobile games and uses C#. The Godot engine also supports C#. On desktops not as much, but it is sometimes used for cross platform development, and plenty of games on Steam are written in Unity and run cross platform. Linux desktop could have had a better story when MonoDevelop was gaining popularity, but Linux/desktop support basically got sidelined when Xamarin shif