Keynote: Android Development
summary
Platform claim: Android’s reality is constrained — about 1.4 billion 30-day actives across ~4,000 distinct devices, and 50 billion installs per year — so memory, CPU and GPU limits drive correctness and UX choices. Runtime specifics: ART cuts GC pauses from ~20–30 ms to ~3–5 ms but GC-for-all pauses still freeze the UI when allocations fragment the heap. Practical tools and fixes include allocation tracker (DDMS/Android Studio Monitor), test on 512 MB devices, keep APKs small, cache for flaky networks, and read the “understanding the mobile context” series (Slides: https://sites.google.com/site/android...).
AI-written summary · about
chapters (13)
- 0:00Welcome
- 5:39Introducing Chad
- 8:13Android challenges
- 12:03User expectations
- 14:55Memory limits
- 21:40Memory equals performance
- 23:05Garbage collection
- 28:19Hardware diversity
- 31:27Dalvik vs ART
- 35:57UI thread bottlenecks
- 37:40Storage and network
- 40:51Best practices
- 42:43Q&A
related talks
51mKeynote: Modern Android Development
46mOpening Keynote: Android Then & Now
35mKeynote: Trash Talk: The Evolution of Android Garbage Collection
46mDeveloping for Android: the Naughty Bits
45mHigh performance in Android
01h 01mAn Android Retrospective
40mAndroid high performance baby
37mUnderstanding Android Runtime (ART) for faster apps