Why doesn't Microsoft have just 1 flagship product built on .NET MAUI?

[Pinpaho]

I'm not saying all but I mean like Teams would be a great candidate to give the community some confidence in the dev platform. I've been asked this by my higher ups when I bring up the benefits of MAUI. When they looked and saw that Teams was built on WebView2 they didn't want to use MAUI. Why doesn't Microsoft use it for a flagship product? Not a side one.

[wubalubadubdub55]

Because Microsoft doesn't have good leadership that can encourage dogfooding internally (that eventually improves their tools and massively helps developers in the .NET ecosystem).
Look at how Meta invests on React Native and how they dogfood it in their flagship apps, and how that has improved it.
Microsoft has no such concept.

Microsoft encourages developers to use MAUI, Blazor etc. to create client apps, but when it comes to their own flagship apps or important projects, they use React, Electron, Native etc.

Developers shouldn't listen to what Microsoft says or advertises.
Developers should rather do what Microsoft does.

[wubalubadubdub55]

Developers should rather do what Microsoft does.

And learn Java, Golang, Node, React etc. Because Microsoft has more confidence on those tools and frameworks rather than their own tools (C#, F#, .NET, MAUI, Blazor etc.).

While you're at it, learn AWS, GCP etc., so you don't have to depend on a company that has no confidence on their own tools.
Microsoft themselves might start using AWS, GCP etc. instead of Azure someday, lol.

[davidortinau]

@Pinpaho thanks for advocating for the benefits of .NET MAUI! ❤️

Having a Microsoft product like Teams built with .NET MAUI would indeed make that conversation with the "higher ups" a lot easier. There are several other products built with .NET like Azure mobile, Seeing AI, Microsoft 365 Admin, and a variety of Dynamics apps. Several of these "side apps" have well over 1M downloads in the Play Store alone.

A few things to consider:

• to say that Teams is built with WebView2 is a gross oversimplification of the architecture
• Teams was built before .NET MAUI was an option
• a dev teams skillset is a major driver on technology choice
• Microsoft is a massive company - think of it more like many, many companies that work together. It's 3x the size of Meta (Facebook)
• Is your company building Teams (not just the scale of app, but the entire complex architecture with multiple teams and tech), or are they building something more aligned with one of the "side apps" (suitable for focused teams, maximizing a single tech stack and language to reach multiple platforms with native experiences)?
• If choosing web UI is the attractive aspect, then you can do that in .NET MAUI as well with HybridWebView or BlazorWebView. These were introduced for the companies that wanted to use .NET but also have a lot of expertise and investment in web and JavaScript/TypeScript.

4 new customer stories were recently published about .NET MAUI, and Fidelity highlighted at .NET Conf last Nov how they are using .NET MAUI to get amazing perf.

When apps need deep native integration and performance, while maximizing your code share across a single language, then .NET MAUI is a great fit. The Fidelity app is a fantastic example of that.

I agree with @wubalubadubdub55's point to put more weight on what you see done than said. Look at GitHub momentum (PRs created and merged are way up, incoming issues are down). Look at partnerships bringing tons of contributions like Syncfusion. Look at other companies sharing their success, like Fidelity and the other case studies.

@Pinpaho I hope some of this helps you with the conversations you're having.

[mairaw]

appreciate the confirmation. Let me reach out to that team internally.

[mairaw]

@Pastajello can you confirm your location?

[Pastajello]

Poland ;)
@mairaw

[rokmeglic71]

Same here, Slovenia @mairaw

[mairaw]

Thank you. I also got a coworker from Czech Republic to confirm they get the same behavior. I'm discussing with that team. If nothing works, I'll switch the URLs to include the en so it will be set to English.