The Infuriating Flaw in Google Nearby Share No One is Talking About

Nov. 5, 2020

After a year of tease,Nearby Sharewas finally unveiled by Google in August, this year. Currently, Nearby Share is available only on Android smartphones running Android 6.0 or above. The company has stated that Nearby Share will be coming to Chromebooks (already in Beta) andChrome browseracross platforms. While that’s exciting news for users who are part of multiple ecosystems, there is an elementary flaw in Nearby Share that is pretty infuriating. And in this article, I am going to address that problem. So without any delay, let’s go ahead and learn about the issue in detail.

Google’s Half-baked Nearby Share Implementation

Without beating around the bush, let me get straight to the point. Nearby Share is a great technology, but it has been marred by some weird issue that holds back its performance. In my experience and testing so far, I have witnessed extremely slow file transfer when bothdevices are connected to a common WiFi network.

No matter what settings you choose for Nearby Share — Data, WiFi only or Without Internet — the transfer speed is lukewarm at best. While being connected to a WiFi network, the transfer speed hoversaround 2 to 2.5MBpswhich is plain disappointing.

For reference, snapdrop.net which offers localized network transfer over a common WiFi point offers speed up to 1.5MBps. On the other hand,Xiaomi’s built-in Mi Shareoffers around 10 -15 MBps of transfer speed. Not to forget, Apple’sAirDrop which goes way above 30MBps. In tandem, Google’s much-touted Nearby Share is embarrassingly slow and nowhere near the competition.

No. Nearby Share is actually not slow and you discover that when you are not connected to a WiFi network. Surprisingly, when both the devices arenot connected to a WiFi access point, you will find that Nearby Share just flies through and transfers the files much quickly.

So it’s clear thatNearby Share is pretty capablebut due to some unknown reasons, the speed remains slow when devices are connected to a WiFi network. So what explains this weird behavior? I think the problem lies in the algorithm that determines the protocol for file sharing.

Google inits blogstates that “Nearby Shareautomaticallychooses the best protocol for fast and easy sharing using Bluetooth, Bluetooth Low Energy, WebRTC or peer-to-peer WiFi”. Here, peer-to-peer WiFi(WiFi Direct) is the fastest way to transfer filesand when you are not connected to an access point, WiFi Direct is used.

However, when you are connected to a WiFi Network, it seems Nearby Share is choosing WebRTC or Bluetooth protocol which results in a much slower transfer. It goes on to show thatNearby Share’s algorithm is not fine-tunedto pick the right protocol and often, it picks the wrong ones to transfer files.

There are times when itcorrectly chooses the WiFi Direct protocolbut the chances are very slim. Frequently, you get slower transfer speed and that makes file sharing through Nearby Share infuriating, to say the least.

As we went through the article, it’s clear that the Nearby Share algorithm is unable to determine the right protocol for file sharing, especially when devices are connected to a WiFi network. We hope that Google fixes the issue and brings faster file sharing — no matter whether the device is connected to an access point or not.

Passionate about Windows, ChromeOS, Android, security and privacy issues. Have a penchant to solve everyday computing problems.