Android's Nearby Connections 2.0 API, which enables offline, P2P communication between devices over Bluetooth and Wi-Fi, is now available to developers
Some of you might remember the Contextual App Experiences talk at I/O this year. The seemingly convoluted name actually held some pretty big news …
Context & Ripple Effects
Nearby Connections 2.0 completes a two-part play Google started with the Awareness API in 2016: that API gave apps context signals like time, location, activity, and beacons, while this one gives them the transport — direct Bluetooth and Wi-Fi links between devices with no network in between. Together they let an app know where a user is and act on nearby devices without touching a server.
The reason it matters beyond the release notes is what the lineage grew into: the same proximity plumbing resurfaced three years later as Nearby Share, Google's AirDrop-style transfer tool, and then as the Cross Device SDK for phone-to-tablet experiences. This 2017 API is the developer-facing seed of that platform.
First-order effects
- Android developers can now ship offline multiplayer games, local file sharing, and device-to-device collaboration features without building their own discovery and pairing stacks over raw Bluetooth or Wi-Fi.
Second-order effects
- Apps built on the API work in connectivity dead zones — planes, rural areas, crowded venues — shifting some feature competition away from who has backend infrastructure toward who uses the radios already in every handset.
Third-order effects
- If the pattern holds, proximity stops being a per-app hack and becomes a platform layer: Google's own later products — Nearby Share on Android, Nearby Share for Windows, and the Cross Device SDK — all trace back to making device-to-device links a first-class OS capability rather than something each developer reinvents.
The trend: Google is assembling an ambient computing layer out of proximity APIs, moving device-to-device connectivity from individual app implementations into platform-owned primitives.