Google's Android 17 Beta 3 has landed with a feature that fundamentally changes how Android handles multitasking. After teasing the "Bubbles" windowing framework in Beta 2 without making it functional, Google has now delivered a working implementation that lets users run apps in floating windows—transforming smartphones into something closer to desktop computing environments.
The update is available for Pixel 6 and newer devices and marks the platform stability milestone, meaning the SDK and NDK APIs are finalized. Developers can now confidently build and release Android 17-compatible apps on the Play Store without worrying about breaking API changes.
Floating Windows Arrive, But the Execution Feels Familiar
The Bubbles feature allows nearly any app to run in a floating window that hovers above other content. Activating it requires a long-press on an app icon from either the launcher or taskbar, then selecting the bubble option. On tablets and foldables, users can drag icons from the taskbar to a bottom corner to achieve the same effect.
For larger screens, Google has introduced a bubble bar UI where windows pin to the taskbar rather than float freely. Users can organize these bubbles and snap them to predefined positions, creating a more structured multitasking environment.
The implementation is solid and addresses real use cases—replying to messages while watching video, referencing information while writing, or monitoring multiple apps simultaneously. The detailed audio controls demonstrate thoughtful design, allowing users to manage sound from different apps independently.
Yet this functionality isn't breaking new ground. Samsung's DeX has offered similar desktop-style multitasking for years, and third-party launchers have provided floating window capabilities long before Google made it a native feature. The frustration isn't with the feature itself—it's with the execution. Google announced Bubbles in Beta 2, left it non-functional for an entire release cycle, then quietly activated it in Beta 3 as if the delay never happened. For a company of Google's resources, this feels like poor project management rather than technical limitation.
Interface Refinements That Should Have Come Sooner
Beta 3 includes several interface changes that improve daily usability, though many feel overdue. The combined "Internet" Quick Settings tile has been split into separate Wi-Fi and mobile data controls. Tapping the icon toggles the radio on or off, while tapping the label opens the full settings panel. This reduces the number of taps needed for basic connectivity changes—a welcome simplification that raises the question of why it took this long to implement.
Screen recording gets a redesigned toolbar that floats above other content, providing recording controls and capture options without interrupting workflow. After stopping a recording, users can immediately view, edit, delete, or share the video from the same interface.
Home screen customization expands with the ability to hide app labels entirely. The option lives under Wallpaper & style > Home screen > Icons > Names, where disabling "Show app names" creates a cleaner visual aesthetic. Folders and the app drawer retain their labels—this only affects the home screen itself.
Widgets now render correctly on external displays, automatically adjusting padding, text size, and layout based on display density. Anyone who has connected their phone to a monitor and watched widgets appear at absurd sizes will appreciate this fix.
Desktop Mode and Accessibility Improvements
Interactive Picture-in-Picture arrives for Desktop mode, allowing apps to maintain functional controls while floating above other windows. Video conferencing apps can keep call controls accessible while users work in other applications—a practical enhancement for anyone using Android devices as productivity tools.
Accessibility features receive meaningful updates. Users with hearing aids can now route system sounds independently—notifications, ringtones, and alarms can each be directed to either the hearing aid or the device speaker. This granular control addresses a real accessibility gap that affects daily usability for hearing aid users.
A new Assistant volume slider operates independently from media volume, preventing the common frustration of adjusting one when you meant to change the other.
Privacy Controls Get More Nuanced
The expanded dark theme now supports per-app exceptions, addressing a problem introduced in Android 16 QPR2. That update forced dark mode on apps that didn't natively support it, sometimes causing display issues or breaking visual hierarchies. Beta 3 lets users disable dark theme for specific apps while keeping the system-wide setting active.
Password visibility behavior now adapts to input method. Physical keyboards hide characters immediately for better privacy, while touchscreen input briefly displays characters to compensate for the lack of tactile feedback. This context-aware approach balances security with usability.
A new Location Button API lets apps request precise location for a single session without triggering system dialogs or requesting permanent permissions. Users tap the button, the app gets location data for that interaction, and no persistent permission is granted. This reduces permission fatigue while giving users clear control over location sharing.
Beta 3 also adds notifications for clock changes during daylight saving time transitions—a small touch that prevents the confusion of discovering your device's time has shifted without warning.
What This Means for Android's Direction
Android 17 Beta 3 represents Google's most serious attempt yet to make Android competitive in productivity scenarios. The floating windows, desktop mode enhancements, and refined multitasking controls suggest Google is targeting users who want their phones to function as legitimate work devices, not just consumption tools.
The platform stability milestone means the Android 17 ecosystem can now mature. Developers have stable APIs to target, and the features introduced in Beta 3 will likely see refinement and expansion as third-party apps adopt the new capabilities.
For users considering the beta, the multitasking improvements are substantial enough to justify installation on secondary devices. The feature set is complete enough for daily use, though as with any beta software, stability issues may surface. Anyone relying on their device for critical work should wait for the stable release, expected in the coming months based on Google's typical release cadence.
The question now is whether Google will maintain momentum or let these features stagnate. Android has a history of introducing promising capabilities that never reach their full potential. Bubbles and desktop mode need ongoing refinement and developer adoption to become truly useful rather than novelties that users try once and forget.
