-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: How does MAUI fit here? #36
Comments
I wonder the same. Great question! Also, I sure hope XAMLs are unified moving forward: no more XAML for WPF and XAML for UWP... but rather one single XAML syntax for all UI apps. |
It's still unclear what API MAUI will target on Windows. I thought it would be UWP but now I think it might be targetting WinUI 3 now (or at least it is a good idea to) BTW this project is a reunion of UWP, WPF, WinForms and MFC |
FYI there's a big thread in the MAUI repo on this: dotnet/maui#43 (comment) |
One way to think about this is that Reunion's APIs are generally expected to lay in the layer that frameworks build upon. Maui could choose to relayer itself on top of Reunion components, in the same way as WinUI is relayering itself on top of other lifted APIs for input, rendering and composition. That will help extend Maui's reach to all the same Windows endpoints Reunion is targeting. |
This project is basically reunion of UWP and WPF => One best option for creating windows apps with capabilities from both technologies. And now, we have another way of making Windows app. MAUI.
How does it fit together, will be future maui app also under reunion. Will be every reunion app "compatible" with maui app?
The text was updated successfully, but these errors were encountered: