Android is now Compose First - Future of .NET Android & MAUI?

[cjrvdev]

Android framework version

Other

Affected platform version

ALL

Description

In the recent days Android has been declared Compose-first and therefore the old Views approach is being deprecated (maintenance mode, but read between lines...). As far as I know both .NET Android and MAUI are built upon Views system and has never been compatible with Jetpack Compose way of building screens.

What is the future of these technologies? Has Microsoft decided something regarding the future of develpment in C# or at some point whenever Google decides to fully remove these old APIs we will be left abandoned?

Please let us know the future ahead! Thanks!

Source: https://developer.android.com/develop/ui/compose/first

Steps to Reproduce

Be a developer! 💃🏻

Did you find any workaround?

No response

Relevant log output

[gmck]

@cjrvdev
I'm very interested in your observations, especially your "but read between the lines" comment. I'm thinking along similar lines. I tried to start a similar conversation when I recently reported the "Preview 3 and Preview 4 can't create an Android 37 emulator" issue #11387. However, that is now closed, as it should be, so you can only view it by changing it to a “closed” issue. I can also see that you follow me on my GitHub page, but when I follow you back, I still can't see your email address. If you are interested in sharing your ideas, I'd appreciate being able to share future ideas, preferably by finding a suitable public forum to continue, as this obviously isn’t the right place. Please email me if you are interested. I’ve just modified my p4 repo to make my GoogleSignInFragment comply with the new API 37 rules, so I’m going to add it to one of my existing projects on my GitHub page to explain what is required.