Published November 19, 2026

Android Studio Rabbit 3 Reaches RC 1: Journeys, Compose Migration, and What Flutter Teams Actually Get

Android Studio Rabbit 3 RC 1 arrived on the Beta channel on November 11. For anyone who tracks these releases, the important word is not Rabbit, and it is not RC. It is the sentence that appears in the release candidate definition on the preview page: the feature set for the next version has been stabilized.

Rabbit 2 has been the stable channel since late October. With Rabbit 3 now frozen in release candidate form, the version that follows it is essentially decided, and the remaining weeks are about regressions rather than ideas. That is the right moment for a Flutter team to decide whether any of it changes their daily work.

The release post itself is thin. Rabbit 3 RC 1 lists exactly one fixed issue: a crash when opening layout XML files, tracked as issue 583343830. If that is the whole changelog, the story is not in the changelog.

The two features Rabbit 3 is carrying

The preview release notes describe two additions, and they point in the same direction as everything else Google shipped this year: less manual work, more agent execution.

The first is Migrations in Android Studio. Studio can now take a project built with the old views system and convert it into a Kotlin and Jetpack Compose application, producing a project that is functional and ready for testing rather than a half-finished diff. It is the sort of migration that agencies quote in weeks and that reviewers dread, which explains why Google built a tool for it.

The second is Agentic Journeys. You describe an end-to-end user flow in natural language, and the agent runs it on a connected device or emulator, stepping through the flow, verifying expected outcomes, and producing a pass or fail report with screenshots attached. Journeys can be created, edited, or run from the Agent window, or launched from a journey file with the Run button in the toolbar.

Neither feature targets Flutter directly. Migrations converts Android views to Compose, and Compose is what Flutter replaced for the teams who chose Flutter. Journeys reasons about screens and state in an Android app. Read the release notes as a Flutter developer and it is easy to conclude that this one is not for you.

Where a Flutter project actually touches this release

It touches it in three places, and two of them are dull in the way that infrastructure is always dull until it breaks.

The first is the layout XML crash. Most Flutter apps will never open a layout file, but add-to-app projects do. The moment a Flutter module lives inside a host Android app, someone on the team is editing activity layouts, theme files, and manifest include fragments in Studio. A crash on opening those files is not a curiosity for that team; it is the reason the preview build gets uninstalled.

The second is the Gradle and AGP surface. The current version table published with the preview notes lists Android Studio Rabbit 2 on the stable channel, Android Gradle Plugin 9.5.0 as stable, Rabbit 3 as the release candidate, and Stingray 1 on canary. Flutter's Android build rides on AGP and Gradle, and Flutter's own tooling enforces a supported range. Rabbit 3 stabilizing alongside the AGP 9.5.0 line means the next Studio upgrade does not drag an AGP jump behind it, which is the usual source of a broken build on a Monday morning.

The third is the thing that quietly improves for everyone: the emulator, Logcat, the device manager, and the profiler. Flutter developers lean on Studio for those even when the Dart code lives in another editor, and every release candidate in that chain tends to ship fixes that never make the release notes.

What is queued behind it

Stingray 1, already on canary, shows where the tooling is going, and two of its items are worth watching from a distance.

  • Test suites in the Android Gradle plugin: named suites that group unit, instrumented, and asset tests, each with its own source sets, dependencies, test engines, and target variants.
  • A Compose Preview Screenshot Testing tool that generates HTML reports for visual regression review.
  • Model Assignment, which lets you point complex agent reasoning at a pro-tier model and latency-sensitive chores at a lighter one.

Screenshot testing in particular is the kind of capability Flutter developers already take for granted through golden tests, and watching Android build the equivalent is a reminder of how much of Flutter's value sits in the toolchain rather than the widget catalogue.

The practical recommendation is unchanged from every previous cycle. If your Flutter app is on stable Flutter and stable AGP, do not move to a Beta IDE build to get Journeys. Install it alongside, keep it out of the critical path, and let the release candidate soak for a few weeks. If you maintain a plugin with an Android side, or you are shipping an add-to-app module, the layout XML fix alone justifies installing RC 1 on a second machine this week and opening the host project.

Rabbit 3 will be judged by how boring its stable release is. On the evidence of one fixed issue and a feature set frozen three weeks after the canary line started, that is exactly what Google appears to be aiming for.