How are things in 2026?

[Mimisss]

Inspired by the How are things in 2025? discussion.

So, how is MAUI doing in 2026?

Is it growing strong or not? Any cool packages worth mentioning?

And are we going to see any major improvements? For example, the process of publishing for iOS could be heavily improved, IMHO.

[AlleSchonWeg]

Performance improvements. But i'm still on .Net 9.
.Net 10 in 2026 introduced new "features" which created new trouble:

• EdgeToEdge in Android (Statusbar color, ModalPages, TabbedPage)
• iOS 26 liquid glass (LargeTitels, TitleView)
• iOS CV2

Issues and PR's created for almost every issue, but merging is still very slow. Focus is more on ai, automatic pr review and repository statistic.
As a result, more open issues and a lot of open pull requests.

[MartyIX]

• [iOS 26] ToolbarItem color with custom BarTextColor not working #33970

It seem that this issue was fixed by #34036 (merged into #29755).

• [NET 9 regression] Changing StatusBar and NavigationBar background color doesn't work with Modal pages [NET 9 regression] Changing StatusBar and NavigationBar background color doesn't work with Modal pages #28552

Interestingly, this issue is marked as fixed by #28568 many months ago. But the issue is not closed. @kubaflo may know the current status.

[AlleSchonWeg]

It seem that this issue was fixed by #34036 (merged into #29755).

The team merged this yesterday after posting this message. Yes his could be fixed. Need to test.

Interestingly, this issue is marked as fixed by #28568 many months ago. But the issue is not closed. @kubaflo may know the current status.

