Comment by jjtech
12 hours ago
I'm pretty sure this is just incorrect. According to the linked report[1], they tested it for compatibility with OpenDrop, so I think they simply implemented AWDL.
That might also explain the limited Pixel 10 rollout, if it required a specific WiFi chipset/firmware.
[1] https://www.netspi.com/wp-content/uploads/2025/11/google-fea...
In the last link provided by parent you can read:
> Close-range wireless file transfers: this feature allows to access the same iOS-controlled features as Apple’s services in third-party file sharing apps, creating, for example, alternatives to AirDrop.
As you can read here (https://www.ditto.com/blog/cross-platform-p2p-wi-fi-how-the-...):
> Under pressure from the EU’s Digital Markets Act (DMA), Apple is being forced to ditch its proprietary peer-to-peer Wi-Fi protocol – Apple Wireless Direct Link (AWDL) – in favor of the industry-standard Wi-Fi Aware, also known as Neighbor Awareness Networking (NAN). A quietly published EU interoperability roadmap mandates Apple support Wi-Fi Aware 4.0 in iOS 19 and v5.0,1 thereafter, essentially forcing AWDL into retirement. This post investigates how we got here (from Wi-Fi Direct to AWDL to Wi-Fi Aware), what makes Wi-Fi Aware technically superior, and why this shift unlocks true cross-platform peer-to-peer connectivity for developers.
That's what was confusing to me. It's one thing for Apple to add wifi aware by force, it would be another for them to completely reimplement Airdrop with it. I don't think they were required to do that.
They were required to drop AWDL, yes. They had to reimplement AirDrop.
https://www.ditto.com/blog/cross-platform-p2p-wi-fi-how-the-...