# An update on Android KTX

DevFeed: [An update on Android KTX](<https://devfeed.tech/articles/an-update-on-android-ktx-20915.md>)

Original publisher: [Read original article](<https://jakewharton.com/an-update-on-android-ktx/>)

Published: 2026-04-01T00:00:00Z

Content type: article

Language: en

Sources: [Jake Wharton](<https://devfeed.tech/sources/jake-wharton.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [library](<https://devfeed.tech/tags/library.md>), [update](<https://devfeed.tech/tags/update.md>)

## AI overview

Android KTX extension libraries are being wound down because their Kotlin extensions have been merged into the corresponding AndroidX libraries. The article lists obsolete or soon-to-be-obsolete KTX modules and notes that developers may eventually receive Lint warnings to help migrate their code.

## Source excerpt

Eight years ago we launched a library of Kotlin extensions for the Android platform, Android KTX. In the time since, the library became Core KTX, and numerous other KTX libraries were written for other AndroidX libraries. And while KTX's approach to adding Kotlin niceties was built on a strong technology foundation, we've made the difficult decision to begin winding down our KTX extension libraries1. That's right folks-toss another entry on the Killed By Google board! Despite the date this is no joke. However, mourn not, friends. The KTX libraries were killed because the adoption of Kotlin has been such a resounding success. All extensions have now been merged directly into their respective main library. Woo! Below is a table of every library which had a -ktx module and the first version where it became empty and thus obsolete. KTX library Obsolete in version activity-ktx 1.9.0 appsearch-ktx None, empty2 collection-ktx 1.3.0 concurrent-futures-ktx 1.4.0-alpha0134 core-ktx 1.19.0-alpha0134 dynamicanimation-ktx 1.2.0-alpha0134 fragment-ktx 1.9.0-alpha0134 lifecycle-livedata-ktx 2.7.0 lifecycle-livedata-core-ktx 2.8.0 lifecycle-reactivestreams-ktx 2.6.0 lifecycle-runtime-ktx 2.8.0 lifecycle-viewmodel-ktx 2.8.0 loader-ktx 1.2.0-alpha0134 navigation-common-ktx 2.4.0 navigation-fragment-ktx 2.4.0 navigation-runtime-ktx 2.4.0 navigation-ui-ktx 2.4.0 paging-common-ktx 3.0.0 paging-runtime-ktx 3.0.0 paging-rxjava2-ktx 3.0.0 palette-ktx 1.1.0-alpha0134 preference-ktx 1.3.0-alpha0134 savedstate-ktx 1.3.0 security-crypto-ktx None, deprecated5 sqlite-ktx 2.7.0-alpha0334 tracing-ktx 1.3.0 transition-ktx 1.8.0-alpha0134 watchface-complications-data-source-ktx 1.4.0-alpha0134 work-runtime-ktx 2.9.0 There is a feature request on Lint to provide a warning when you are declaring a KTX library equal to or newer than when it became obsolete. Hopefully this will be implemented and can aid in migrating your codebase over time. I had the privilege of starting the KTX libraries. And I also