Most .NET developers formed their opinion of MAUI somewhere around 2022, and a lot of those opinions were fair at the time. Four years and an LTS release later, it's worth asking the question again, not as a fan, and not as a critic, but as someone who has to decide what to build the next app in. This session is a status report. We'll look at what MAUI genuinely does well today, where it still hurts, and which problems are fixed, which are worked around, and which are structural. From this, we'll get into the part that actually determines whether a MAUI project succeeds: architecture. What a maintainable app looks like, how to keep platform-specific code from bleeding everywhere, and which decisions are expensive to reverse six months in. We'll also look at where the framework has been heading lately, and what that direction means for real projects." You don't need any MAUI experience. You'll leave knowing whether MAUI belongs in your toolbox, and if so, how to use it without regret.
I am a Microsoft MVP and Software Development Engineer. A frequent regional and international speaker at Microsoft-related events and User Group meetings. While spending my free time, love to play chess, run in nature, write blog posts, help the community on StackOverflow to contribute to open-source projects, or be an instructor at NGO programming-related events. Completely dedicated to Software Development, mostly on the .NET platform, crafting apps using C# & .NET. Truly been in love with programming since my childhood days. ♥️