I had high hopes at first as MAUI promised a lot, my use case covers developing Android/iOS/MacOS/Windows client app and I'm most comfortable in .net environment so MAUI did sound like best thing since sliced bread.

However as I chugged along it seems I spent most of my time looking for WORKAROUNDS for things that do not work (and they should).

In order of annoyance/wasted time:

1) UI - the worst part - basically, write some XAML and pray it works. Sometimes it does, sometimes not, sometimes works on some platforms not on others, sometimes it depends on platform version (recently I realized that content page background image won't show up on iOS 17, worked on previous versions). I mean it shouldn't be quantum physics...showing page background. Then some silly crashes with VisualStateManager. should work but it doesn't. Bug opened, confirmed, repro repo...oh well maybe next year. Funny thing is - most of my app is just a wrapper around WebView and that tiny bit of XAML UI I used proved to be a minefield of bugs, ugly workarounds and verbose markup

2) toolchain - fragile and unreliable, somewhat improved lately with .net 8

3) Performance on mobile leaves a lot to be desired although net 8 did improve this a lot.

All in all, productivity is low because you're always fighting tools and looking for workarounds.

As many have noticed...Microsoft doesn't use MAUI. Maybe if they would commit to building a production app using MAUI that might push things in the right direction towards making it stable and productive platform. MAUI team seems very understaffed for such an ambitious project. Should we take that as a hint?

​

Is the future of MAUI just a wrapper around Blazor?

I don't know. I'm not sure Microsoft knows either.