Is MAUI mature enough for enterprise grade native application deployment?

[PBTests]

Is MAUI mature enough for enterprise grade native application deployment?

[Adelzu]

As of September 2022, the short answer is "it depends"
Almost everything is fixable. But it requires time. IF and only IF you are not on tight deadlines, the answer is not yet.

[janseris]

Yes it is possible we are doing it but it will get your devs insane because almost every feature has a bug or a workaround is needed to make it working which is a lot of unwanted complexity in the project
It takes 4x more time to develop than it should

[Adelzu]

I changed my mind; With MAUI, you spend more time debugging the tools than debugging the app.
I wish we didn't move from Xamarin yet.

[manishbisen]

Sad to hear that

[GeoSaffer]

Its now June 2023......

Moving from Xamarin Forms to Maui feels like it is at least 2 years too early, but still Microsoft is forcing us to move to Maui. This is absolute bullshit ! It feels like the start of Xamarin forms All over again, FFS Microsoft wake up !

[Adelzu]

@GeoSaffer thanks for reminding me to post here again.

Here we are 8 months later. Now you :

1. debug the tools less, face weird issues.
2. trace weird issues and find out they known bugs and at of the github issue, you see a comment from the infamous msftbot saying We've added this issue to our backlog, and we will work to address it as time and resources allow or that the fix for a major issue is coming in the next major release!
3. try to find workarounds and fail around 50% of the time.
4. abandon the change then design it in another way.

It seems we are hitting a sunk cost fallacy with MAUI.

[nor0x]

I changed my mind; With MAUI, you spend more time debugging the tools than debugging the app.
I wish we didn't move from Xamarin yet.

unfortunately this is still true today, in the current state MAUI development is a great pita!

[FM1973]

It kind of depends....

We have a relatively big app in open beta for Android and Ios. So far, there are not many problems.
But we had to work aroud a lot of known bugs, as most of you. We are currently stuck at version 7.0.59 beause of the severe regression bugs in 7.0.81 and 7.0.86.

The main problems, in my oppinion, are the regression bugs and the bug fix speed for .net 7. You can´t update without having to test everything again, in my case, two platforms - if there is a version you can update to.

The second problem is the development policy. The team currently is targeting .net 8, as @hartez stated in #14257 (comment) . I´d really like to knwo how the team decides which bug fixes are important enough to be backported to .net 7, since everyone of us has different needs. I think there are a lot, but the last service release for .net 7 was more than a month ago and there are a lot of important bug fixes we need to see in .net 7. Furtheremore this policy won´t change. So, even if we get a .net 8 version in november (!!!), the same game will start again. The team will develop against a beta version of .net 9 we can´t use, and we will be waiting for bugfixes to be backported to .net 8. Sisyphus is calling.....

So I can´t vote. I´m in between....

[Adelzu]

Your comment ended a 2 days spiral of weird issues. We have mistakenly upgraded from 7.0.59 and were face issues we couldn't explain!
Thank you.

[AlleSchonWeg]

Coupling to .Net releases was the worst decision they have made.
Nobody knows what bugs are fixed. In a service release or in next main version?! Totally random.

[giuseppenovielli]

@FM1973 @davidortinau
With .NET 8, MAUI will be released also like nuget package, as Xamarin.Forms did?
So with nuget package can release bugs fix, fastest than .NET Versioning?

[FM1973]

Look there: https://devblogs.microsoft.com/dotnet/announcing-dotnet-maui-in-dotnet-8-preview-3/ .

[giuseppenovielli]

Guys, the idea is that must provide a channel (like nuget) where can release fastly new MAUI version, for regression or some issues with hight priority.
So also 2 service release in a week, but only the most important issues, without waiting months, for fix an issue regression, that have generated another Service Release.

P.S. This is only an'idea, i don't known how .NET Servicing work, but it can be very useful fix fastly regression, hight priority issues, that have generated by another Service Release.

[Strypper]

It still a total crap today with RC2

[Adelzu]

I think it is less buggy now. Still a long way to go though.

[Strypper]

Collectionview view still broken
Label isn't display html correctly
And people migrate crash the application with 0 logs on Android
LOL this is a piece of garbage.

[azrinsani]

Is collection views still broken?

[GeoSaffer]

Still dont have the basics working, still stupid bugs and missing ported code. FFS Microsoft.

React is starting to look really good right now.

What a waist of time and money trying to get everything ported to Maui