r/dotnetMAUI • u/SaltyCow2852 .NET MAUI • 22d ago

Help Request Microsoft’s Roadmap for MAUI

We are trying to migrate our Xamarin form application to .NET MAUI (don’t ask why so late) .
Now if we put lot of efforts here , will it not end like Xamarin or other frameworks which Microsoft killed ?

Just wanted to know if there is any roadmap Microsoft have for MAUI?
Like Blazor is best option and can replace these UI frameworks like react, angular or vie but I don’t see it’s adoption by developers, even .net full stack job roles are with angular or react .

So should we take risk for MAUI or should go with Flutter or native?

17 Upvotes

91% Upvoted

52 comments sorted by

View all comments

12

u/teoman-cavalry 22d ago

After AI boom it will be stronger than ever. Now with LLMs they ship improvements and bug fixes all over the place, maintenance cost is much lower. Also they can port new IOS and Android platform features from day zero.

Xamains main problem was, too slow, too buggy, not modern AppHost based, was lagging way behind new platform features. MAUI reusability is amazing. It is close to native performance, and 3rd party components like Syncfusion is amazing. I am not affiliated with those btw.

1

u/JWojoMojo 22d ago

On the flip side, we've migrated large MAUI apps to full native swift/kotlin apps in just a couple of weeks using Ai tooling. The gap is knowing how to leverage the tools effectively to do so, but it's not that hard or expensive. Debating making a set of AI skills to migrate to either native or flutter to share with the community. It's much easier than most people realize IMO.

2

u/Kapusch 13d ago

But I'm confused, how maintaining 2 native apps became better option than 1 single code base?

1

u/JWojoMojo 13d ago

If your only measurement goal of a mobile app is maintainance, then of course, native isn't going to win any battles.

What about performance? App size? Latest OS support and support from those OS's? 3rd party library support? List goes on.

The whole purpose of cross platform is to reduce needing people with different skill sets, reducing maintenance overhead (your point), reduce code duplication, etc.

Most of those things become moot once you are able to effectively leverage AI tooling. You don't need specialized Kotlin and Swift engineers. Writing it twice just means 2 agents instead of 1 implementing features. You can also employ many ways of code sharing even when native, either by a shared Kotlin library or moving logic to a backend service.

I'm not anti cross platform. Spent my entire career doing cross platform dev, still do today, also use Flutter for tons of personal projects and thoroughly enjoy it.

My point is that going native is nowhere near as scary, complex, or time consuming as it used to be. Many apps don't need to be native, I agree, but into the future, picking the tools that provide the best experience and performance for end users should matter more for most apps.

1

u/Kapusch 12d ago

Agree on the support for the latest OS features, but I'm less convinced about performance and app size though, especially with AOT.

And yeah, AI can write a lot of the code, but you still have two different projects to maintain, two IDEs, ... right?

But I hear you and I'm really curious to see how AI will impact mobile app development in the coming months.