Facing the Anxiety of Being the Only Android Engineer
summary
An Android engineer describes surviving as the sole Android dev since 2017 by shipping a full rewrite of the RadioTalk app, later hiring a contractor, and standardizing on Kotlin + Jetpack. Concrete tactics include following Android Kotlin Fundamentals, studying OSS examples (Sunflower, Ixodes/DroidKaigi app), and adopting ViewModel + Repository + Kotlin Flow/coroutines with sealed classes and unidirectional data flow; they also instrument events, build KPI dashboards, own documentation and tech‑lead tasks to improve release cadence and reduce anxiety.
AI-written summary · about
chapters (8)
- 0:00Only Android engineer
- 2:54Android techniques
- 8:54Reading quality code
- 15:55Architecture vs anxiety
- 17:42Expanding knowledge
- 21:30Service understanding
- 22:32Engineering services
- 25:19Overcoming anxiety
related talks
34mBeing more than an Android developer
26mKeynote: Being more than an Android Developer
49mBe Like Water: Keeping Up with Android
49mThe Lonely App Development Class of a Jock Female Engineer
25mFOMO - How an Android dev cut through the noise and build proactive learning habits
36mAndroid to Full-Stack: A Devs Journey to the Great Unknown
32mA Designer’s Challenge: Trying Android Engineering
58mModern Android Development