20 Years in the Field and Still Plenty of Questions
summary
A senior Android engineer shares concrete testing prescriptions from 20 years of experience: allocate about 40% to unit tests and 30% to integration tests, and adopt a coherent testing policy instead of ad-hoc manual checks. He contrasts RxJava’s steep learning curve with simpler stacks like Room, Retrofit, LiveData and ViewModel, and describes automated testing practices (screenshots, permissions, airplane mode) that can consume roughly 30% of development time, based on work building players and apps at Deezer and Sony.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 10:42Android dev evolution
- 24:28From idea to product
- 36:07Unit tests and quality
- 45:00Tech culture and UX
- 50:18Q&A
related talks
55mShifting the Testing Role Pendulum
30mWhat I Learned in Two Years as an Android Engineer
42m12 Years On: A Retrospective
34mBeing more than an Android developer
42m10 years of Android Development: The Retrospective
44m30 years in testing – Battles won and battles lost
45mFor Beginners and Career Changers: Android App Development Today and Key Points in 40 Minutes
26mKeynote: Being more than an Android Developer