Google has released the second beta of Android 17 which introduces a suite of new APIs focused on privacy, connectivity, and improved user interface controls. The update introduces system-level tools such as EyeDropper API and a secure Contacts Picker to limit broad data access.
The search giant also said that the platform is quickly moving towards its Platform Stability milestone, which is set to be reached in March. This will see Google provide the final SDK and NDK APIs, allowing developers to finalize their apps for a stable release in June 2026.
For a long time now, Android has supported chat buttons that give you fast access to conversations across apps. With this latest beta, bubbles are now available for any application just by long-pressing the launcher icon. On tablets and foldable devices, a new bubble bar within the taskbar will allow for easier organization and movement between anchored points on the screen.
Also in this update, Google has improved pointer capture compatibility to treat touchpad movements and scrolling gestures as mouse events by default. This will significantly improve the experience for first-person games. The search giant notes that developers can still opt for absolute mode if they require raw finger-location data rather than relative movement.
Google has also improved security for One-Time Passwords (OTPs) by implementing a mandatory three-hour delay on SMS access for apps that aren’t the intended recipient or the default SMS handler. This will help to stop OTP hijacking by ensuring only verified domains can programmatically read verification codes right after codes have been delivered.
Another security improvement is the introduction of the ACCESS_LOCAL_NETWORK permission which stops apps from scanning local area networks without user consent. This helps to prevent covert tracking and fingerprinting risks. Going forward, apps should now use system-mediated device pickers or request explicit runtime permissions to keep communicating with smart home and casting hardware.
Google says that developers should start compiling their apps against SDK 37 now to test for app-breaking changes. Following the March stability milestone, developers will be able to push their updated apps to the Google Play Store, ahead of the general availability launch. For end users enrolled in the Android Beta program, Beta 2 will be rolled out over-the-air automatically.
If you are in the Beta program and want to go back to Android 16 QPR3 without a data wipe, you must do this before installing this update as the next change for a seamless exit from the Beta program won’t happen until June 2026 next time.