It’s not the function, it’s the method.How is being able to directly and locally send files to more people a bad thing?
It’s not the function, it’s the method.How is being able to directly and locally send files to more people a bad thing?
yeah tho not on older devices haha... so you will get super spammedIt's only on for 10 mins at a time, maximum.
..when it was it possible to keep it on all the time, I got spammed by other iPhone users several times when at busy airports...LAX, mainly. That time has passed.
yeah tho not on older devices haha... so you will get super spammed
arstechnica.com
It’s not the function, it’s the method.
In other words "I have no good answer." Got it.It’s not the function, it’s the method.
Leveraging open standards does not mean the handshake was not reverse engineered. why was Apple not upfront about this then and publish their “open standards”?It's simply leveraging open standards to accomplish peer-to-peer file transfer between platforms. iOS now uses Wi-Fi Aware for airdrop, and Android already had support for that spec, so this is really just a match made in heaven.
Android devices won't appear or be able to send when either end is set to accept airdrop from contacts only. Google did not reverse-engineer the handshake that exposes contacts in airdrop.
Do you not think that iPhone users are already capable of spamming other iPhone users?When airdrop is activated for everyone... those android users will just spam sending things to Apple users !
You mean like they did when they invented USB, IRDA, Blutooth, WiFi, RS-232, SCSI, PCI, SATA, TCP/IP, Countless Graphics, Sound, and Video formats...On the flip side, you have more open devices like android phones and windows computers, but because they are all manufactured by different vendors and the software is maintained by different companies, there really isn't much incentive for them to come together and improve on the inter-operability of their products.
Not directly from an iPhone using iPhone software and if the target has a modicum of correct settings.Do you not think that iPhone users are already capable of spamming other iPhone users?
That's not how contract law works. Its more likely Google could be in breach of existing contracts with this feature. Apple could use existing contracts to kill this or inject language into future contracts.Google has leverage now that Gemini is gonna be used for Siri.
Not directly from an iPhone using iPhone software and if the target has a modicum of correct settings.
Those last two words are carrying a lot of weight in your comment. Especially given the restrictive setting requirements Google put in place for this to even work.Not directly from an iPhone using iPhone software and if the target has a modicum of correct settings.
What contract do you think Apple has with Google in relation to this feature?That's not how contract law works. Its more likely Google could be in breach of existing contracts with this feature.
Wifi Aware support was introduced in iOS 26, that's correct. This only means, that third-party apps can use the technology to build solutions on top of the API. But I doubt that Apple's current AirDrop implementation is already based on that. The EU mandated that Apple and Google support interoperable file exchange by the end of next year based on Wifi Aware.Read the Arstechnica article linked above. iOS already has Wi-Fi Aware, which is why Google were able to implement this.
I’m not an expert on that, but sounds to me like yet another “open” standard where the individual features in the standard is voluntary, meaning that two products supporting the same standard may not support the same features. Negating the benefits of having an open standard in the first place.
Leveraging open standards does not mean the handshake was not reverse engineered. why was Apple not upfront about this then and publish their “open standards”?
Yes best practices are best practices. Don’t want to do them, no harm no foul.Those last two words are carrying a lot of weight in your comment. Especially given the restrictive setting requirements Google put in place for this to even work.
Yes, at least in the EU. Apple can continue maintaining two codebases as they do now or one codebase for airdrop. We’ll see. But you can see how Apple will be selective with the features the eu countries will receive in the future.By then end of next year, Apple and Google will have to support a version of AirDrop that is based on open standards (Wifi Aware) anyway. The old AirDrop will be a thing of the past, at least in the EU.
I regret to inform you that Steve has unfortunately passed away, and is no longer in a decision making capacity at AppleJobs didn’t tolerate palm hooking into iTunes with webos and pre. Don’t see em being happy about this either.
There are many non-Apple devices with AirPlayyou can always use LocalSend I guess.
Apple will not let any one break their walled-garden barrier. There is a reason imessages only work with Apple, and Airplay only works on Apple products, and Pages only open on Apple software.
I'm a bit of a platform tart - on desktop I've bounced between Windows and Macs for decades, and tbh limitations like this one have me leaning back toweards Windows on my next rotation. I require an iPad for a lecturing side gig I do.This feature won’t work for the Mac.
May I ask what motivated you to get a Oneplus instead of iPhone?