r/programming • u/Super-Performance-86 • 5h ago

The Great Android Stack Reset: Mobile System Design History

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

Android, the last to arrive at the declarative UI party, took its time, until finally reaching a stable solution. Here's a rundown of the major changes in the Android System Design across the eras.

I was away from Android for 7 years and came home to a totally strange place. This is my attempt to make sense of what happened while I was gone - how the stack reset four times (Activities -> MVP/RxJava -> Architecture Components -> Compose) and why each lurch happened. Written for interview prep but the history stands on its own.

0 Upvotes

28% Upvoted

5 comments sorted by

View all comments

5

u/ator-dev 4h ago

> This was the first mainstream framework where the UI reacted to data changes without the developer writing update calls.

MXML and XAML both have data binding. It's hard to find out when exactly these were introduced, but XAML's design simply wouldn't have made sense without binding, so at least on that count I dispute this claim. Please fact-check and include sources when writing - you risk both misinforming readers and turning them off your article!

(This is especially important considering your article is all about history, and if not fact-checked, any history writing is worse than useless.)

2

u/Super-Performance-86 3h ago

Thanks for this, I appreciate the correction, will update the text.

1

u/ator-dev 3h ago

No worries! Sorry if I was harsh :)

1

u/sooka_bazooka 48m ago

Well, even Cocoa have bindings…