Been using this in production for years now (although we target just Windows and MacOS so I don't have experience with it on Linux). It is buggier than WPF and

Been using this in production for years now (although we target just Windows and MacOS so I don't have experience with it on Linux). It is buggier than WPF and has occasional annoying issues when you update to a newer version, but it's still too good for us not to use compared to .NET-based alternatives. We've been using it more and more over time. Just keep in mind, this is all custom rendering, it is not a native control wrapper. If you want an app that will look like a normal MacOS app on the Mac, this may not be the best choice, and something that wraps native controls (like Xamarin) would likely work better. If you want a UI that looks the same everywhere, it's great. One advantage is that it works in a very "sane" way - you're just writing a net core app, that's all there is to it, unlike with Xamarin. A disadvantage/advantage (based on your perspective) is that this is just a UI framework, so you don't get .NET wrappers for all the other, non-UI platform stuff that Xamarin provides. If you need some platform functionality, you have to access that in some other way.