Top Hidden Features Discovered in the Latest Android Beta Release

The most useful Android changes are sometimes the ones you miss while looking for a redesigned home screen. A floating app, a selective contact chooser, or a separate assistant volume can change a daily task more than another animation.

As of November 5, 2026, the latest release verified for this article is Android 17 QPR3 Beta 3, released October 29. The features below are documented platform capabilities worth exploring on that branch; they were not all introduced in Beta 3. I have separated those capabilities from this build’s fixes, because calling every repaired behavior a newly discovered feature would be misleading.

Android 17 QPR3 Beta 3: build details and feature availability

“Latest Android beta” needs a date and a branch. A quarterly beta, the original major-version beta, and a manufacturer’s separate preview program are not interchangeable. Open Settings > About phone > Android version and inspect the build information before comparing your screen with someone else’s.

Android beta feature availability depends on hardware, launcher support, the application involved, and staged delivery. A developer API can exist before all your favorite apps expose it. A feature shown on a tablet may also have a different presentation on a phone.

For broader preparation, the beta testing basics explain the background. The useful focus here is the actual feature: where you encounter it, what enables it, and what problem it can solve.

App Bubbles and Bubble Bar: floating multitasking across phones and tablets

1. App Bubbles turn an application into a floating workspace

Android 17 App Bubbles extend the floating-window idea beyond messaging conversations. On a supported launcher, long-press an app icon and choose its bubble action. The application can then appear in a compact floating window above another task.

That is useful when you need a small reference while completing something else: a checklist beside a booking form, notes beside a map, or a calculator beside a document. I would start with a simple app whose layout is easy to read at a smaller size.

Where to find it: the launcher’s app-icon menu on supported software. How to enable it: choose the bubble option when present. What it does: keeps the app available without repeatedly switching full-screen tasks. If the menu does not contain the action, check the launcher and device support rather than assuming an undocumented flag is required.

App Bubbles are different from message notification bubbles

A chat notification bubble represents a conversation exposed through an app’s notification integration. An app bubble is a broader windowing capability. Turning off one messaging app’s notification bubbles is not a reliable test of whether the launcher supports floating an ordinary application.

For Android floating windows on small screens, readability is the first trade-off. A form that already feels crowded full-screen may be awkward in a compact window. Expand the app for a detailed action, then return it to a small reference role when that is more comfortable.

2. Bubble Bar organizes floating apps on larger displays

On supported tablets and foldables, the Bubble Bar provides a taskbar area for managing app bubbles. It gives the floating-workspace model a more organized home when the display has room for several tasks.

Where to find it: the taskbar on a supported large-screen setup after creating app bubbles. How to use it: select a bubble to return to that task and use the supported window controls to adjust its presentation. What it does: reduces the need to hunt for overlapping floating elements.

For foldable multitasking with a Bubble Bar, compare the outer and inner display experience. A layout that works well unfolded may be unsuitable when closed. Preserve your work before switching posture, and judge the feature by whether it keeps the task understandable rather than by how many windows fit at once.

Screen Reactions and EyeDropper: creator tools that hide in workflows

3. Screen Reactions combines your screen with a selfie view

Screen Reactions lets supported Android 17 devices combine screen recording with a front-camera reaction view. It suits a narrated explanation, a walkthrough, or commentary on something displayed on the phone.

Where to look: the system screen-recording flow, usually reached from Quick Settings > Screen record. Open the available toolbar or capture options and look for Screen Reactions when offered. Enabling the camera option in that supported flow adds the reaction view; a plain screen recording without that option is a different capture.

For Android screen recording with a face camera, make a short harmless recording before a longer session. Check where the face view sits, whether it covers a button, and which audio source was selected. Review the resulting clip instead of assuming that a microphone icon means every audio source was captured.

Keep private content outside the recording

Close sensitive apps, inspect notification previews, and use the supported capture scope that suits the task. A reaction overlay adds another image source; it does not automatically hide account details in the main screen. Some protected content may also refuse to appear in a recording.

The useful creator workflow is short and deliberate: prepare the screen, select the supported reaction option, record one action, then inspect the saved video. That avoids discovering an obscured control or the wrong audio source after recording a complete tutorial.

4. EyeDropper lets supporting apps request a screen color

The Android 17 EyeDropper API provides a system color-selection flow. A supporting application can ask you to choose a pixel color without requiring the broad screen-capture permission normally associated with recording the display.

Where to find it: inside an app that has implemented a system screen-color picker, such as a design workflow offering that capability. How to enable it: invoke that app’s color-selection action and complete the system picker. There is no universal EyeDropper switch that adds a button to every existing app.

For picking a color from an Android screen, distinguish the sampled display value from the original file’s underlying color data. Rendering, transparency, and the app’s own processing can affect what you see. Use a sample as a practical design reference, then verify the final color in the document or asset you are creating.

This is a good example of an Android feature hidden behind app integration. Updating the operating system supplies the capability; the app still needs to expose a useful action. A missing menu in one graphics app does not show that the platform API is absent.

Android Contacts Picker and Assistant volume: smaller controls with daily value

5. Contacts Picker shares selected fields instead of the whole address book

