Google has recently unveiled that connected display support for Android has achieved general availability with the release of Android 16 QPR3. This milestone is pivotal for both developers and users, particularly those utilizing supported Pixel and Samsung devices, as it facilitates seamless smartphone-to-desktop workflows.
What connected displays actually do
When a compatible Android phone or foldable device is linked to an external display, a new desktop session is initiated on that display, while the phone retains its independent state. A taskbar on the connected display showcases active applications and enables users to pin apps for swift access. This setup allows multiple applications to run side by side in freely resizable windows, enhancing multitasking capabilities.
In contrast, when a tablet, such as the Samsung Galaxy Tab S11, connects to an external display, the desktop session extends across both screens, creating a unified system. This configuration permits app windows, content, and the cursor to transition fluidly between the displays.
Currently, connected displays are supported on the Pixel 8, 9, and 10 series, along with various Samsung devices including the Galaxy S26, Fold7, Flip7, and Tab S11.
A Google-Samsung collaboration
The collaboration between Google and Samsung has been instrumental in delivering this desktop windowing experience across the Android ecosystem. This partnership underscores the ongoing co-development efforts between the two tech giants, particularly regarding Android platform features. Notably, Samsung’s One UI 7 update in April 2025 highlighted how intertwined their software decisions can be, as it replaced Google Discover with Samsung News on swipe panels.
The connected display feature was initially showcased at Google I/O 2025 and has since progressed through development stages to reach its current general availability in the QPR3 release, which stands for Quarterly Platform Release—a mid-cycle update track that Google employs to introduce new features and fixes between major Android versions.
What changed in QPR3
In his announcement, Romano detailed that the Android 16 QPR3 release has refined three critical aspects of the connected display experience: windowing behaviors, taskbar interactions, and input compatibility, specifically for mouse and keyboard usage. Additionally, the release introduced compatibility enhancements to scale windows appropriately and mitigate app restarts when switching displays—an essential consideration for developers whose applications may struggle with display configuration changes.
Developers are advised to pay attention to three technical areas: first, apps should not presume a constant Display object, as this can change when a window transitions to a different display or when display configurations shift. Second, external displays often possess different pixel densities compared to a phone’s primary screen, necessitating careful management of density-independent pixels (dp) and density-specific resources. Lastly, connected display setups generally involve external peripherals like keyboards, mice, and webcams, which apps designed primarily for touchscreens may not accommodate effectively.
New window size classes: Large and Extra-large
The most significant enhancement in Jetpack WindowManager 1.5.0 is the introduction of two new width window size classes: Large and Extra-large. These classes serve as official viewport breakpoints to assist developers in crafting adaptive layouts. The new classifications are defined as follows:
- Large: for widths between 1200dp and 1600dp
- Extra-large: for widths at or exceeding 1600dp
This update allows for more sophisticated layouts; for instance, an email client could display multiple panes simultaneously on an Extra-large monitor, enhancing user experience and productivity.
To implement these new breakpoints, developers need to adjust their code from WindowSizeClass.BREAKPOINTSV1 to WindowSizeClass.BREAKPOINTSV2. The Compose Material 3 Adaptive library has been updated to support these new breakpoints, enabling developers to opt in by declaring them in their Gradle build files.
Navigation 3 and the Scenes system
Navigation 3 has made its debut as part of the Jetpack collection, achieving its first stable release alongside this announcement. This navigation library, tailored for Compose, is designed to work seamlessly with adaptive layouts. It introduces a system for managing UI flow based on what is termed as Scenes.
A Scene represents a layout that can display one or more destinations simultaneously. The SceneStrategy determines the feasibility of creating a given Scene, allowing developers to chain multiple strategies to adapt the display based on screen size and device configuration. For example, a ThreePaneSceneStrategy could show three panes side by side on wider screens, while reverting to a TwoPaneStrategy or a single-pane view as space diminishes.
Design principles for the desktop context
A separate announcement by Ivy Knight, Senior Design Advocate at Android, highlighted significant updates to Android’s design resources, including new Desktop Experience guidance and a revamped Android Design Gallery. Knight articulates that a desktop experience encompasses scenarios where an app operates in a desktop-like mode, typically involving non-touch input devices or external displays.
The guidance outlines six foundational design principles for this context:
- Designing for desktop should be integral, not an afterthought.
- Utilize increased screen space meaningfully, avoiding mere scaling of elements.
- Motion transitions should be adapted for desktop interactions.
- Support multitasking within apps, not just through the OS’s multi-window capabilities.
- Balance efficiency with information density to avoid overwhelming users.
- Recognize the importance of touch, pointer, and keyboard inputs in a desktop environment.
The documentation also emphasizes multitasking specifics, noting that desktop users often keep multiple windows of the same app open, with Android facilitating easy switching between instances using keyboard shortcuts.
The Android Design Gallery
In conjunction with the design principles, Knight introduced the Android Design Gallery, a dynamic catalog showcasing inspirational examples across various verticals, form factors, and UX patterns. This gallery encompasses categories such as creativity, games, media, productivity, reading, shopping, and social interactions, allowing for filtering by form factor, UX pattern, input type, and screen size class.
It includes design examples for workflows like multitasking while reading, social media editing, and drag-and-drop interactions, catering to diverse input types and spanning from mobile to desktop environments.
Adaptive layout design guidance
The Android developer documentation on adaptive layouts, recently updated, stresses that adaptive design should be the foundational approach rather than an afterthought. The documentation acknowledges the diversity of the Android mobile market, which includes handsets, foldables, tablets, and more, advocating for designs that enhance ergonomics, usability, and overall app quality.
Specific guidelines are provided, advising developers to set maximum widths on content to prevent excessive stretching and to think in terms of containment or panes for easier design across various device types.
Why this matters for the marketing and advertising community
The announcement regarding connected display support carries significant implications for mobile advertising and app measurement, complicating the distinction between mobile and desktop ad inventory. An app operating in a freeform window on an external monitor presents a different context compared to its mobile screen counterpart, despite originating from the same device.
As Android evolves into desktop-like environments, advertisers must reconsider targeting parameters, viewability measurement, and creative formats. Ads designed for mobile screens may not translate effectively in resizable windows on larger displays, prompting app developers to ensure their ad implementations can adapt to changes in density and window configurations.
The requirement for apps to dynamically manage Display object changes is particularly relevant for ad SDKs that rely on cached display metrics for determining ad dimensions. Failure to adapt could lead to incorrect creative sizes or layout issues during connected display sessions, impacting ad performance and measurement accuracy.
Timeline
- February 2, 2026 – Update to Android developer documentation on adaptive layouts, emphasizing adaptive design as a default approach.
- March 3, 2026 – Announcement of connected display general availability with Android 16 QPR3, detailing supported devices and new features.
- March 3, 2026 – Release of updated desktop experience design documentation outlining foundational principles.
- March 16, 2026 – Launch of the Android Design Gallery, showcasing design resources and interaction patterns.
Related PPC Land coverage
Summary
Who: Google and Samsung, with contributions from developer relations engineers Francesco Romano and design advocate Ivy Knight.
What: General availability of connected display support with Android 16 QPR3, enabling desktop-like environments on supported devices.
When: Announced on March 3, 2026, with design guidance following on March 16, 2026.
Where: Available on supported hardware running Android 16 and connected to external displays.
Why: Google is positioning Android as a comprehensive desktop computing platform, necessitating updates from developers to accommodate new windowing behaviors and input types.
