Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
AndroidX akan menggantikan API support library asli dengan paket dalam
namespace androidx. Hanya nama artefak Maven dan paket yang berubah; nama class,
metode, dan kolom tidak berubah.
Prasyarat
Sebelum bermigrasi, update aplikasi Anda.
Sebaiknya update project untuk menggunakan support
library versi akhir: versi 28.0.0.
Ini karena artefak AndroidX dengan versi 1.0.0 adalah biner yang setara dengan
artefak Support Library 28.0.0.
Pemetaan
Jika Anda mengalami masalah karena project Anda belum sepenuhnya dimigrasikan ke AndroidX,
lihat tabel berikut untuk menentukan pemetaan yang tepat dari support library
ke artefak dan class AndroidX yang sesuai:
Konten dan contoh kode di halaman ini tunduk kepada lisensi yang dijelaskan dalam Lisensi Konten. Java dan OpenJDK adalah merek dagang atau merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-07-26 UTC.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-26 UTC."],[],[],null,["# Migrate to AndroidX\n\nAndroidX replaces the original support library APIs with packages in the\n`androidx` namespace. Only the package and Maven artifact names changed; class,\nmethod, and field names did not change.\n| **Caution:** As of late 2021, most of the library ecosystem already supports AndroidX natively. This means that your project is most likely already using AndroidX libraries directly and there is no need to follow the steps in this migration guide. Additionally, the [`enableJetifier`](#migrate_an_existing_project_using_android_studio) flag mentioned in this guide can lead to slower build times and should not be used unless it's necessary.\n|\n|\n| If your project already has the `enableJetifier` flag and it's\n| turned on, you can run Build Analyzer's Jetifier check to confirm if it's\n| actually needed. The Build Analyzer check is available starting in\n| [Android Studio Chipmunk](/studio/preview/features#jetifier-build-analyzer).\n\nPrerequisites\n-------------\n\nBefore you migrate, bring your app up to date.\nWe recommend updating your project to use the final version of the support\nlibrary: [version 28.0.0](/topic/libraries/support-library/revisions#28-0-0).\nThis is because AndroidX artifacts with version 1.0.0 are binary equivalent to\nthe Support Library 28.0.0 artifacts.\n| **Note:** We recommend working in a separate branch when migrating. Also try to avoid refactoring your code while performing the migration.\n\nMappings\n--------\n\nIf you run into issues because your project hasn't fully migrated to AndroidX,\nrefer to these tables to determine the proper mappings from the support library\nto the corresponding AndroidX artifacts and classes:\n\n- [Maven artifact mappings](/jetpack/androidx/migrate/artifact-mappings)\n- [Class mappings](/jetpack/androidx/migrate/class-mappings)\n\nFor the latest versions of the Jetpack libraries, see the [versions\npage](/jetpack/androidx/versions).\n\nAdditional resources\n--------------------\n\nTo learn more about migrating your code to AndroidX, see the following\nadditional resources:\n\n### Blog posts\n\n- [Cross-stitching Plaid and AndroidX](https://medium.com/androiddevelopers/cross-stitching-plaid-and-androidx-7603a192348e)\n- [Migrating to AndroidX: Tip, Tricks, and Guidance](https://medium.com/androiddevelopers/migrating-to-androidx-tip-tricks-and-guidance-88d5de238876)\n\n### Videos\n\n- [Migrating to AndroidX: the time is right](https://www.youtube.com/watch?v=Hyt7LR5mXLc)"]]
