User privacy and transparency are core to the Android experience. To better align with these principles, we are updating the default behavior of the Nearby Connections API regarding how it interacts with device radios.
What is changing?
Previously, the Nearby Connections API could automatically toggle Wi-Fi and Bluetooth radios ON to facilitate connections without explicit user intervention. Moving forward, the API will no longer automatically enable these radios for 1P and 3P applications.
What this means for developers
If your app relies on Nearby Connections, you will need to update your implementation to account for these changes:
- Manual Radio Management: You must ensure that the necessary radios (Wi-Fi or Bluetooth) are enabled before initiating Nearby Connections tasks.
- User Notification: If the required radios are disabled, your app must now inform the user and request that they enable them manually. The API will no longer programmatically turn them on for you.
Timing
These changes are scheduled to take effect in late 2026. We recommend reviewing your connection workflows now to ensure a seamless transition for your users.
-
CommunityWe released the official Android Skills in April. This blog post covers the feedback we received and explains the philosophy and methodology behind the project.
Jose Alcérreca • 4 min read -
Product NewsProviding a safe online experience and protecting users from harm is a top priority at Google Play.
Paul Feng • 2 min read -
Product NewsToday, we officially celebrate five years since the release of Jetpack Compose 1.0. From version 1.0, announced on July 28th, 2021, to our latest 1.11 release, we’ve seen the APIs evolve significantly over the years, and we’re taking a moment to celebrate.
Rebecca Franks, Nick Butcher, Loryn Hairston • 4 min read
Get the latest Android development insights delivered to your inbox weekly.
