To a point. Making cross platform native desktop apps is still in the hands of 3rd party vendors such as Avalonia and Uno. MAUI was supposed to fix that oversight to a less than stellar results.
So this "it's all for backend now" notion is surprising.
That's what you have to compare against, and .NET/C# falls flat.
C# and F# get to enjoy the integration that is "much closer to the metal" as well as much richer cross-platform GUI frameworks ecosystem with longer history.
Win32? Silverlight/Blend? XAML? MAUI? They're all windows only.
Gtk? Qt? Sure, they exist, but they're ancient and limited to long outdated paradigms.
I don't know if you can get QtQuick with KDE Kirigami to work on .NET, otherwise that might be one option.
Kotlin Multiplatform is btw a solution for building the same code for kotlin native, JVM and web to target all the OSes at the same time.
While Jetpack Compose is the Android Version of Compose, Compose Multiplatform is Compose for Kotlin Multiplatform.
> subject to the quirks and specifics of JVM implementations, build-systems and package management
That's a massive advantage over the arcane package management and build systems of .NET
Very few languages ever achieve a build and package management system as mature and usable as the Java ecosystem.
I've been waiting for 12 years for .NET to match Java's ecosystem, and it's still not there yet.