Being more than an Android developer
summary
Advocates moving beyond “Android developer” into full‑stack care: learn continuously, push design and product to match platform realities, and automate collaboration. Uses concrete tools and practices — Jenkins/CI, Retrofit/Realm, Dagger/data binding, Kotlin, Postman/Charles/Stetho, Google Play staged rollouts — and metrics: cites 30% increase in sign‑ins from Smart Lock adoption and insists keep crash rate under 1% with staged releases and CI before shipping. Practice small PRs, testing parties, and versioned builds.
AI-written summary · about
chapters (4)
related talks
26mKeynote: Being more than an Android Developer
49mBe Like Water: Keeping Up with Android
36mAndroid to Full-Stack: A Devs Journey to the Great Unknown
26mFacing the Anxiety of Being the Only Android Engineer
37mHow Android development experience applies outside Android development
30mWhat I Learned in Two Years as an Android Engineer
25mFOMO - How an Android dev cut through the noise and build proactive learning habits
45mFor Beginners and Career Changers: Android App Development Today and Key Points in 40 Minutes