leonix Would you choose .NET MAUI today?
MAUI is just another layer on top of what I am using, promising less work to target multiple platforms.
I would not use it for a few reasons:
- It does not support macOS (only Mac Catalyst)
- More layers means more bugs. And you might have heard that MAUI has a bad reputation, and this is mainly because of the bugs in the MAUI layer, not in the underlying .NET iOS/Android layer
- The MAUI layer also has a negative impact on app size and app performance
- Adding the UI layer takes away that granular control over certain aspects of the UI. There might be ways to workaround thouse limitations, but then you lose again the time you won with using MAUI and not having to write UI code separately
- Without MAUI, it is much easier to understand and apply the Apple/Google docs for Swift/Kotlin. There's a UIButton for UIKit, and there's the same UIButton in the .NET bindings
Generally, I wish Microsoft would advertise MAUI less and the underlying layers more, I feel like most people aren't aware of the possiblity to use .NET for mobile development without having to use MAUI.
I did not know that you could write Delphi apps for mobile apps and that the language influenced .NET, I have basically no knowledge of that programming language 😃
