Metadawhat? Managing compatibility of your Kotlin apps and libraries
summary
Covers problems that appear when upgrading to a new Kotlin version—Gradle errors, transitive dependency issues, runtime failures on older Android releases, and cache misses—and examines the guarantees provided by ecosystem components. Presents tools and metadata-based techniques to precisely manage the evolution and compatibility of Kotlin apps and libraries.
AI-written summary · about
chapters (15)
- 0:00Compatibility introduction
- 1:42Java and Kotlin challenges
- 4:13Avoid Gradle toolchains
- 5:39Kotlin source, API and target
- 7:26Kotlin metadata discovery
- 9:54Kotlin metadata versions
- 11:40Kotlin retrocompatibility
- 12:21Android compatibility specifics
- 14:51D8 and Java desugaring
- 15:54Android API lint checks
- 16:37Gradle metadata role
- 18:00Gradle Kotlin tooling
- 19:26Kotlin Multiplatform compatibility
- 20:47Tool version recommendations
- 21:10Best practices
related talks
36mBest practices for evolving Kotlin libraries
17mKotlin Library API Design and Compatibility Challenges
41mThe future of dependency management, seen from 2022
59mHow to Evolve Your Kotlin Library Painlessly for Clients
16mHow to get satisfaction from ungrateful work: A journey into updating Kotlin
42mEvolving your Kotlin API painlessly for clients- 42mEvolving your Kotlin API painlessly for clients
26mUpgrading Meta's Kotlin Infrastructure to K2