This was partially fixed for .Net 9. But broke again with .Net 10, because of EdgeToEdge and target android api level >=35 setStatusBarColor (https://developer.android.com/reference/android/view/Window#setStatusBarColor(int)) and setNavigationBarColor https://developer.android.com/reference/android/view/Window#setNavigationBarColor(int) have no effect.
Perhaps #32987 solves also the modal pages problem.

[jfversluis]

@AlleSchonWeg are you on the MAUIverse Discord by any chance? That can be an easy way to be in touch, iterate over these (now faster than ever because of AI!) and lets get you unblocked

[AlleSchonWeg]

@jfversluis Thanks for your reply.
No i have no discord account. I also think the issues are described very well. Issue #32987 is tagged as p/0 and for me it is the top issue if i had a wish ;)

I will use .Net 9 as long as necessary and possible. The customers don't care if we use .Net 9 or 10. They only see that something looks different and i won't a discussion and explain them the reasons.

Thanks again.

[jfversluis]

@AlleSchonWeg this is not about the issues being described well or not, it just takes longer to go back and forth through various issues and a direct channel can help resolve things quicker if we do have questions about it. Less room for misinterpretation, quicker verification, means that the issues that are important to you will be resolved faster.

[jianfeng586]

A fair number of PRs were merged this week. I would be happy if this pace could be maintained, or at least kept up for three weeks out of a month. I hope AI can help increase the merge speed and reduce the occurrence of issues.

[jfversluis]

That is definitely part of the reason why we ware investing in AI right now even though that might seem silly. In the longer run that will definitely pay off and that is what we are starting to see now. Thanks for noticing!

[Xyncgas]

#15203 (reply in thread)
Antigravity + redot is the butter
AI can be knife to butter but instead of address MAUI's failure people are pointing to artificial intelligence to fix everything which looks bad because then why not use AI writing an app in natural language and have agent verify the result by giving them emulators of android and ios and comparing screenshot / pdf

[Xynratron]

Review / Retest on every platform consumes most of my time. A Real-Time Click on every platform-emulator would be very nice, but currently we have to wait many seconde between every click / touch to see the next screen (Emulator / Simulator are realy slow). All at the same time with hot reload to review the changes?

An easy to use and implement frontent test framework may be the first step: Testers can define a step-through and AI-Agents can verify. Maybe 2029? (or proof me wrong! Is there someting around!?)

[Xyncgas]

[jfversluis]

Not sure what those badges say about how well things are going. MAUI is a complex codebase running tens of thousands of UI/unit/device/integration tests. Some of these are flaky by nature. We can run them in such a way that it looks green there, but that would not help anyone I think. In fact, I don't think this is any useful indication of anything, so I just removed them. Thanks for the nudge!

[holecekp]

MAUI is great and I would definitely recommend it. About a year ago (I'm not sure when exactly), I noticed a significant improvement in the speed of releasing bug fixes. However, the year 2026 didn't started well. MAUI needed to tackle the edge-to-edge mode, which is required for targetting Android 16. This introduced a great amount of bugs in the .NET 10 version. The following service releases in 2026 fixed some of them but often introducing regressions. If you use Android, it's safer to stay with .NET 9 for a while. However, I'm optimistic because the current pace of bug fixing is quite good.

Version 10.0.41 is the first .NET 10 version that could be usable for me in the production on Android with a few workarounds. I released a new version that is based on it to the beta testers today.

Here are the main difficulties I've experienced for different platforms as of 2026:

• Android (.NET 10) - Incorrect background and icons colors for the status bar - to make things even worse, they differ depending on your Android version and if a modal page is opened. Shell doesn't fully support edge-to-edge mode, there are visual bugs espeically in the landscape mode, even though the serious ones were fixed in the latest MAUI version. Rendering speed for a groupped CollectionView is not ideal (both .NET 9 and 10).
• Windows - Publishing is not fully supported in VS and I need to use the command line (VS can create only MSIX, which is refused by Micorsoft Store because I used MSIXBUNDLE for Xamarin.Forms version in the past).
• iOS - there are much mure issues compared to Android. Many of them are visual and layout bugs when a visibility of a control is changed at run time or when the screen is rotated. The most serious ones have been fixed at the end of 2025 and beginning of 2026. Some still remain. For example, if I rotate the device to the landscape mode and then back to the portrait mode, the safe-area stops working and moreover one of the tabs disappears. Turning the display off with the power button and turning it on again returns everything to the correct state. Also requiring a certain XCode version is not comfortable. When VS or something else is updated, running on iOS stops working unless I download and install a newer XCode version (which can be an hour or even more depending on the Internet connection speed). The setup for Pair-to-Mac is also very difficult in general.

[Xynratron]

For Windows: I have a .targets File to build bundles (had the same problem last year, I think this one: #22445 (comment)) - but for .net10 my sideloading packets for testers are broken.
Windows-Store itself has no prio at microsoft since years.

[Xynratron]

MAUI is a great Idea, but not a solution for an Enterprise.

We had a Xamarin-App for many years. Needed to port it to MAUI. Now needed to port to .net10.

In an Enterprise driven environment the Idea of changing the Framework every 12 months is terrible. That is a Microsoft decision, but .net10 is only till 2028. The Problem: the changes are very fast and you cannot establish stability. From .net 8-9-10 the Bindings changed, you have to correct everything and let it go to the complete Enterprise Review Process. There are no 2-Weeks Reviews. We do our sprints in that time, but a product review?

Current State: .net9.0 worked fine, Update to .net10 broke too much. We are not finished with the migration now and .net9 Support ends in Nov2026. We are not allowed to ship after Support. Nice.. one Year for everything. (to be clear: .net10: release Nov2025, .net9 Support End: Nov2026)

Suggestion: New / Breaking Changes not for the "cool new .net Release" - .net 10 broke too much to be feature complete till Nov this year.

You are not stable on .net10 till now! How can we update?

[kubaflo]

Hi! Thank you for the feedback - it’s really appreciated!
The key question is: what is preventing you from shipping on .NET 10 today?
If you can share the specific issues or breaking changes you're hitting, we can take a closer look. Maybe we can address them or fix them in an upcoming release.

Cheers!

[Xynratron]

Problems with iOS. Things work on Windows / Android but break at iOS. And may not be our c# code in the ViewModels?

Example: We have an Issue with "IsVisible" set to false leads iOs to not display a Page. I filed a bug for the Syncfusion-Team, but that does not seem the whole story.
Maybe if you see something similar, it looks more to be an issue with "View.IsVisible" on iOS. (because, If I set it on a sourounding ContentView, it also breaks rendering without any Exception)

Next Example: I have an Layout Control to do a Wrapping & Sizeing of Child Controls (very close to the Microsoft Example Documentation) -> perfect at .net9, works at Windows & Android at .net10; breaks on iOS -> Loop for Measure() whithout a LayoutCycleEcxeption

I dislike the Idea of filing Bugs without proper investigation. I will provide it, if I have a reduced the example for the team to investigate it ( and I can be sure it's not my fault ;-) )

To reduce the Syncfuison-Problem to a small project I needed ~8h. (Extract from main project, copy everything to have it compiling, remove, remove, revert, remove etc.)

So: I expect stability.