Improving Developer Experience On Byte At a Time
summary
Build system middleware ByteX uses the Android Gradle Transform API and ASM to host isolated bytecode plugins that run as a single transform task, process class files in parallel, and cut redundant IO so builds and CI become measurably faster. Examples include a usage-metrics scanner that outputs JSON/CSV, dead-code and resource removal, getter/setter inlining, and reference-check fixes. Developed for a 600-engineer mobile org shipping weekly to ~1B DAU, the approach works but must migrate to AGP instrumentation APIs for newer Gradle versions.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:08Developer experience importance
- 5:04Why care about DX
- 8:16DX scale at TikTok
- 10:03DX team challenges
- 11:05ByteDex and bytecode plugin
- 17:16Gradle Transform API and ASM
- 18:40ByteX motivations
- 20:44ByteX infrastructure and plugins
- 22:06ByteX in action
- 22:48SDK metrics plugin
- 27:43Build optimization
- 28:50Memory and stability check
- 30:14Getter/setter inlining
- 31:19ByteX and Gradle
- 33:03ByteX benefits and scalability
- 35:07Bytecode with AGP 8
- 36:13Closing
related talks
37mBuild bigger, better: Gradle for large projects
41mScaling Productivity: How we have improved our dev experience
31mImproving Android Build performance
19mCOMPILING...? HOW TO REDUCE YOUR WAIT TIMES AND "GET BACK TO WORK"
48mMobile Developer Productivity at Scale
36mImproving Android Developer Experience with Gradle Build Scans
36mImproving Gradle Builds
33mTools of the Trade