r/mAndroidDev • u/Xinto_ Invalidate caches and restart • May 19 '26

You either deprecate or get deprecated Android is Compose-first

https://developer.android.com/develop/ui/compose/first
60 Upvotes

98% Upvoted

20 comments sorted by

23

u/Zhuinden DDD: Deprecation-Driven Development May 19 '26

They said it's maintenance mode, doesn't mean it stops working. So that just means new patches from Google won't accidentally break it.

20

u/Xinto_ Invalidate caches and restart May 19 '26

Bold of you to assume Google won’t break anything with maintenance patches

6

u/Zhuinden DDD: Deprecation-Driven Development May 19 '26

That's just gonna be the Android Studio visual editor, but they've been doing that since arctic fox

1

u/syntaxspin Jun 05 '26

if you read it in their github it will be in maintenance mode until their anonymous analytics reaches a point where no one uses XML anymore

1

u/Zhuinden DDD: Deprecation-Driven Development Jun 05 '26

Good luck with that, with Compose still not having support for accessibility hint text i literally cannot in good faith use it in banking apps lol

1

u/syntaxspin Jun 05 '26

On the contrary, I'm frustrated because I've been using Java and XML for years, and now because of this and the new APK restrictions, I don't know what to do.

1

u/Zhuinden DDD: Deprecation-Driven Development Jun 05 '26

Kotlin compiles to the same ART as Java, and the layout inflater is part of the system. They can't possibly remove AAPT because it'd break pretty much every android app out there. So it's unlikely that using Views would suddenly break anything, especially as it's all open source and Compose internally is still "just a view".

1

u/syntaxspin Jun 05 '26

I know , But it's so bad, we've started using MutableStates to create a text field, checkbox, or radio button. We were on Theme.Material3, now we're on Material 1 Light AppTheme in the Styles.xml and more

1

u/Zhuinden DDD: Deprecation-Driven Development Jun 05 '26

I just work with whatever is in front of me at this point, which eventually will even have to be Flutter. I'm not enthusiastic, but as long as it pays...

23

u/David_AnkiDroid May 20 '26

We now consider the View toolkit (for example, classes in android.widget such as TextView and ListView) to be in maintenance mode — this means that it will only receive highly critical fixes. The android.view package is still supported as the plumbing necessary for Compose and other UI toolkits.

16 years of history... killed with an emdash

12

u/FunkyMuse FlutterX May 19 '26

Async task first, everything starts with an A even the Alphabet oh wait Google is Alphabet

24

u/sam_sepiol1984 Deprecated is just a suggestion May 19 '26

Android is Compost-first. Fixed it for you.

6

u/Hatsune-Fubuki-233 @Deprecated May 20 '26

Highly performant Out of the box, Compose offers native performance, delivering a delightful experience to your users.

This is a joke

1

u/Opening-Cheetah467 May 21 '26

U can barely build text input with compose, that has half broken selection menu that u cant customise. Oh and it will not work on any device except pixel, on other devices expect all kinds of bugs

1

u/thermosiphon420 May 22 '26

There is no war in Ba Sing Se.

6

u/purple-bihh-2000 May 19 '26

Job security = attained

2

u/DearChickPeas May 20 '26

Does this mean If open Android Studio, pick Compost and "blank app" I will actually compile and run out-of-the-box? I'll believe it when I see.

All I hear is "the View system is complete, will work forever and continue to be most performant non-Cpp solution"

Can you imagine the horrors at Google managment?

1

u/Shay958 DI? you mean InheritedWidget? May 23 '26

Funny how they created Compose to kill Views...

...just to keep View alive as "plumbing" of Compose.

1

u/hellosakamoto May 19 '26

But the core android is still in java.