Android CLI 1.0 and Compose 1.11: what June 2026’s developer tooling wave means for your workflow
June 2026 is quietly becoming one of the most consequential months for Android developer tooling in years. Android CLI reached stable 1.0, Jetpack Compose 1.11 landed with layout primitives developers have requested since the toolkit’s launch, and the Android Studio Quail release train delivered a patch release plus a steady run of Quail 2 canaries. None of these arrived with keynote fanfare — but together they change how Android apps get built, tested, and debugged in the agent-assisted era.
Android CLI graduates to stable 1.0
The biggest structural shift is Android CLI hitting version 1.0. What started as a convenience layer over Gradle, adb, and SDK tooling is now a supported, stable surface — and Google is positioning it as the integration point for AI coding agents in Android workflows.
Programmatic version lookup
The 1.0 release introduces programmatic version lookup, letting scripts and agents query SDK, build-tools, and dependency versions without parsing human-readable output. For CI pipelines this removes a whole class of brittle regex-based version checks. Build scripts can now resolve the installed toolchain state deterministically and fail fast when an environment drifts from the project’s requirements.
Journeys support from the command line
Journeys — the natural-language UI testing flows introduced alongside Android Studio’s I/O Edition release — can now be authored and executed from the CLI. That makes Journey-based tests viable in headless CI for the first time, rather than being an IDE-only convenience. Teams that adopted Journeys after the Android Studio I/O Edition tooling announcements can now gate merges on the same flows locally and in automation.
The Studio bridge: agents driving the IDE
The most forward-looking 1.0 capability is bridging: the new studio command lets external agents integrate directly with a running Android Studio instance. An agent can open projects, trigger builds, run inspections, and read results — turning the IDE from a human-only surface into an automation target. Combined with the platform’s agent-first direction visible in efforts like Microsoft’s Project Solara AOSP build, the trajectory is clear: command-line and agent-driven development is becoming a first-class Android workflow, not a hack.
Jetpack Compose 1.11: Grid, FlexBox, and accessibility by default
Compose 1.11 is the kind of release that looks incremental in the changelog and transformative in day-to-day code.
New layout primitives: Grid and FlexBox
Compose finally ships first-party Grid and FlexBox layout primitives. Until now, grid-like arrangements meant LazyVerticalGrid (scroll-coupled), nested Rows and Columns (verbose and fragile), or custom Layout implementations (expensive to maintain). The new primitives handle non-lazy, intrinsically measured grid and flex arrangements directly — closing one of the longest-standing gaps versus both the web’s CSS toolkit and classic ConstraintLayout. Form layouts, dashboard tiles, and adaptive two-pane arrangements built for the foldable wave described in our Android 17 API deep dive get dramatically simpler.
Trackpad support and new testing APIs
With Android increasingly running on laptops and large-screen devices, Compose 1.11 adds proper trackpad support — hover states, precision scrolling, and gesture differentiation — along with testing APIs that can simulate trackpad input. If your app targets Googlebooks or desktop-class form factors, these tests belong in your suite now, before user reports arrive.
Built-in focus rings
Accessibility gets a structural upgrade: focus rings are now built into Compose’s focus system rather than hand-rolled per component. Keyboard and d-pad navigation renders a consistent, theme-aware focus indicator by default. Apps that implemented custom focus visuals should audit for double-ring rendering after upgrading.
Android Studio Quail: patches, canaries, and LeakCanary in the IDE
The Quail release train kept its cadence through early June: Quail 1 Patch 1 shipped stability fixes for the stable channel, while Quail 2 moved through Canary 5, 6, and 7.
LeakCanary profiler task
The standout addition is the LeakCanary profiler task, which brings memory-leak trace analysis directly into the IDE’s profiling workflow. Instead of digging through device logs or in-app LeakCanary reports, developers can capture, inspect, and diff leak traces in the same window as CPU and memory profiling. For teams chasing the memory regressions that surfaced in recent platform updates — like those addressed in Android 17 QPR1 Beta 4 — this shortens the repro-to-fix loop considerably.
What developers should do now
Adopt in this order. First, upgrade CI to Android CLI 1.0 and replace any version-parsing scripts with programmatic lookup — this is low-risk and immediately removes fragility. Second, bump to Compose 1.11 in a feature branch and run your full UI test suite; pay attention to focus-ring rendering and any custom grid implementations that the new primitives can replace. Third, if you ship to large-screen or Googlebook form factors, add trackpad input tests using the new APIs. Fourth, try the LeakCanary profiler task on your worst-known memory path — it requires no code changes for apps already shipping LeakCanary. Finally, experiment with the studio bridge in a sandbox project before wiring agents into production workflows; the surface is new and conventions are still forming.
The fastest starting point: update the CLI with sdkmanager tooling, then run android –version to confirm 1.0, and check your Compose BOM against the 1.11 release in File → Project Structure → Dependencies inside Android Studio.