36･15 Cash App
summary
1300 modules, roughly 50–60 Android developers, and ~40–56 million customers drive a concrete engineering picture: protobufs via Wire, Retrofit/OkHttp networking, SQLDelight DB, Compose with molecule presenters, testing with Turbine, and Paparazzi snapshot UI tests; CI uses in‑house Kochiko and Broadway runs navigation (not open source). Built features include a debug drawer, mock mode that lets features run offline, remote feature flags with staged rollouts, and presenter migration tools that actually reduce friction—these systems work in production.
AI-written summary · about
chapters (22)
- 0:00Cash App Android architecture
- 3:19Screens from network to UI
- 5:46Database with SQL Delight
- 7:09Backend services and reactive managers
- 9:37Reactive UI with Jetpack Compose
- 11:01MVW architecture and UDF
- 13:09View events and sealed classes
- 15:13Presenter lifecycle and molecule
- 17:15Testing with Turbine
- 20:25UI testing with Paparazzi
- 23:56UI variations with Paparazzi
- 27:10Navigation and routing
- 30:39Broadway navigator and transitions
- 33:30App flavors and builds
- 35:18Debug drawer and feature flags
- 37:44Development workflow and PR
- 40:49Code review and checks
- 42:35CI pipeline and optimization
- 44:03Continuous delivery and APK
- 44:46Design system and tokens
- 46:09Team structure and development
- 47:12Remote code execution future
related talks
49mBuilding for the future at Snapchat
39mScaling an Android App from 1 to 100 developers with modularization.
37mTackling Android Development at Scale
48mMobile Developer Productivity at Scale
40mSubito, Android Development at Scale
32mRoad to modularization
43mThe Engineering Playbook for Growing Android Teams
43mAndroid Dev Tools and Workflows