Replies: 4 comments
-
What about delay showing the main window until properly rendered? |
Beta Was this translation helpful? Give feedback.
-
WinUI3's performance is really bad.But you could not change their decision,because they don't want to discuss this issue head-on. |
Beta Was this translation helpful? Give feedback.
-
I had some other problems with WinUI3. Does anyone know if there is any UWP adapter for MAUI? |
Beta Was this translation helpful? Give feedback.
-
I think Microsoft has been listening and Maui AND WinUI3 have received a lot of stability and performance-enhancing fixes recently. Give
a chance. It is fast and stable. |
Beta Was this translation helpful? Give feedback.
-
Description
Xamarin for Windows is powered by UWP. React Native is also powered by UWP.
But MAUI is powered by... WinUI3.
For me, WinUI3 is just not good enough. It has some major issues. We are talking about old WinUI3 issues, still not fixed. Perhaps never will be fixed.
The WinUI3 issues are for me dealbreakers... I'm not even talking about app-size or sandboxing.
But the app startup is very important. An app needs to be quick and responsive, that's the first impression user get from the app.
Xamarin en React Native are using UWP. Because Xamarin is ending, I think it's good idea for MAUI to continue using UWP for people that need to create quality UX apps.
Public API Changes
Unlike WPF which has older XAML dialect, WinUI3 and UWP have similar XAML/API syntax. So it shouldn't be that difficult to map and maintain both of them?
React Native also supports UWP and WinUI3 simultaneously.
Intended Use-Case
UWP has its own strong advantages, like .NET Native (high performance) and security (sandboxed). If you want to push faster, lighter MAUI apps, give us the option to use UWP instead of WinUI3.
Beta Was this translation helpful? Give feedback.
All reactions