Does .NETZ MAUI rightly have the reputation of being half-baked?
I'm a Swift guy, but I want to re-check on the Microsoft approach after my break up with Xamarin like 5 years ago.
I read a lot of Reddit, Twitter and other platforms where long time .NET developers are outraged about the state of .NET MAUI.
Some points are valid, like sun settings VS for Mac, etc. Other says that they have a lot of weird work arounds to get a stable PROD app going with MAUI.
What's your opinion, do you see MAUI as the go-to-choice for multiplatform apps in the .NET ecosystem?
Thanks for your insights!
3 Replies
Yes, MAUI is somewhat functional for simple projects, but it crumbles apart easily. It's supported by a skeleton crew, too, so don't count on getting many updates or getting them quickly.
The way it works, where it uses native components instead of drawing them with Skia or something like, for example, Flutter does, also lends itself to a glacial development speed.
It might become stable and actually good in the future, sure
But with how few resources MS puts into it, and with MS themselves just moving all their stuff to React + WebView, not even trying to dogfood MAUI, I wouldn't count on that
I'd sooner expect MS to announce another new UI framework lmao
There aren't any crossplatform alternatives from MS either, from the community you have Avalonia, Uno and Eto though
They aren't that popular for mobile dev though afair
Oh okay thanks for your feedback