Why Projects Succeed: Lessons Learned from the Android OS
summary
Begins as a camera OS in 2003 then pivots to phones, gets acquired in 2005 and ships Android 1.0 in 2008 after a tiny team (few dozen engineers, only three writing code early on) builds kernel drivers, a Java-based runtime (the Dalvik runtime), an SDK and app store, and open-sourced AOSP. Key claims: compatibility enforced by CDD and CTS compatibility tests, GPU-first graphics with OpenGL, and a demo of 3,000 lines of JavaScript that proves the vision — it works and scales to billions.
AI-written summary · about
chapters (23)
- 0:00Intro
- 2:00History of Android
- 6:13Why Google bought Android
- 11:10The iPhone
- 13:37Android 10 release
- 14:58Timeline
- 17:06Why did it work
- 17:38The team
- 18:59Leadership
- 21:03Decisions
- 24:40Timing
- 27:52Why Projects Succeed
- 28:10Lessons Learned
- 30:48Competition
- 31:39Hard work
- 32:28Shipping
- 33:25Keep going
- 34:15Timing helps
- 35:04Luck
- 35:19Analyzing Luck
- 35:45Jetpack Compose
- 42:13Questions
- 42:30QA
related talks
35mWhy Projects Succeed: Lessons Learned from the Android OS
01h 10mWhy Projects Succeed: Lessons learned from the Android OS
52mKeynote: Why Projects Succeed: Lessons Learned from the Android OS
59mAndroid History, from the Inside
01h 01mAn Android Retrospective
27mComedy Talk
32mAndroid Open Source: What more can we do with Android?
46mIntroduction to AOSP, or How to Spend a Night Building Android