Skip to content

Compatibility

Use this page to quickly confirm whether your current development environment and target capability are within Jugg's supported range. See the corresponding capability page for specific trigger conditions, outcomes, and limitations.

Environment compatibility

ItemSupported range
Android StudioBumblebee through Quail
IntelliJ IDEA2021.1.3 through 2025.1 Beta
AGP3.4 through 9.1
Gradle5.4.1 through 9.2.1
Kotlin1.3 through 2.2
target API21 through 36
Android devicesAndroid 8 through 16
  • The current Android Studio compatibility implementations cover Chipmunk through Quail. Bumblebee uses the implementation for older versions.
  • Verified AGP versions include 3.4.2, 3.5.4, 4.1.3, 4.2.0, 7.2.2, 8.3.0, 8.7.0, 8.13.0, and 9.1.2.
  • Gradle compatibility has been verified with 5.4.1, 6.8, 7.3.3, and 9.2.1. Gradle 8.x is also supported.
  • Android 8 through 10 use compatibility deployment. Android 11 and later support standard incremental deployment.

NOTE

The version ranges represent the compatibility boundaries covered by Jugg. Intermediate versions that are not listed as verified usually work directly. If you encounter a compatibility problem, submit a report through the plugin's Report issues action.

Capability support

AreaSupported capabilities
CompilationSource compilation, recompilation, resource compilation, AndroidManifest compilation, so updates, DataBinding/ViewBinding, Kotlin Compose, KMP and Compose Multiplatform, annotation processors, custom compilers, incremental compilation of dependencies, AabResGuard
DeploymentMultiple APKs, multiple devices
Android TestApplication Android Test, Library Android Test, Test Results UI, Logcat attribution
Agents, CLI, and MCPAgent Skills, Jugg CLI, build and deployment, Android Test CLI, runtime and devices, UI automation, UI layout evidence, remote diagnostics, MCP
  • Release compilation is experimental.
  • Changes to Gradle scripts, dependencies, variants, source sets, or complex plugin configuration require a Gradle build.
  • Android Test is disabled by default and prompts you to enable it the first time you use it.
  • Agent, CLI, and MCP features must be installed manually before use.