Replies: 10 comments 36 replies
-
|
We migrated our app from xamarin to MAUI on .NET 8 and are now on .NET 9. Initially everything was a big pain. Now things are kinda smooth, comparable to how they were on xamarin. We are not using Shell! But this is just for our project, I see some other people still struggle more. Generally you still need to work around a lot of smaller quirks, but that was already the case in xamarin. My biggest pain is that the performance on Android is terrible. Regarding rider it works quite fine now. There is some issues for me still where builds will randomly fail and debugging/hot reloading will not work and I need to clean the project and delete .idea files, this is a pain sometimes. MAUI is not great but it does its job for the most part. I would still be hesitant to recommend anyone using it because of all the quirks, performance issues and instabilities. |
Beta Was this translation helpful? Give feedback.
-
|
As far as I know, Xamarin support will end in May 2024, right? For me there is no question about MAUI team regarding the MAUI issues, the guys give the best of themselves. But what I keep asking myself is if c-suite from Microsoft is still alive on this planet earth? Because how can you remove support from Xamarin when MAUI is not yet mature (even if it was released 2 years ago)? Maybe Microsoft also hopes that there will only be programmers in this year 2025 and after that no more because AI will take over everything (Mark Zuckerberg)? pc |
Beta Was this translation helpful? Give feedback.
-
|
To be fair it seems we are going back rather than going forward. I hope things will get better but for now I'm not very confident about it. |
Beta Was this translation helpful? Give feedback.
-
|
@phillippschmedt Could you try #27259 if it fixes your performance issue? Any feedback there is tracked by the MAUI team, so it's useful to present there any positive impact, if any. |
Beta Was this translation helpful? Give feedback.
-
|
Well, my main issue nowadays is regarding tooling. Still an awful experience, either using Rider, or Visual Studio for Windows, (rider is better though). The classic clean, delete bin/objs, fonts not being rendered, etc, hot reload stopping to work. On the positive side, my experience so far has been good regarding the framework itself. Not that many issues regarding performance ( thgough previous knowledge from Xamarin helps a lot, Visual Tree, simplification of xaml, some controls in pure c#, MVVM, less packages). One thing people keep forgetting - debug is WAY slower in MAUI rather than xamarin. but like 4/5 times slower. If you go to a release version the app seems like another one. Still, there is a long road ahead, with many critical bugs, (or just simple ones) to be fixed, but things are going forward at least |
Beta Was this translation helpful? Give feedback.
-
|
I'm aware about the debug and that's fine... it's the release that I'm complaining about. Everything is slow without reason. I used a syncfusion calendar component for one of my client's app but it was too slow and I had to rewrite it from scratch to make it decent so it's not how I write code. I loved Xamarin and love C# but this team need more resources to do something good |
Beta Was this translation helpful? Give feedback.
-
|
#27042 seems to improve perf considerably for all platforms. See the perf impact section. There is much more that can be achieved with this approach. But even with this PR, a big group of apps might turn from slow to okay performance-wise. One can even somehow download nugets for that PR to check it out now, but I'm not sure how at the moment. |
Beta Was this translation helpful? Give feedback.
-
|
With MAUI I only use Blazor and don't really experience these performance problems. I have the impression that the majority of MAUI problems are caused by XAML, but can @MartyIX please clarify this because you are dealing with it? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
More in-depth reasons are mentioned in the PR. But in short: MAUI on Windows/Android/etc. requires interop calls to propagate virtual views changes to platform views. These are costly, #27042 reduces significantly the number of such calls. Personally, I don't think that XAML is the issue. |
Beta Was this translation helpful? Give feedback.
-
the nugets are on Generally speaking, I have to say that the performance in release mode is now great if you have the resources and the will to optimize your code and xaml |
Beta Was this translation helpful? Give feedback.
-
|
Does this already contain #27042?
Not sure about the comment about optimizing code and xaml..
Is this related to this build or a generic comment?
…On Mon, 20 Jan 2025, 15:18 Nico, ***@***.***> wrote:
#27042 <#27042> seems to improve perf
considerably for all platforms. See the perf impact section. There is much
more that can be achieved with this approach. But even with this PR, a big
group of apps might turn from slow to okay performance-wise.
One can even somehow download nugets for that PR to check it out now, but
I'm not sure how at the moment.
the nugets are on
https://dev.azure.com/xamarin/public/_build/results?buildId=132815&view=artifacts&pathAsName=false&type=publishedArtifacts
--> nuget
--> 3-dot menu (appearing on mouseover)
--> download artifacts
Generally speaking, I have to say that the performance in release mode is
now great if you have the resources and the will to optimize your code and
xaml
—
Reply to this email directly, view it on GitHub
<#27185 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUIPIWKXLXOHM67TMXPVET2LUHTXAVCNFSM6AAAAABVKAC3KCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBZGE4DCOI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
That is my own general opinion regarding performance at the moment, even without #27042 It helps a lot to create ViewModels in background threads and only set the ViewModel in the view as a BindingContext when all properties have their value. Especially IsVisible properties. And of course don't create unnecessary controls and then hide them with IsVisible="false". |
Beta Was this translation helpful? Give feedback.
-
|
@marcojak I was talking about some general considerations ( most of them are pointed in the performance section of MAUI). Keep the Visual Tree as slim as possible. One of the advantages or disadvantages of XAML is that you can have the same layout constructed in different ways ( VerticalStacklayouts, grids, etc): I tend to use as many Grids as possible. Regarding the VMs, the same comment as @baaaaif , background whenever possible, async awaits, offload from MainThread whenever possible ( see ConfigureAwaits in your HTTP Requests and other possible tasks) |
Beta Was this translation helpful? Give feedback.
-
|
OK, I overlooked one thing - for me this is only the case on iOS and Android if UseInterpreter=False(iOS) / RunAOTCompilation=True(Android) are set. |
Beta Was this translation helpful? Give feedback.
-
|
These are all great suggestions but unfortunately, MAUI is for some reason slower than Xamarin Forms. This is true especially for iOS where X.F. was really smooth on iOS and really slow with MAUI. In addition to this, I see some strange behaviours in one of my sporting from XF to MAUI (but I still have to investigate them so I haven't opened any issues yet), where some controls just disappear from my CollectionView and others are not properly updated. I'm not saying it's all bad, but just that there is a lot of room for improvements |
Beta Was this translation helpful? Give feedback.
-
|
Try MauiReactor |
Beta Was this translation helpful? Give feedback.
-
|
I didn't know about it. I'll have a look. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Here are some important links for MauiReactor: https://github.com/adospace/reactorui-maui https://github.com/adospace/mauireactor-samples |
Beta Was this translation helpful? Give feedback.
-
|
I think in 2025 we should continue to accelerate the resolution of bugs and optimize the logic at the same time. By using AI analysis to improve the code, the problem of maui being slow may be improved. |
Beta Was this translation helpful? Give feedback.
-
|
Just as an update. I've published my client latest app yesterday, both on Android and iOS. |
Beta Was this translation helpful? Give feedback.
-
|
Personally, I had to create a customised Calendar with a custom cell for each day. Also getting rid of the CarouselView, replaced by another control made by other developers, solved almost all problems, we went from more than 400 crashes in 1 day to just 1 today. I really hope the team will get rid of the CarouselView and replace it with another component. Regarding Blazor, unfortunately, I have no real experience with it (I've done a few tests to see if it was mature enough) so I cannot say. My feeling anyway is that Blazor shouldn't have the same performance issues |
Beta Was this translation helpful? Give feedback.
-
|
@marcojak what pre-release already includeshttps://github.com//pull/27042 ? |
Beta Was this translation helpful? Give feedback.
-
It's a pull request, so one can download nugets for the PR. It's not in the nightly feed because it was not merged. And it is a good question if it will be ever merged because @albyrock87 presented #27259 which seems to be an even better implementation of what I wanted to achieve. You can check out the perf improvements of his PR1. Footnotes
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you. Anyway, whatever will be chosen, will be a good improvement! |
Beta Was this translation helpful? Give feedback.
-
I don't want to a bearer of bad news but ... I sincerely doubt that 😂. It's a non-trivial change so I don't expect it. But sometimes miracles happen. |
Beta Was this translation helpful? Give feedback.
-
|
In 2025, we still using Xamarin.Forms, Xamarin.Android, and Xamarin.iOS. Why we still using Xamarin? Because migration to MAUI is painfull, we have a lot custom handler, and too much components must be enchance. MAUI is good for .NET developer to craft some mobile apps, but if you wont to migrate, consider to re-write all source to another crossplatform framework (RN or Flutter). |
Beta Was this translation helpful? Give feedback.
-
|
You would have the energy and resources to rewrite to another framework, but you would not have the energy and resources to rewrite some of your old custom handlers and components to a more modern and performant platform - .NET Maui? Doesn't the reasoning seem nonsensical to you? |
Beta Was this translation helpful? Give feedback.
-
|
@saint4eva please try development in macos if you want know developing .NET MAUI and you want to throw you energy to .NET MAUI. |
Beta Was this translation helpful? Give feedback.
-
|
@raselldev how you will compile Xamarin apps with iOS 18 (required from April 2025) and Android 15 (required from August 2025)? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, so you now, i think compile iOS with xcode 15 but starting from April 2025 how you compile Xamarin with xcode 16? |
Beta Was this translation helpful? Give feedback.
-
|
I can build xamarin app with ios18.2 SDK in the following environment. For Android, install the Android SDK and tools that support API Level 35 and set the targetSdkVersion in AndroidManifest.xml to 35. |
Beta Was this translation helpful? Give feedback.
-
|
I'm also still using Xamarin.Forms. I've changed my Xamarin.Forms app so that it would target Android 15 to prolong it's life a bit. I've just installed Android SDK for Android 15 and edited the target version in AndroidManifest.xml. It was simpler than I had thought. I just needed to opt-out from edge-to-edge mode afterwards and that was it. I've published it to Google Play and it works well. However, it gave me just a few months. From November 1st, 2025, Google Play will require apps to support 16 KB memory pages. This is supported in MAUI but not in Xamarin.Forms. I've almost finished migration to MAUI for Android. I've uploaded MAUI version of my app to the Google Play internal testing channel to try it. It was surprisingly smooth process. And there is a really nice performance boost compared to Xamarin.Forms version. On the other hand publishing Windows version to Microsoft Store turn out to be a nightmare for the app updated to MAUI and I have not been able to solve it yet. |
Beta Was this translation helpful? Give feedback.
-
|
@holecekp Is there an issue for the Windows issue? |
Beta Was this translation helpful? Give feedback.
-
|
@MartyIX I've reported there: https://developercommunity.visualstudio.com/t/Missing-option-in-VS-for-publishing-NET/10918920?viewtype=all Besically, I have troubles associating the MAUI app with the existing app in Microsoft Store (which was no problem for the original Xamarin.Forms version of the app). Additionally, I updated MAUI from 9.0.70 to 9.0.80 and the app started crashing with the code 2147942405 (0x80070005) on Windows, so I reverted back to the origianl MAUI 9.0.70 but the crashes still persist (???). I've deleted bin and obj folders, restarted computer but still the MAUI app could not run on Windows anymore. Then I spent some time googling and found that this might be the issue #12080. It's from the year 2022 and marked as closed but apparently it's still a problem also in 2025. I've added |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, .NET MAUI is not that bad actually. I am just finishing the development of a .NET MAUI 8 App for Android and iOS and the framework was pretty descent, actually. It is not a huge app but includes many features (user management through an API, a mechanism to maintain state between views, barcode scanning, search-enabled, dynamic CollectionViews and even forms dynamically created in code, etc) that were all implemented nicely in a MVVM fashion. It is a wizard-like app and I did use Shell, which worked as expected, too, even though it took me some time to understand its twists and bolts. Also, MAUI XAML (2021) is a bliss compared to WPF XAML (2009), really. Overall, a very good experience. I had heard LOTS of bad things and rants about .NET MAUI but decided to go for it and I cannot say I got disappointed in any major way. Things do work and the official documentation is good enough (compared to ChatGPT and StackOverflow that misled me most of the times). |
Beta Was this translation helpful? Give feedback.
-
|
I'd say things are a lot better now that things have had some time to stabilize after the dotnet 9 release. Yeah, there are some bugs still, and the performance could be improved a bit. Generally though, things are getting to be pretty smooth. For the most part the apps are pretty snappy in terms of startup and runtime performance. The MAUI team are pretty responsive I find. Certainly beats developing multiple native apps, especially if you already have C# experience and/or an existing C# app you need to port. Release builds for iOS are abominably slow, but that takes place on CI and only when publishing so doesn't affect the dev cycle too much. Using MVVM can mitigate some of the risks if you wanted to jump ship to AvaloniaUI, which might be a better choice if you want something more custom in terms of drawn controls, etc. |
Beta Was this translation helpful? Give feedback.
-
I would just like to mention https://github.com/taublast/DrawnUi/ here. It appears one can use drawn buttons, etc. with this library. Personally, I haven't had a chance to test it but the demos look fabulous. Kudos @taublast. |
Beta Was this translation helpful? Give feedback.
-
Buy a Mac Mini M4 to use as CI Agent and your build will be much faster, even for Android I've had amazing results. |
Beta Was this translation helpful? Give feedback.
-
@MartyIX Thanks! It's not just for buttons :) You might be interested in taking a look at something really fun I shown today |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, it's a good point how much community libraries/plugins have improved too! I've been keeping an eye on DrawnUi too - definitely considering using it in the next release cycle. Thanks @taublast! There are some other plugins I'd like to shout out to fill some functionality gaps past the obvious MVVM stuff:
FWIW, here I have a Mac M2 Pro and it takes roughly 30 mins for an iOS release build 😞 |
Beta Was this translation helpful? Give feedback.
-
Very interesting in why it will take about 30 min for the build. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Many older discussions stem from the rocky transition period of the past few years. But what’s MAUI’s current state?
I work with MvvmCross but am considering making a relatively simple MAUI app, without much media or other UI-heavy tasks.
Side question: Is Rider’s support for MAUI any good?
Beta Was this translation helpful? Give feedback.
All reactions