What I Learned in Two Years as an Android Engineer
summary
Covers practical lessons from two years as an Android engineer: break features into small testable implementations (examples: setOnClickListener, XML onClick, data binding, Butter Knife), verify libraries before adopting (moved from Volley to OkHttp due to SDK issues), prefer support libraries (use support-v4 fragments), test early on real devices (recommends Nexus 5), and enforce coding style, auto-formatting, and design documents to speed reviews and onboarding.
AI-written summary · about
chapters (7)
- 0:00Two years of Android learning
- 1:40Breaking features into parts
- 7:21Choosing tech and libraries
- 17:10Material Design compatibility
- 20:42Real devices in development
- 25:00Solo vs team differences
- 29:39Summary
related talks
26mKeynote: Being more than an Android Developer
34mBeing more than an Android developer
49mBe Like Water: Keeping Up with Android
47m15 Things I Learned Switching from iOS to Android Development
52m20 Years in the Field and Still Plenty of Questions
32mBest findings in Kotlin for Android
32mA Designer’s Challenge: Trying Android Engineering
42m12 Years On: A Retrospective
