Migrating from Autovalue to Kotlin Data Classes
summary
Migrating 46 AutoValue classes to Kotlin data classes removes AutoValue and its plugins, reduces boilerplate, and replaces four dependencies while adding one (removed 4 dependencies, added JSON value). An IntelliJ/Android Studio refactoring plugin automates conversion and renames Java/Kotlin call sites, preserving Java-friendly with/create helpers. Clean builds run more than a minute faster and incremental edits improve, APK size stays unchanged, startup time edges up slightly, and Kotlinx.serialization is initially three times slower but after optimizations is now comparable to GSON/Moshi.
AI-written summary · about
chapters (11)
- 0:00Introduction to migration
- 0:20What is AutoValue
- 3:31Why use AutoValue
- 4:36How AutoValue works
- 7:48Why migrate to Kotlin
- 10:36Kotlin serialization options
- 18:07Migration process overview
- 19:15Demo of IntelliJ plugin
- 24:52Handling Java compatibility
- 25:56Testing and results
- 27:31Q&A session








