The effects of Kotlin inside Android apps and libraries
summary
Analysis of the Google I/O scheduling app (300 Kotlin files, 176 JARs → 16 DEX) shows concrete effects: Kotlin stdlib ~1.4MB, coroutines ~1.5MB; enabling minify with ProGuard shrinks text-bytes by 73% and APK size by 55%; removing Kotlin null checks and intrinsics saves ~32KB; ProGuard and DexGuard handle Kotlin metadata and can rename hard-coded names, while R8 lags on some string renames; an open-source Kotlin metadata printer exposes the protobuffer metadata so obfuscation keeps runtime compatibility.
AI-written summary · about
chapters (9)
- 0:00Introduction to Kotlin impact
- 1:38Kotlin runtime libraries overview
- 4:10Kotlin constructs in bytecode
- 8:49Optimizing with ProGuard
- 12:47Kotlin-specific optimizations
- 17:23Kotlin metadata structure
- 23:20Metadata files and reflection
- 27:35Optimization tips and resources
- 31:14Conclusion and Q&A intro
related talks
49mKotlin on Android (en)
01h 03mKotlin on Android
20mState of Kotlin in Android
38mState of Kotlin for Android
52mPowered by Kotlin
41mKotlin for Android Developers
42mThe Future of Android, Kotlin and Everything
03h 23mKotlin 1.4 Online Event, Day 3: Kotlin everywhere: Android, Mobile Multiplatform, Kotlin/JS
