Replies: 6 comments 3 replies
-
Having never heard of Avalonia, I naturally followed the link. if anybody can work out what this thing is from just the home page, I would be amazed. Three of us eventually worked it out from the documentation and quickly returned to MAUI. |
Beta Was this translation helpful? Give feedback.
-
You're free to use Avalonia instead of MAUI if for your project native controls are not important. I love to have the both projects active, and select MAUI or Avalonia depending if I need native controls. For me, I native controls are mandatory in some projects: #1058 (comment) |
Beta Was this translation helpful? Give feedback.
-
Well, that is my experience with Xamarin. And that is why I'm looking for alternatives to MAUI. |
Beta Was this translation helpful? Give feedback.
-
Actually you can combine both and reuse Avalonia controls in .net maui if you want; https://github.com/AvaloniaUI/AvaloniaMauiHybrid |
Beta Was this translation helpful? Give feedback.
-
I wonder sometimes if the effort MAUI put on using native controls would have cost much less time and effort by just maintaining custom drawn libraries of controls adapted for each Operating system like Avalonia. |
Beta Was this translation helpful? Give feedback.
-
Another very interesting and promising solution for .net maui with drawn controls is DrawnUi: |
Beta Was this translation helpful? Give feedback.
-
Edit: I changed my mind about drawn controls and support native controls offered by MAUI. So rest of this post doesn't really resonate with me anymore.
For MAUI to stay competitive in cross platform app development, it'd definitely help to learn from Avalonia, and forgo native controls in favor of renderers and also learn from their clean and simple architecture.
Avalonia has solved the cross platform problem so elegantly. Why not learn from them?
Beta Was this translation helpful? Give feedback.
All reactions