Skip to content

Android Studio plugin

Jugg

Incremental compile and deploy for large Android projects.Reuse Gradle output, handle the current delta,and fall back when state cannot be trusted.

RUNtrusted baseline
  1. Detect changesRead source, resource, Manifest, and device state changes.
  2. Compile deltaReuse the Gradle baseline and compile changed or impacted sources.
  3. Stage artifactsPrepare DEX, resource overlays, assets, and other local outputs.
  4. Deploy safelyChoose hot reload, restart, overlay, reinstall, or Gradle fallback by state.
< 3saverage compile time
40k+monthly compiles
800k+total compiles
36k+ hwaiting time saved

Start here

Choose by the task in front of you

01First setup

Install the plugin, create a run configuration, and produce the first trusted Gradle baseline.

02Run your app

Understand how incremental compile, deploy, and cancellation behave after pressing Run.

03Learn the boundaries

Follow the path from Gradle baseline to resource link, impact analysis, and mixed deploy.

04Diagnose a problem

Start from compile, deploy, runtime, logs, or performance symptoms.

What Jugg optimizes

Reduce fixed Run costs that are larger than the current edit

Safety model

Jugg does not replace Gradle

Jugg treats Gradle output as the trusted starting point. First runs, build file changes, dependency or compiler option changes, uncertain annotation or instrumentation results, and inconsistent deploy history all return to Gradle before the next incremental run.

Directory

Complete documentation