How Android development experience applies outside Android development
summary
Describes how Android engineering skills transfer to backend and iOS work and leadership: moved from Android to writing Go server code, doing Kotlin Android and Swift iOS feature development, and managing engineering. Gives concrete tooling and stack used—Room, sqlc, Android Studio/IntelliJ, VS Code, Docker, PostgreSQL, GitHub Actions—and advises maintaining deep Android expertise while spending about 10% of time exploring adjacent technologies.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 3:16Speaker background
- 8:36Android outside Android
- 10:01Transferable skills
- 14:21Testing across languages
- 16:12IDE and tooling
- 19:26ORM and database design
- 21:15Hands-on labs
- 23:22Breadth vs depth
- 24:25Communication and leadership
- 26:34Management skills
- 28:39Engineering resources
- 30:45Community role
- 33:34Focus on Android
- 35:20Why Android matters
- 36:05Building confidence
- 36:47Closing
related talks
36mAndroid to Full-Stack: A Devs Journey to the Great Unknown
34mBeing more than an Android developer
26mKeynote: Being more than an Android Developer
39mI’m an iOS Engineer, So I Can Build Android Apps Too…
49mBe Like Water: Keeping Up with Android
30mWhat I Learned in Two Years as an Android Engineer
26mFacing the Anxiety of Being the Only Android Engineer
38mThe Highway That Trains Androiders and Where We Landed After Real-World Battles