Sending recordsdata by way of Fast Share might get a bit inconvenient, nevertheless it may be for a superb purpose

One of many best methods to ship recordsdata throughout Android is Fast Share, and Google has been working to enhance cross-platform transfers by including help for Apple’s AirDrop, which was not too long ago expanded to the Galaxy S26 telephones. In mild of its growth, Google can be engaged on some preventive measures to make sure you don’t ship recordsdata to the wrong particular person, and it seems prefer it may include a little bit of an inconvenience.

With an upcoming change, Google might add an additional step to sending recordsdata utilizing Fast Share. At present, whenever you ship a file to a different Android machine with a unique Google ID logged in, the recipient is requested to “Settle for” or “Reject” the incoming recordsdata. As you’ll anticipate, that is designed to forestall unknown of us from sending you recordsdata, which might very properly be malware, to your units with out your data or consent.

Now, Google is including an additional step, the place the recipient must settle for the switch after which anticipate the sender to provoke the switch. In contrast to the present technique, the place the file switch begins the second a recipient accepts it, the brand new technique requires an additional step from the sender.

After they first ship a file to a different machine, the recipient will simply see the file request. When the recipient accepts it, the sender might be required to faucet their machine title once more to provoke a switch. The file switch might be initiated as soon as the sender faucets the machine.

To sum it up, that is what the switch might appear like:

• Step 1: Sender faucets the recipient’s title within the checklist to ship the file
• Step 2: Recipient accepts the switch
• Step 3: Sender faucets their title once more to provoke the switch.

Whereas the precise purpose for including this additional step stays unclear, we speculate it could be to offer the sender one other probability to verify they’re sending recordsdata to the appropriate particular person, although we are able to think about it may very well be a bit inconvenient if the opposite particular person isn’t proper subsequent to them. In the meantime, if each units are linked to the identical Google account, the consumer is not going to be required to faucet the sender’s title twice earlier than sending.

This function is presently being examined with model 26.12.30 beta of Google Play Companies. As with different APK teardowns, there’s a chance that the function may very well not be applied.

Apparently, Google has additionally been engaged on safeguards that forestall anybody from taking your telephone and transferring recordsdata to their units with out your data. At present, there aren’t any measures to forestall that, however senders could quickly be required to confirm themselves with biometrics or a passcode earlier than sending recordsdata by way of Fast Share, offered Android’s Superior Safety options are enabled. This function has but to be launched, though we have now been seeing hints since October final yr.