Member-only story
Why I Don’t Use .NET MAUI Anymore
Tooling issues, bugs, and complexity made me realize that I get things done quicker with Flutter.
I am not a beginner when it comes to cross-platform frameworks. Over the years I tried many of them. It all started with Delphi many years ago (yes, you can write cross-platform apps for desktop and mobile with it), then I went towards Xamarin/.NET MAUI, and finally settled with Flutter. I also did some small evaluation projects with Electron and Ionic. From all those options, I liked .NET MAUI and Flutter the most. But recently, I started focusing on Flutter and left .NET MAUI behind.
I want to talk about some of the issues that I encountered.
Language issues on Android phones
I worked with Visual Studio and deploying usually worked. But when the app launches with a debugger attached, I usually had an instant exception without a helpful message. The “solution” was to set the device language to US English. Then it worked. I cannot find anything on the internet anymore, but a SO thread led me to this solution.
Once I got used to it, it wasn’t a real deal breaker anymore. But finding that fix took a while. And it didn’t happen with the default app but only with mine.
