Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Untuk mendapatkan pengalaman pengguna terbaik, Anda harus mengoptimalkan aplikasi agar sekecil
dan secepat mungkin. Pengoptimal aplikasi kami, yang disebut R8, menyederhanakan aplikasi Anda dengan
menghapus kode dan resource yang tidak terpakai, menulis ulang kode untuk mengoptimalkan performa runtime, dan banyak lagi. Bagi pengguna Anda, hal ini berarti:
Untuk mengaktifkan pengoptimalan aplikasi, tetapkan isMinifyEnabled = true (untuk pengoptimalan kode)
dan isShrinkResources = true (untuk pengoptimalan resource) dalam skrip build tingkat aplikasi build rilis seperti yang ditunjukkan dalam kode berikut. Sebaiknya Anda selalu mengaktifkan kedua setelan tersebut. Sebaiknya aktifkan pengoptimalan aplikasi hanya di versi akhir aplikasi yang Anda uji sebelum dipublikasikan—biasanya build rilis—karena pengoptimalan meningkatkan waktu build project dan dapat mempersulit proses debug karena cara pengoptimalan memodifikasi kode.
Selain itu, pastikan R8 menggunakan kemampuan pengoptimalan penuhnya dengan menghapus baris ini dari file gradle.properties project Anda, jika ada:
android.enableR8.fullMode=false# Remove this line from your codebase.
Perhatikan bahwa mengaktifkan pengoptimalan aplikasi membuat pelacakan tumpukan sulit dipahami,
terutama jika R8 mengganti nama class atau metode. Untuk mendapatkan pelacakan tumpukan yang
sesuai dengan kode sumber Anda, lihat
Memulihkan pelacakan tumpukan asli.
Jika R8 diaktifkan, Anda juga harus membuat Profil Startup untuk performa startup yang lebih baik.
Jika Anda mengaktifkan pengoptimalan aplikasi dan menyebabkan error, berikut beberapa strategi untuk memperbaikinya:
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-30 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-30 UTC."],[],[],null,["# Enable app optimization\n\nFor the best user experience, you should optimize your app to make it as small\nand fast as possible. Our app optimizer, called R8, streamlines your app by\nremoving unused code and resources, rewriting code to optimize runtime\nperformance, and more. To your users, this means:\n\n- Faster startup time\n- Improved rendering and runtime performance\n- Fewer [ANRs](/topic/performance/anrs/keep-your-app-responsive)\n\n| **Important:** You should always enable optimization for your app's release build; however, you probably don't want to enable it for tests or libraries. For more information about using R8 with tests, see [Test and troubleshoot the\n| optimization](/topic/performance/app-optimization/test-and-troubleshoot-the-optimization). For more information about enabling R8 from libraries, see [Optimization for library authors](/topic/performance/app-optimization/library-optimization).\n\nTo enable app optimization, set `isMinifyEnabled = true` (for code optimization)\nand `isShrinkResources = true` (for resource optimization) in your [release\nbuild's](/studio/publish/preparing#turn-off-debugging) app-level build script as shown in the following code. We recommend\nthat you always enable both settings. We also recommend enabling app\noptimization only in the final version of your app that you test before\npublishing---usually your release build---because the optimizations increase the\nbuild time of your project and can make debugging harder due to the way it\nmodifies code. \n\n### Kotlin\n\n```kotlin\nandroid {\n buildTypes {\n release {\n\n // Enables code-related app optimization.\n isMinifyEnabled = true\n\n // Enables resource shrinking.\n isShrinkResources = true\n\n proguardFiles(\n // Default file with automatically generated optimization rules.\n getDefaultProguardFile(\"proguard-android-optimize.txt\"),\n\n ...\n )\n ...\n }\n }\n ...\n}\n```\n\n### Groovy\n\n```groovy\nandroid {\n buildTypes {\n release {\n\n // Enables code-related app optimization.\n minifyEnabled true\n\n // Enables resource shrinking.\n shrinkResources true\n\n // Default file with automatically generated optimization rules.\n proguardFiles getDefaultProguardFile('proguard-android-optimize.txt')\n\n ...\n }\n }\n}\n```\n\nAdditionally, verify that R8 uses its full optimization capabilities by\nremoving this line from your project's `gradle.properties` file, if it exists: \n\n android.enableR8.fullMode=false # Remove this line from your codebase.\n\nNote that enabling app optimization makes stack traces difficult to understand,\nespecially if R8 renames class or method names. To get stack traces that\ncorrectly correspond to your source code, see\n[Recover the original stack trace](/topic/performance/app-optimization/test-and-troubleshoot-the-optimization#recover-original-stack-trace).\n\nIf R8 is enabled, you should also [create Startup Profiles](/topic/performance/baselineprofiles/dex-layout-optimizations) for even better\nstartup performance.\n\nIf you enable app optimization and it causes errors, here are some strategies to\nfix them:\n\n- [Add keep rules](/topic/performance/app-optimization/add-keep-rules) to keep some code untouched.\n- [Adopt optimizations incrementally](/topic/performance/app-optimization/adopt-optimizations-incrementally).\n- Update your code to [use libraries that are better suited for optimization](/topic/performance/app-optimization/choose-libraries-wisely).\n\n| **Caution:** Tools that replace or modify R8's output can negatively impact runtime performance. R8 is careful about including and testing many optimizations at the code level, in [DEX layout](/topic/performance/app-optimization/6), and in correctly producing Baseline Profiles - other tools producing or modifying DEX files may break these optimizations, or otherwise regress performance."]]