Reexamining Developer Advice from the First droidcon
summary
Compares advice from 2009 to 2024 and finds which rules still matter: keep long work off the UI thread, use StrictMode for thread/resource issues, test on real devices for battery and performance but use emulators plus Firebase Test Lab or BrowserStack for scale, and prefer vector drawables over nine-patch. Shows AI prompts versus human answers, cites tools like Charles/Fiddler for network faults, notes Pixel 8 class hardware invalidates some early optimizations and foldables remain a special case.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 10:05From books to engineering
- 19:46Field testing philosophy
- 23:28Modern Android performance
- 30:47Hardware future
- 32:52Conclusion
related talks
31mDangerous Minds: How we're getting developer education wrong
30mBehind The Screen: The Humans Who Use Our Code
43mGood or bad - a key skill for developers
26mKeynote: Being more than an Android Developer
42m12 Years On: A Retrospective
34mBeing more than an Android developer
42m10 years of Android Development: The Retrospective
49mBe Like Water: Keeping Up with Android