The Android Contacts Picker gives supporting apps a system interface for selecting contacts and requested fields. The useful privacy difference is scope: an app can receive the particular contact data you choose instead of asking for broad access to the address book.

Where to find it: a supported app’s choose-contact, invite, or recipient action. How to use it: open that action, select the intended contact or contacts in the system picker, and confirm the fields being shared. What it does: grants the app access to the selected data through that flow.

For selective contact sharing on Android, start with a low-stakes example and inspect what returns to the app. If a feature needs one email address, ask why it is requesting the entire contacts permission instead. That question remains useful even when a legacy app has not adopted the newer picker.

The Android contact chooser is not a tool for deleting previously uploaded address books from a service. Revoking a permission and managing data already held by an app are different tasks. Review the service’s own deletion controls when that is the actual goal.

6. Dedicated Assistant volume separates replies from media

The system provides a dedicated Assistant audio stream so compatible assistant playback can be controlled separately from media. This can help when you want a spoken reply to remain audible without raising a music or video level.

Where to check: the expanded volume panel or relevant sound controls while using a supported assistant. How to use it: adjust the Assistant control if your device and assistant integration expose it. What it does: changes that stream independently rather than treating all playback as media.

Assistant volume separate from media is dependent on correct app integration. If the assistant still plays through the media stream, moving a separate slider may not affect that output. Test with a brief ordinary response and then play media to see whether the two levels behave independently.

Bluetooth assistant volume behavior may also depend on the active assistant audio mode and connected device. Do not infer that a car, speaker, or headset follows the same control path as the phone’s own speaker. The feature is most useful when you verify the route you use daily.

Handoff and interactive Picture-in-Picture across Android workspaces

7. Handoff lets a supporting app continue a task on another device

Android 17 Handoff is a platform capability for developers to offer cross-device task continuation. It is more specific than copying a link: the application needs to define the state that can be continued and participate in the handoff experience.

Where to find it: a supporting app’s continue-on-device or related cross-device interface. How to enable it: follow that app’s device association and continuation flow, using compatible devices. What it does: lets the receiving app resume the supported task state.

For continuing an Android task from phone to tablet, first choose a harmless task you can reproduce. Compare the destination screen with the source: did the app reopen the right document, return to the right stage, or merely launch its home page? That distinction tells you whether the particular workflow is actually supported.

Handoff app support is not universal account synchronization. An app can synchronize files without using this task-continuation feature, and a handoff can have limits around authentication or content rights. Keep those limits visible when deciding whether it improves your routine.

8. Interactive desktop PiP keeps a small window usable

The platform adds interactive Picture-in-Picture in desktop environments, allowing a pinned window to remain interactive. It differs from treating a small video rectangle as a passive playback surface.

Where to look: a supported app in a supported desktop windowing environment. How to use it: enter the application’s available PiP or pinning flow when that environment exposes it. What it does: retains an interactive compact window above the rest of the desktop workspace.

For Android desktop interactive PiP, choose a modest use case such as a small reference tool. Check whether pointer input reaches the intended control and whether the window stays readable. The existence of the platform feature does not mean every phone connected to every monitor exposes the same desktop controls.

I would treat this as a useful workspace option, rather than a reason to expect laptop behavior from every Android app. A good compact window has a clear job and can expand when the task becomes more detailed.

QPR3 Beta 3 fixes that make existing Android features easier to use

Beta 3 fixes include bubbles becoming stuck while being dismissed, activity launches failing with an active PiP window, and missing image-action icons in Recents. Those changes improve existing workflows; they are not three new feature announcements.

For a beta bubble dismissal problem, reopen a simple app as a bubble and check ordinary open, minimize, and dismiss actions. For a PiP launch problem, compare the same app action with and without a small playback window present. These are targeted checks of the named behavior, not a reason to force hidden flags.

Recents image actions also remain content- and device-dependent. Open the overview on a screen that contains a suitable image and inspect the actions actually offered. A fix for missing icons should not be interpreted as a promise that every application exposes every image action.

If an app will not open at all, the beta feature insights provide related context. Keep feature availability separate from a general application crash so you report the problem accurately.

Android beta hidden-feature questions

Are these features exclusive to QPR3 Beta 3?

No. They are documented capabilities relevant to this release branch. Some arrived earlier or require additional application support. The table at the beginning identifies the build context so this list does not present old capabilities as brand-new discoveries.

Should I run shell commands to force a missing feature?

Not merely because a menu is absent. A disabled flag may reflect incomplete support or a device restriction, and a copied command may target a different build. Check the launcher, app version, and supported device behavior before assuming the interface is hiding a usable control.

Can I leave the beta without losing data?

A limited no-wipe exit opportunity can exist after moving to an eligible stable release, but leaving at another point can require a reset. Read the actual update message and backup status before acting. The title of related beta guidance should never replace the conditions shown for your current branch.

Try one Android 17 feature in a real task

Start with App Bubbles if the launcher offers them, or try selective contact sharing in an app that supports the new picker. For a creative task, inspect the screen-recording reaction options. Each gives you a concrete result you can judge without enabling experimental flags.

Keep app integration and device support in the picture. The best discovery is a capability that makes your own task easier, with its limitations understood and its behavior confirmed on the build you actually run.