Java to Kotlin Migration Mistakes
summary
Led a migration from a Java MVVM app using RxJava and Dagger to Kotlin over about four to five months, and the converter proves imperfect: in/out generics get wrong, automatic nullability creates nullable model fields that break APIs and DB schemas, and Java statics become companion objects instead of const val constants. Lessons: migrate models and abstractions first, then business logic, UI last; prefer Kotlin data classes and single‑expression functions; test framework compatibility (some libraries are not Kotlin‑friendly).
AI-written summary · about
chapters (7)
related talks
46mThe Road to Kotlintown
35mPractical Tips For Legacy Java Codebases Conversion Into Kotlin
31mArchitecture metamorphosis: a real case study
39mKotlin, Practically Speaking
31mDesign Patterns with Kotlin
33mTravelling across Asia - Our journey from Java to Kotlin
33mPragmatic Kotlin on Android
34mFunctional Android
