如何无需每次安装APK运行Android程序？求Android Studio启动提速方案

Hey there! As someone who's spent countless hours tweaking Android Studio to speed up my dev workflow, let's tackle your two questions with practical, tried-and-true solutions:

You don't have to reinstall the APK every time you make a change—here are the most common ways to run updated code/resources without a full install:

• Android Studio's Apply Changes (Official Tool)
  This is the go-to for most devs. When you make code changes (Java/Kotlin logic) or modify resources (layouts, drawables), just click the lightning bolt icon ("Apply Changes") in the toolbar. It pushes only the updated parts to your running app, either restarting the affected activity or applying changes instantly (no restart needed for some code tweaks). Note that changes to the AndroidManifest.xml, native code, or app signing configs still require a full reinstall, but 90% of daily edits work with this.

• ADB Push for Manual Resource/File Updates
  If you prefer command-line workflows, you can use adb push to replace specific files on the device without reinstalling. For example, to update a drawable:

  adb push ./app/src/main/res/drawable/ic_updated_icon.png /data/data/com.your.app.package/app_drawable/
  

  This works best for debug builds (since you need access to the app's data directory) and is great for automation scripts, but it's less convenient than the official Apply Changes.

• Hot Reload for Jetpack Compose
  If you're using Jetpack Compose, Android Studio's live preview lets you see UI changes in real-time without even restarting the app. For full runtime changes, the Apply Changes feature works seamlessly with Compose too—most UI tweaks take effect instantly.

Cutting down on reinstalls is key to speeding up your workflow—here's how to optimize:

• Maximize Apply Changes Efficiency
  First, make sure the feature is enabled: Go to Settings > Build, Execution, Deployment > Deployment > Apply Changes and check all relevant options (like "Apply code changes without restarting activity"). When you run your app in Debug mode, this feature is active by default. Instead of clicking "Run" every time, use "Apply Changes" after edits—this skips the full APK install and launch process entirely.

• Tweak Run Configuration for Faster Launches
  In your Run Configuration, under "Launch Options", set "Launch" to "Do not launch activity". This way, if your app is already running on the device, Android Studio won't kill and restart it when you apply changes. You can just switch back to the running app to see updates.

• Modularize Your Project
  Split your app into modules (e.g., app, feature_profile, core_utils). When you modify code in a single library module, Android Studio only recompiles that module and pushes the update—no need to rebuild the entire APK. This drastically cuts down on build time, especially for large projects.

• Disable Unnecessary Debug Build Steps
  In your app's build.gradle file, turn off time-consuming steps for Debug builds to speed up compilation:

  android {
      buildTypes {
          debug {
              minifyEnabled false       // No obfuscation needed for debug
              shrinkResources false     // Skip resource shrinking
              lintOptions {
                  checkReleaseBuilds false
                  abortOnError false    // Don't halt builds on lint warnings
              }
          }
      }
  }
  

• Enable Gradle Build Cache
  Go to Settings > Build, Execution, Deployment > Build Tools > Gradle and check "Enable Gradle build cache". This caches previous build outputs, so repeated builds reuse cached results instead of recompiling everything from scratch. It makes both full builds and Apply Changes much faster.

内容的提问来源于stack exchange，提问作者Mark Caveneau