XDA Developers finally get a demo of how the Google new file sharing protocol feature will work – and it’s very similar to Apple’s AirDrop.
The feature is (un)officially called “Nearby Sharing” and works with the same components as AirDrop: It requires Bluetooth and Location to handshake with the devices and Wi-Fi to complete the data transfer.
Like AirDrop, you can decide whether you want anyone to be able to send you files or only your contacts. Once installed, it also enables a new Quick Settings tile that lets you toggle your visibility on and off to receive files. Here are three different settings for sharing files and their descriptions:
- Data: Data may be uysed for small files (chargers may apply)
- Wi-Fi only: Never use data to share
- Without Internet: Files will always be shared offline
It seems that the feature may use data to send smaller files over a (hopefully secure) data connection. ‘Wi-Fi only’ seems like the most logical way to send files to someone standing right next to you. The “Without internet” option raises questions – will Bluetooth be used to transmit files or is there some other wired kind of protocol that we don’t know about yet?
Once you have a file or files selected, a “Share Nearby” icon appears in the sharing menu, where you’ll see devices nearby. If you’ve ever used AirDrop or Huawei Share, it works the exact same way. Both devices should have the “Nearby Sharing” feature enabled, and the recipient must accept the file’s receipt.
The video shows the feature working between a Google Pixel 2 XL and Google Pixel 4. It was, however, proven to work between a Pixel 2 XL and a OnePlus 7T Pro, so we are expecting Nearby Share to work across all Android devices.
I was personally disappointed to see Android Beam gone, but Nearby Share is what Google should have launched its Files App with in the first place. Though you can share files over Wi-Fi with the Google Files app, the process is much more involved.
We don’t know when the feature will arrive to Android, but it hasn’t yet been announced by Google. We hope it arrives at Google I/O or before.