15 Things I Learned Switching from iOS to Android Development
summary
Fifteen concrete lessons map what actually changed: Kotlin, Jetpack Compose, coroutines become the working stack, app lifecycle and state restoration behave differently, and device/os distribution forces different testing. Specific process moves: code retros and phased beta testing expose bad prior‑art ports and justify refactors. Personal takeaways include the steep painful learning curve, using focused scope to avoid ballooning work, and tracking visible progress over months rather than comparing to long‑time Android engineers.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 3:10Patterns
- 6:32Same but different
- 7:17fragmentation
- 9:17app life cycle
- 11:18levels of understanding
- 14:00process learning
- 14:14making technical decisions
- 16:56the siren sounds of prior art
- 19:56scope is life
- 22:07know your stakeholders
- 24:17be triaging
- 26:30personal learnings
- 29:00dont compare yourself
- 31:27software development is a team sport
- 33:48find your corner
- 36:11intuition
- 37:31introspection
- 39:17rest
- 41:42summary
- 42:28process
- 43:28personal
related talks
43m10 Years of Android Development: The Retrospective
16mThe Android Experience seen from an iOS dev's perspective
42m10 years of Android Development: The Retrospective
45mFor Beginners and Career Changers: Android App Development Today and Key Points in 40 Minutes
49mBe Like Water: Keeping Up with Android
01h 01mKeynote! 10 years of Android development: the retrospective
43mWhat a Long Strange Trip it's Been: A Year In Android
38mBuilding Android apps in 2022