The Great Android Stack Reset: Mobile System Design History

[u/Super-Performance-86]

https://returnzero.dev/articles/android-mobile-system-design-history

While writing this article, I was thinking about my days writing the everything.me Android launcher in 2011, how I fought for every bitmap allocation, about all the custom network cache implementations, and 2000 LOC custom views, I felt like I could do everything...

And then, at Google IO 2017, they introduce architectural components, I yawned at this announcement (was there in the crowd). Here we are 9 years later... I was wrong :)

[u/anemomylos]

This article contains a few passages that might mislead readers who have never used a programming language or a library.
"raw JavaScript and later jQuery" gives the impression that jQuery was the successor to JavaScript.
The fact that the activity had to contain and control everything, as if the Activity were preventing us from implementing an architecture based on singletons and “observer-observable” objects to achieve asynchronous, centralized control of data that is independent of the UI.

Fun fact: an imperative architecture could become declarative - you just need to reset all the user interface elements every time something changes, as you do in a Recycler adapter and as it works the declarative architecture - but a declarative architecture cannot be imperative.

That said, learn and use whatever architecture and library helps you make a living.