What is the future of MAUI?

[erossini]

I watched Microsoft Build and there wasn't much about MAUI. Looking around on the internet, there are a lot of commentators that say that Microsoft is not interested in continuing the development of MAUI. One of the proofs of that is that Microsoft fired important software engineers from the MAUI team. The same commentators give advice to move to Avalonia or Uno.

On X there is this https://x.com/migueldeicaza/status/1922409129567563855?t=niaTRg-0tDzr4MCQwyKigw.

Could you confirm if Microsoft is planning to do so or those comments are completely untrue?

[developer9969]

I would love to know it too... we invested heavily in Maui as we ported all our apps from Xamarin , as we had a couple of years of rollercoster with the quality and we have now finally reached stability and then this kind of news..

No easy to justify to customers on why we use maui, @davidortinau anything to add ? Silence does not help

[MartyIX]

@PureWeen commented on this issue on Discord:

[JohnUTerry]

My understanding is MAUI has been in maintenance since net8: Fixing bugs, improving performance, but no real new features or anything really innovating. Has been the same thing with net9 and same thing is pretty much planned for net10.

[Stedy59]

That's good! Before adding, they are working on the backlog... You should be happy for that!

[davidortinau]

Build is not our primary conference, it's .NET Conf which we just announced the dates for 2025, November 11-13. Hope to see you there!

Our commitment to the longevity of .NET MAUI continues unchanged.

I hope everyone has a chance to watch our Build breakout session AI infused mobile & desktop app development with .NET MAUI. While it's not a future of MAUI style presentation, I do highlight the wonderful product momentum we are seeing.

During Build we also hosted 2 .NET MAUI Hybrid lab sessions led by Beth Massi and James Montemagno that were packed out. And Gerald Versluis showed off some great productivity work we have been doing in Visual Studio during a theater demo session. Coincidentally Satya also mentioned some of that in his Keynote. Compared to last Build this is way more .NET MAUI content, and in neither case was it a reflection of commitment to the product.

Today we have more contributors to .NET MAUI than ever before, thanks in good part to the amazing partnership from Syncfusion and our consistent and wonderful community. Our product roadmap is up to date.

[JohnUTerry]

Arguably, the Build session was super interesting but was more about VS/Copilot Tooling and showcasing existing MAUI Hybrid capabilities than about showcasing anything "new" in MAUI itself.

There's nothing wrong in acknowledging again that most work in net8/9/10 has been in stabilizing on the initial MAUI vision vs building net new capabilities.

Would it be fair to conclude that the recommended approach and where salvation resides for MAUI is in the MAUI+Blazor Hybrid stack?

[JohnKesko]

@davidortinau

Many years ago when was I working abroad, the company I was consulting for had 2 full time employees only writing documentation/technical docs.

The company was not big but documentation was so critical.

Don't know how MS doing these days but I've started to implement that at my job and we're an enterprise company.

The main issue is me as an architect is supposed to write most of the docs, the problem is obviously time as many others.. plus the evolution of tech has gone so fast recent years that documentation is hard to stay updated.

I think this is what we are looking for MAUI in general terms.
Anyhow, you're doing great - just a thought.

[tjiakwokyung28]

run on harmonynext os 👍

[oseifrimpongg]

I do hope that I am doing the right thing by deciding to learn MAUI to build my first full fledged product 😄

[hflexgrig]

The thing is really frustrating is that very essential elementary things like adding Firebase analytics, or External authentication takes a weeks as there's lots of deprecated packages like Xamarin.Firebase.iOS.Analytics or Xamarin.Google.iOS.SignIn is not even building solution I had to replace it with AdamE.Google.iOS.SignIn which is working. Also I spent weeks on implementing share extension functionality on iOS https://github.com/hflexgrig/MauiSamples/tree/main/iOSExtensions/ShareExtension

[hflexgrig]

My understanding is 99% not doing real world business apps on MAUI but just experimental or investigation staff. And those who investigating, most probably will go with more well grained platforms like Flutter or React Native. Even those who had Xamarin App on prod, many of them will refuse to migrate to MAUI. Because without analytics metrics or external authentication it is hard to go to prod, and spending so much time on investigating workarounds is also not acceptable as well, as primary functionality of the app is suffering.

In the other hand I see that not many people cares about staff mentioned above, that's why I think most of devs just playing around, not doing real production apps.

[gabsamples6]

We use Maui for production app successfully- Maui was a pain but much better now. Yes there is little dogfooding but hey that is the way it is. The ecosy stem is growing but analytics push notification etc is a huge nightmare but I have solved like this

analytics we use Google rest api message protocol this avoids the use of nightmare nugets etc.

push notifications we rolled our own cannot trust any nugets I am afraid

I think the community nugets should concentrate on the hard stuff like this and not on the silly stuff like converters etc… especially now that syncfusion has given away quality controls -

but hey I don’t it’s way those community roadmap is going -

We invested in Maui and recently I have invested in blazor too I hope I don’t get bitten once again