What is the recommended way to build modern Android applications?

[RoundRaspberry]

I apologize if this is the wrong place to ask.

I want to port a WPF application to Android and have been looking at my options. The WPF application is, for the most part, well written. It adheres to MVVM, and I expect to be able to reuse the view models with only minor code changes.

I would like this application to look and feel both native and modern. Currently, this would be Material 3 Expressive, but I also want to keep up with any future updates to the design language.

I believe these are my options:

1. Use .NET MAUI. Material 3 does not appear to be implemented yet.
2. Use .NET for Android with Views. Some components do not seem to be implemented in MDC-Android (FAB Menu for example). A few components will have to be implemented in Compose using Compose interop.
3. Use .NET for Android, but write most of the UI in Compose. I mean not just individual components, but entire pages, if not the entire application's UI.
4. Write a Kotlin/Compose application that binds to the .NET view models. This is different from the previous option in that the application's entry point would not be in .NET.
5. Give up on the idea of reusing the .NET view models and write the entire application in Kotlin.

I understand that some of these options may not be feasible.

I am not that experienced with Android development, so I would like some advice from those that are. I enjoy working with Kotlin and Compose, but it seems difficult to combine those with .NET. I don't think the documentation describes how to do this. There's documentation on how to combine Kotlin/Compose with Java/Views and there is documentation that describes how to combine Java with C#.

What is the recommended approach for building modern Android apps with .NET?

[rokmeglic71]

From my experience, if you stick with the default MAUI approach, it works well. If you stray too far from the official documentation with unusual combinations, you’re more likely to encounter quirks and end up on your own. In my view, MAUI is a really solid tool for mobile development—especially when paired with C# library re-usage, Visual Studio, regular MAUI updates, and an active community.

Example? FAB Menu. MAUI does not support it, but you can do it in XYZ way.

Hope this helps.