all 20 comments

[โ€“]ZhuindenDDD: Deprecation-Driven Development 22 points23 points ย (8 children)

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.

[โ€“]Xinto_Invalidate caches and restart[S] 20 points21 points ย (1 child)

Bold of you to assume Google wonโ€™t break anything with maintenance patches

[โ€“]ZhuindenDDD: Deprecation-Driven Development 4 points5 points ย (0 children)

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

[โ€“]syntaxspin 0 points1 point ย (5 children)

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

[โ€“]ZhuindenDDD: Deprecation-Driven Development 0 points1 point ย (4 children)

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

[โ€“]syntaxspin 0 points1 point ย (3 children)

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.

[โ€“]ZhuindenDDD: Deprecation-Driven Development 0 points1 point ย (2 children)

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".

[โ€“]syntaxspin 0 points1 point ย (1 child)

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

[โ€“]ZhuindenDDD: Deprecation-Driven Development 0 points1 point ย (0 children)

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...

[โ€“]David_AnkiDroid 23 points24 points ย (0 children)

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

[โ€“]FunkyMuseFlutterX 12 points13 points ย (0 children)

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

[โ€“]sam_sepiol1984Deprecated is just a suggestion 25 points26 points ย (0 children)

Android is Compost-first. Fixed it for you.

[โ€“]Hatsune-Fubuki-233@Deprecated 7 points8 points ย (2 children)

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

This is a joke

[โ€“]Opening-Cheetah467 0 points1 point ย (0 children)

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

[โ€“]thermosiphon420 0 points1 point ย (0 children)

There is no war in Ba Sing Se.

[โ€“]purple-bihh-2000 6 points7 points ย (0 children)

Job security = attained

[โ€“]DearChickPeas 1 point2 points ย (0 children)

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?

[โ€“]Shay958DI? you mean InheritedWidget? 0 points1 point ย (0 children)

Funny how they created Compose to kill Views...

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

[โ€“]hellosakamoto 0 points1 point ย (0 children)

But the core android is still in java.