Lightning Talk: Beyond Good Enough: Why We Want a Kotlin API and SDK
summary
Embrace wants an idiomatic Kotlin path because Java APIs are merely workable on Android and break for Kotlin Multiplatform and fragile mobile runtimes. A pure Kotlin API shim already wraps the Java SDK in the open-telemetry-kotlin and Embrace repos so Android apps get Kotlin-style tracers and spans today; three engineers are productionizing it internally. Plan is an incremental rollout toward a mobile-first Kotlin native SDK that handles intermittent networks, process death, context models, and KMP use cases.
AI-written summary · about
chapters (9)
- 0:00Kotlin-first observability intro
- 1:02Java SDK limits on Android
- 3:12Kotlin multiplatform needs native
- 5:19Mobile context challenges
- 6:21Fragile mobile runtimes
- 7:26Java SDK paper cuts
- 8:31Kotlin API solution
- 9:58Kotlin-native SDK need
- 12:48Summary and call
related talks
43mAndroid Jetpack ❤️ Kotlin: On the road to more wholesome APIs
41mApollo-Android: a Journey to Kotlin Multiplatform
36mBluetooth + Kotlin: It's a Match!
55mIntro & Keynote
40mAndroid Jetpack: Sweetening Kotlin development with Android KTX
38mBuilding Android apps in 2022
03h 23mKotlin 1.4 Online Event, Day 3: Kotlin everywhere: Android, Mobile Multiplatform, Kotlin/JS
41mAdvancing android development with the kotlin language
