Why Projects Succeed: Lessons learned from the Android OS
summary
Starts as a camera OS, gets bought by Google in 2005 with basically 3,000 lines of JavaScript, and the tiny team builds drivers, a Linux-based stack, and chooses Java then ships the Dalvik VM and an SDK plus Android Market. Less than 100 people at 1.0 cheer at 50,000 users, then a 2010 hockey-stick growth after carrier devices. Openness and per-app sandboxes drive manufacturer trust; the platform scales to billions. Recent work replaces the old toolkit with a reactive Compose using Kotlin and compiler plugins.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 1:10Android’s early history
- 3:35From cameras to phones
- 10:57Building Android from scratch
- 17:16Impact of the iPhone
- 22:30Android’s slow start
- 26:40Why Android succeeded
- 31:38Team focus and culture
- 44:13Lessons for project success
- 57:14Android’s evolution
- 58:58Case study: Jetpack Compose
- 1:08:00Q&A
related talks
35mWhy Projects Succeed: Lessons Learned from the Android OS
46mWhy Projects Succeed: Lessons Learned from the Android OS
52mKeynote: Why Projects Succeed: Lessons Learned from the Android OS
27mComedy Talk
01h 00mAndroid at Scale
45mLessons from Android development at Google
45mThe Android Decade
43mThe Engineering Playbook for Growing Android Teams