Gradle, navigable
Browse Gradle tasks in the UI — less archaeology, more shipping.
01 Thesis
Stop acting as a human router between editors, terminals, and device pickers.
This extension wires VS Code to the Gradle + AGP + SDK stack you already use — tasks, targets, and install in one flow.
build.gradle stays the source of truth; controls sit next to the code.
With agents in VS Code, fewer forced trips to a full IDE for routine Gradle or device steps — stay in one surface.
02 The hidden tax
Compilers are fast. Friction isn’t. It lives around the compile button.
- Gradle in the wrong working directory
- Guessing which device is attached
- Install steps that don’t live next to your code
That’s fragmentation — not “how Android is.” This tool aims to own the loop from the editor, without replacing your build.
03 The arsenal
A cockpit, not a junk drawer — Gradle, targets, install, detection.
Targets, unambiguous
Pick devices and emulators with enough context to choose on purpose.
Build → install, relentless
Tight loop: build, push, verify — repeat until it runs on hardware.
Projects, detected
Android Gradle projects surface with sane defaults for normal repos.
04 The loop
Linear flow — write → build → target → install → run.
- Write
- Build
- Target
- Install
- Run
05 Principles
Less theater around the toolchain.
- Respect Gradle — UI on top, not a replacement.
- Match CI — local runs should align with what pipelines enforce.
- Plain SDK/ADB — same binaries, visible flows.
06 Compatibility
Expects a normal Android/Gradle layout, AGP, SDK, and local.properties where applicable.
07 Reality check
Independent extension — not from Google or Gradle. Not a replacement for Android Studio when you need the full IDE; it optimizes the daily write → build → target → prove loop in VS Code.
It does not: rewrite your Gradle files, replace Studio for niche tooling, or magic away the SDK.
09 Open source
Issues and PRs: github.com/AndroidGradleTools
10 License
MIT — see the repository for exact terms.