Why Projects Succeed: Lessons Learned from the Android OS
summary
Project starts as two people building a camera OS then is acquired by Google in 2005 after a 3,000 lines of JavaScript demo; the team builds from kernel up, adds wake locks, chooses Java and implements the Dalvik runtime and DEX format, ships SDK with Eclipse plugin and emulator, pivots for touchscreen, launches 1.0 on G1 in 2008, achieves hockey-stick growth after Droid, and by 2021 runs on 3 billion devices.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:11MAN SPONSOR
- 2:33Availability
- 3:382003: FotoFarm
- 4:122004: No Takers
- 5:522005: Pitch Time
- 7:00July 2005: Acquisition
- 7:452005 - 2008: The Race to 1.0
- 13:012007: iPhone!
- 14:47October 2008: Made it!
- 15:442009: Where Are the Users?
- 16:542010: The Hockey Stick Starts
- 18:28Success Was Not Pre-Ordained
- 19:31Success Factors
- 19:51The Team
- 23:52Key Decisions
- 28:31Timing
- 30:20What Can We Learn from Android?
related talks
01h 10mWhy 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
45mLessons from Android development at Google
01h 00mAndroid at Scale
55mPlan to Throw the First One Away
43mThe Engineering Playbook for Growing Android Teams
31mFrom Closed To Collaborative: Perspectives and Lessons From Qualcomm’s Open Development Experience
