Roundtable: process for your Android team
summary
Eight Android developers at Dashlane, 45–55 at Disney Streaming, 18 at Gorillas (grew from eight), and 30+ across Trainline — teams split into small feature squads with platform squad support; practices include SonarQube quality gates on GitLab merge requests, monorepo sharing, emoji-driven code reviews, heavy pair programming and onboarding checklists. One team shipped a full app in Jetpack Compose before it was stable and reports it worked. Continuous small refactors reduce tech debt.
AI-written summary · about
chapters (13)
- 0:00Start
- 16:33Core Teams
- 17:06Sharing Knowledge
- 18:21How We Handle Onboarding
- 20:46Onboarding Sessions
- 21:59How Do You End Up Sharing Sharing History about Features
- 31:54How Do You Work with Co-Worker in a Different Time Zone Are There any Challenges Uh When We Remote Workers Are Part of a Team
- 33:17Separate Sub Teams per Time Zone
- 34:57Platform Work versus Tech Depth and Feature Work
- 36:55The Android Platform Squad
- 38:18Building a Successful Team
- 39:43How Do You Make Sure that Your Team Members Stay up to Date on Its Onward Knowledge
- 44:10Onboarding
related talks
01h 00mAndroid at Scale
01h 32mLeveling Up: Panel Discussion
43mThe Engineering Playbook for Growing Android Teams
51mBuilding Effective Teams of Competent, Friendly People
21mScaling Android at PagesJaunes
29mGrowing Your Team While Remaining Efficient
41mBuilding Mobile Apps At Scale
39mSurprise! Neighboring Code Reviews