How is Lezhin Comics Applying Kotlin?
summary
Resin Comics migrated their Android app from Java to Kotlin, increasing Kotlin code from ~10–20% to over 50% in about 1.5 years by writing all new features in Kotlin and porting Java during refactors. They use Android-specific Kotlin features—Kotlin Android Extensions, data classes, null-safety, lazy/val, higher-order functions, and collection APIs (reducing Rx)—and run ktlint, while noting practical issues with kapt/annotation processors (Dagger, data binding), the need for clean builds, harder hiring for Kotlin-experienced developers, and a 2–3 month real-work ramp-up period.
AI-written summary · about
chapters (15)
- 0:00Intro
- 6:07Pros: Java Interop
- 6:56Pros: Lambda Expression
- 8:52Pros: Higher order function
- 12:14Pros: Kotlin Extension
- 14:48Pros: Android Extension
- 15:33Pros: Lazy Evaluation
- 18:16Pros: Collection API
- 20:18Pros: Readability, Productivity
- 23:45Pros: Confidence
- 28:22Problem: FP Novice
- 29:10Problem: Code Artist?
- 30:12Problem: Difficulty Hiring Developers
- 33:20Tips: Code Review
- 35:47Tips: Progressive
