Every Android/KMP developer has experienced it. - A bug is fixed. - The PR is merged. - The code is ready. Then everyone waits for the Play Store or the Sprint! We've accepted APK/bundle releases as the only way to deliver Android/KMP application, but what if Kotlin itself could become the deployment unit? In this session, we'll explore an entirely different approach to Android/KMP feature delivery, one where standard Kotlin is compiled into a compact intermediate representation, securely delivered over the air, and executed inside a sandboxed runtime while still interacting with native Android APIs and rendering real Jetpack Compose UI. Rather than focusing on a specific framework, we'll walk through the architecture behind modern Kotlin OTA systems: - Why APKs became the deployment boundary - Why JSON/DSL based approaches eventually hit architectural limits - How Kotlin compiler plugins can transform source into portable bytecode - Designing a secure on-device runtime without downloading DEX files - Keeping downloaded code Play-compliant using capability isolation and cryptographic verification - Making OTA execution feel indistinguishable from normal Android/KMP development We'll also discuss the engineering challenges nobody talks about: - Compiler version compatibility - Runtime versioning - Compose integration - Performance trade-offs - Security boundaries - Developer experience If you're interested in Kotlin engineering, Android/KMP internals, Kotlin, Compose, or simply curious about what the next generation of Android/KMP app delivery could look like, this session will give you an inside look at one possible future.