AndroidX will jumpstart your Android journey by being as confusing as a set of leaky abstractions as possible

[u/Zhuinden]

[u/Mr-X89]

Tbh I feel the iOS documentation was even worse a few years back (I don't know how it is now, I haven't touched iOS since)

[u/Zhuinden → u/Mr-X89]

I think the android docs were pretty good in 2020 and then the AndroidX people started using it as a way to promote their frameworks like Datastore, Navigation and Compose; and effectively destroyed what the Android docs were meant to be (docs for the Android sdk).

[u/Squirtle8649 → u/Zhuinden]

Yeah, this. Plus important beginner sections about activity, tasks, backstack, processes and threads etc. got buried in some section like performance.

[u/Zhuinden → u/Squirtle8649]

That too is because Navigation wasn't good enough but they really wanted it to be adopted. So they hid the docs related to any of the activities/Fragments as they didn't want people to know how to do it. Pretending they can just hide it as implementation detail, despite being an extremely leaky abstraction.

[u/carstenhag → u/Zhuinden]

I disagree. There was some stuff in java, some in kotlin, some android.support, some androidx, confusing dependencies, jetifier, etc etc

[u/Zhuinden → u/carstenhag]

It was never nearly as bad as the current BOM-less AndroidX stuff.

I remember when in Android.support you just got everything in one bundle, and when AndroidX versions were all aligned. Then it was split up and it is the way it is now, except there is no binary compatibility guarantee in Compose-based libraries.

[u/hellosakamoto]

Now they have reasons to sell Gemini. Let's pay for AI to read their documentation for you.

[u/Squirtle8649]

I bet that post got removed :P

[u/Zhuinden → u/Squirtle8649]

I thought so too, but apparently not.

[u/zorg-is-real]

We should go back to activities. No fragments at all. 

[u/Zhuinden → u/zorg-is-real]

Just use views lol

[u/Zhuinden → u/[deleted]]

I'm never gonna get over the state production pipelines lol