Why AirDrop stops at the Apple fence — and browsers don't
Watch two iPhone owners trade holiday photos and you'll see the best file-sharing experience ever built: hold the phones near each other, tap, done. Now put an Android phone in one of those hands. The magic doesn't degrade — it vanishes. AirDrop won't even list the other device as existing. The Android side, running Quick Share, is equally blind in the other direction. Two flagship computers, thirty centimeters apart, on the same wifi, made by companies with hundreds of billions in the bank — and the officially supported way to move a photo between them is to bounce it off a data center.
The fence is a business decision wearing an engineering coat
Technically, nothing prevents AirDrop-style transfers across vendors. The radios are the same, the wifi standards are the same, and the cryptography is commodity. What differs is who controls the two endpoints. AirDrop uses Apple's private discovery protocol over AWDL; Quick Share uses Google's own dialect. Each is implemented in the operating system, by the vendor, for the vendor's devices — and keeping your photo library flowing smoothly only among devices of one brand is, frankly, worth real money to that brand. The fence isn't an accident of engineering; it's the product working as intended.
Every few years an alliance promises to bridge it, and the bridge always lands as "coming to select models" and stays there. Meanwhile the fence has a second, less discussed cost: even inside one vendor's garden, you're trusting an opaque discovery system that has had its own embarrassing moments — researchers showed AirDrop could leak the hashes of your phone number and email to strangers in the same café, simply because that's how it decides who "everyone" is.
One layer up, the fence never existed
Here's the thing the fence-builders can't fence: both phones ship with a browser, and both browsers implement the same open standards, because the web's entire value depends on them agreeing. WebRTC — the standard behind in-browser video calls — includes a data channel: an encrypted, congestion-controlled pipe between two browsers, defined identically in Chrome, Safari, Firefox and Edge, on iOS, Android, Windows, macOS and Linux. It isn't a port of some vendor's sharing feature. It's neutral ground that has been sitting there, fully paved, for over a decade.
That's the ground this counter is built on. When your iPhone beams a video to an Android tablet here, neither device "supports" the other in any special way. Each just runs a web page; the page arranges a standard connection (by QR label, no server); the bytes cross your router encrypted end-to-end. iPhone to Android. Android to a Linux laptop. A Windows PC to the browser in a smart display, if it has a camera or a paste box. The compatibility matrix is one cell: has a modern browser.
What you give up, honestly
Native tools have real advantages the web can't fully match, and pretending otherwise would be selling. AirDrop can wake the radio and create an ad-hoc link with no shared network at all; a web page needs both devices on the same wifi (or one phone's hotspot — which, tip, works beautifully as the "shared wifi" anywhere). Native tools also integrate into the share sheet, while a beam starts by opening a page on both sides — a ten-second toll the natives don't pay. And iOS insists on a tap before saving each file, where AirDrop drops straight into your photo roll.
There's also a speed myth worth retiring while we're here: people assume the native tools must be faster because they're "closer to the metal". In practice both approaches saturate the same wifi link. A browser data channel moving 20 MB/s through your router isn't leaving meaningful performance on the table versus AirDrop moving the same photos over the same radio — the bottleneck is the air between the antennas, not the software layer. You can check the ceiling yourself with our two-device gauge.
In exchange, you get the property that actually matters the moment your household owns devices from more than one company: it works between all of them, today, with nothing installed and no account signed into. Mixed families, mixed offices, the friend with the "wrong" phone — the fence just isn't there. Bring both devices to the beaming counter and walk them across.