Before Android 8.0 Oreo, notifications were a free-for-all. Apps could post anything at any priority, change importance on the fly, and users had limited control. A messaging app and a spammy game had the same ability to interrupt you.
Author: Nadia Malik
Project Treble: How Android Fixed Its Update Problem
In 2017, the average Android phone received exactly one major OS update — if the manufacturer felt generous. The reason wasn’t laziness. It was architecture. Every Android update required chipset vendors (Qualcomm, MediaTek, Samsung) to recompile their driver code against the new framework. Vendors had no financial incentive to update old chipsets. Manufacturers couldn’t update devices even if they wanted to.
Seamless Updates: A/B Partitioning Explained
For a decade, updating Android meant watching a screen that said “Android is upgrading… Optimizing app 1 of 87” for 10–20 minutes while your phone was completely unusable. If the update failed — corrupted download, power loss, bug — your phone might not boot at all.
Android’s Multitasking Evolution: From Single-Task to Split-Screen
The first Android phone — the T-Mobile G1 — could run exactly one app at a time. When you pressed Home, the previous app was suspended. When you launched a new app, the old one died. Multitasking meant switching between apps, not running them simultaneously.