Should I start an app on MAUI in June 2025? #29865
-
I need to start a new project and I'm wondering if MAUI is the correct decission or if I should go for flutter (I don't have any experience with dart or flutter). All my background is with C#, ASPNET Core, Blazor and Xamarin. The backend will use ASP NET Core so seems like MAUI is a good choice but I have a couple questions. The app consists of 5 or 6 pages, not too complicated but they will render quite a lot of items. I only need the app on iOS and Android, nothing else.
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
YES |
Beta Was this translation helpful? Give feedback.
-
Maui today is way way way better than it used to be .. I would say that is stable now , still a rollercoster though when there is a new release, but given your background and not sure on your timelines I would stick with Maui. Things to point out...
I have recently done blazor stuff too, and the most pleasant thing , things just worked! when you have 2 OS - android and Apple its a nightmare as things do not work exactly the same and you might be totally happy in android how a page looks and you run in apple and there are issues and viceversa.. Building a solution is slow , depends on how many projects and your machine, there are still issues when in iOS you have to nuke the bin/obj rather than clean to see a change take place hope the above helps a bit. |
Beta Was this translation helpful? Give feedback.
-
You may find this answer helpful. My experience with Blazor Hybrid was not a good one, though. Blending the web technology with the .NET MAUI App Container was like trying to fit the pegs and holes shown in the image below resulting in a very slow development process with lots of obstacles and a horrible debugging experience. |
Beta Was this translation helpful? Give feedback.
You may find this answer helpful.
My experience with Blazor Hybrid was not a good one, though. Blending the web technology with the .NET MAUI App Container was like trying to fit the pegs and holes shown in the image below resulting in a very slow development process with lots of obstacles and a horrible debugging experience.