Getting to 100% Kotlin: A practical guide
summary
Basecamp converts a ~20,000-line Android app to 100% Kotlin over 430 days with two engineers and uses Android Studio’s autoconverter as a starting tool that delivers roughly 60% from autoconverter. The practical plan: start with small conversions (POJOs, utilities, adapters), do work during cooldowns or when touching Java files, learn a few idioms (flow control, collections, extension functions), accept a messy 50/50 phase, avoid perfectionism, and prioritize customers while converting incrementally.
AI-written summary · about
chapters (11)
- 0:00Introduction to Kotlin journey
- 4:39Start with small Kotlin conversions
- 9:30Forget about perfect Kotlin
- 13:19Learn key Kotlin concepts
- 16:05Use the Kotlin auto-converter
- 18:29Convert during cooldowns
- 21:21Expect the ugly transition phase
- 23:05Avoid overusing Kotlin features
- 26:33Organize Kotlin code carefully
- 27:57Prioritize customer needs
- 29:42Take your time with conversion
related talks
31mGetting to 100% Kotlin: A Practical Guide
33mPragmatic Kotlin on Android
35mPractical Tips For Legacy Java Codebases Conversion Into Kotlin
33mTravelling across Asia - Our journey from Java to Kotlin
31mA Kotlin Journey
35mAt long last we have Kotlin first at Meta!
16mThe Journey From Legacy Code to Idiomatic Kotlin
42mKotlin Adoption in the Giant Java Application