Upcoming Changes to the Nearby Connections API
Starting in the final months of 2026, the Android platform—under the direction of Engineering Manager Wei Wang—will alter the default operation of its Nearby Connections API. The service, which developers have relied on to spin up peer‑to‑peer links without user interaction, will no longer flip Wi‑Fi or Bluetooth radios on its own for either Google‑owned (1P) or external (3P) apps. Instead, apps must check the radio state, prompt the user, and wait for a manual enable before any discovery or payload transfer can proceed. This shift directly reflects Android’s renewed emphasis on user privacy and transparency, removing a background behavior that previously concealed network activity from the end‑user.
The move aligns Android with a broader industry push toward explicit consent for radio usage. Apple’s iOS already requires apps to request Bluetooth permission and to surface a system dialog before turning on the radio, a model that has become a de‑facto standard for privacy‑conscious platforms. Google’s decision also preempts upcoming regulatory scrutiny in Europe and the U.S., where lawmakers are probing “silent” activation of connectivity hardware. For developers, the change means revisiting code paths in games that use Nearby Connections for local multiplayer, file‑sharing utilities, and IoT onboarding tools, all of which previously assumed the API would handle radio power automatically.
The practical impact will surface in user experience and adoption metrics. Apps that fail to provide clear, timely prompts may see higher drop‑off rates during connection attempts, especially on devices where Wi‑Fi or Bluetooth is disabled by default to conserve battery. Conversely, developers who implement smooth onboarding flows—perhaps bundling a single “Enable radios” button with contextual explanations—could mitigate friction and even gain trust. Watch for Android’s rollout schedule across API levels; early beta releases may expose edge cases where the API still toggles radios under specific conditions, and third‑party libraries that abstract Nearby Connections will need updates to propagate the new requirement.
Key Takeaways
Developers must add logic to detect and request Wi‑Fi or Bluetooth activation before using Nearby Connections after late 2026.
The policy change is a direct response to Android’s privacy roadmap, mirroring consent‑first trends seen on competing platforms.
Apps that previously relied on silent radio activation risk user churn unless they redesign their permission dialogs.
Monitoring Android’s staged rollout and updating any third‑party SDKs that wrap Nearby Connections will be essential to avoid runtime failures.
About the Source
This analysis is based on reporting by Android Developers. Here is a short excerpt for context:
Posted by Wei Wang, Engineering Manager, Android BeTo 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.Read the original at Android Developers
