Android Canary 2603 Blur Effect: How the New Transition Animation Works

Google has released Android Canary 2603, a public testing build that adds a blur filter to the app-launch transition, among a broader set of UI changes. Android Authority reported the blur addition about two months ago, noting that tapping an app from the home screen or app drawer now triggers a progressively intensifying blur layered over the existing pinch zoom animation. When you return to the home screen, the effect reverses, icons sharpening back into place. The whole sequence moves fast enough that most users will never consciously notice it.

The build carries version number ZP11.260220.007 and is available for Pixel 6 and later devices and the Pixel Tablet, per Android Authority. Google has delivered new Canary builds on a monthly cadence since launching the program last summer, the same report notes, and an updated SDK was expected in the days following the 2603 release.

Beyond the blur, the build includes separate Quick Settings tiles for Wi-Fi and mobile data, an app lock feature, and a redesigned long-press menu. Each of those changes is notable on its own. The blur, though, sits in a different category: it extends a visual treatment that Android has been applying to static UI surfaces for nearly a year into the animation layer for the first time.

How the new Android app launch blur works

Until Canary 2603, every blur effect in Android lived on a layer at rest. The frosted-glass backdrop behind Quick Settings, the overlay on the app drawer, the recents screen treatment, all of these apply blur while the user is already stopped somewhere in the UI.

The new effect is different. As the home screen zooms toward the app being launched, a blur filter grows in intensity alongside the existing pinch animation. Return to the home screen and it plays back in reverse, the icons moving into position and sharpening as they settle, according to Android Authority. The source's description: it happens so quickly that users might never notice it.

That speed is deliberate. The effect isn't meant to draw attention to itself. It reinforces the transition's sense of depth without interrupting the action.

Static blur and transition blur are doing different work. Static blur marks a surface as background, creating visual separation between the layer in front and the content behind. Transition blur manages attention during movement. As the home screen becomes irrelevant to what the user is about to do, it progressively disappears into soft focus rather than snapping away abruptly. The home screen doesn't cut out; it recedes.

What makes the timing of this notable is context. Background blur arrived across the app drawer, Quick Settings panel, recents screen, and lock screen in Android 16 QPR1 Beta 1, as Android Authority reported about a year ago. That covered every major static surface in the system UI. Canary 2603 is the first build where blur has moved into the animation layer itself, applied to something in motion rather than rendered once beneath a panel.

Whether Google intends this as a deliberate continuation of the static blur rollout or a separate experiment is not confirmed by the available reporting.

What else changed in Canary 2603

The blur is the most visually distinctive addition, but Canary 2603 includes several other functional changes worth noting.

Quick Settings now has separate tiles for Wi-Fi and mobile data, per Android Authority. Previously a single combined control, the split lets users toggle each connection independently, which is a practical change for anyone who frequently switches between networks.

The app lock feature, also new in this build, lets users lock individual apps behind a PIN, password, or fingerprint. When an app is locked, notifications, widgets, and shortcuts are hidden. The lock is activated by long-pressing the app icon, the same gesture that now also triggers a redesigned context menu. App shortcuts in that menu are hidden by default in this build.

Screen recording got a post-recording summary page. After stopping a recording, users see a new screen with options to replay, edit in Google Photos, delete, or share the recording, rather than being dropped back to wherever they were.

The long-press menu also now surfaces a bubbling option, letting users float an app as a movable overlay anywhere on the screen. The bubble can be dismissed via long-press on the icon or through a Manage button.

These are all pre-release features in a Canary build. None carry confirmed timelines for stable availability.

The practical limits already built into Android's blur handling

The blur addition in Canary 2603 doesn't arrive in isolation. Android already has two documented mechanisms for managing blur's costs, and both are relevant to understanding what the transition blur might look like in practice.

On power, the cost is documented. Background blur consumes more battery, and when it arrived across static surfaces in Android 16 QPR1 Beta 1, Battery Saver disabled it automatically. Android Authority confirmed this on test devices about a year ago: enabling Battery Saver turns background blur off.

Whether Canary 2603's transition blur follows the same Battery Saver behavior isn't documented yet. Because the animation is brief, the power overhead may differ from persistent static blur. That's an open variable.

On readability, Android added a "Reduce blur effects" accessibility toggle, first spotted in the 2509 Canary build last September. The toggle disables background blur system-wide, with a stated purpose of making "backgrounds and panels easier to see," according to Android Authority. It replaced the old "allow window-level blurs" setting that had been buried in Developer Options, moving it into standard accessibility settings where users without developer mode enabled can actually reach it.

What the reporting doesn't confirm is whether that toggle's scope covers transition blur. Its current description refers to backgrounds and panels, which maps cleanly to static surfaces. Whether it also suppresses the app-launch animation is unknown. That question is minor when the only motion blur is a brief transition. It becomes more relevant if blur continues expanding into other animation states.

On hardware availability, Canary 2603 is currently limited to Pixel 6 and later devices and the Pixel Tablet, per Android Authority. Whether the transition blur reaches the broader Android ecosystem, stays Pixel-exclusive, or gets revised before a stable release is not yet known.

What the next builds will confirm

Canary is a testing channel, not a release channel. Features that appear here don't always reach stable unchanged, and earlier blur additions arrived in Canary and beta without confirmed stable timelines, as Android Authority noted when reporting on the accessibility toggle last September. The transition blur in 2603 carries the same uncertainty.

Three specific questions subsequent builds can answer: Does Battery Saver suppress the transition blur the way it does static surface blur? Does "Reduce blur effects" extend its coverage to motion states? Do future Canary releases apply blur to additional animation moments beyond app launch?

The blur-plus-Battery Saver behavior surfaced quickly after background blur arrived on static surfaces, suggesting Google tests that interaction early. A similar confirmation for transition blur, or an explicit absence of one, would clarify how Google is categorizing the new effect internally.

What the last year of Canary and beta builds establishes is a sequence: background blur on static surfaces in Android 16 QPR1, an accessibility toggle to manage readability in the 2509 Canary build, and now blur in the app-launch animation itself. Each step came with documented behavior around power and accessibility costs, as the Android 16 QPR1 reporting showed. Whether Canary 2603 continues that sequence or represents a feature that gets dialed back under hardware and battery pressure is what the coming builds will determine.