Free and Open Source Alternative to Airdrop

Original Article ↗ Hacker News Discussion ↗

Open-source web tools like Sharedrop, Snapdrop, and LocalSend aim to replicate Apple’s AirDrop by enabling quick, local file sharing across devices without relying on centralized cloud services. Commenters weigh trade-offs between browser-based solutions and dedicated apps, touching on issues such as WebRTC support, Wi‑Fi Direct vs. Bluetooth, ad-hoc high-speed connections, and ease of use for non-technical users. Many highlight that while these alternatives work well on LANs or via hotspots, none yet fully match AirDrop’s seamless, cross-device experience—especially between iOS and Android.

Scope of Sharedrop / Browser Issues

  • Sharedrop is presented as a free, open-source, browser-based AirDrop alternative.
  • Some users hit a “browser not supported” error on latest Firefox; enabling WebRTC fixes it.
  • UX viewed as “good enough but not as smooth” as native AirDrop; some local-network features don’t work reliably for all.

“Free” vs Free Software

  • Debate over “free” meaning price vs “free software” (libre).
  • Some insist “being free” primarily means zero cost for most users.
  • Others stress that free/open-source software can still be paid for, and that “free” in FOSS is about user freedoms, not price.

How AirDrop Actually Works (and Why People Care)

  • Many tools marketed as “AirDrop alternatives” don’t replicate AirDrop’s core behavior:
    • Ad-hoc high-speed Wi‑Fi connection (Wi‑Fi Direct / AWDL-like), often discovered via Bluetooth/Bonjour-like mechanisms.
    • Works without existing Wi‑Fi, maintains normal network connectivity via frequency hopping.
    • No practical file-size limits; used for very large media (RAW photos, multi‑GB or even hundreds of GB video).
  • Strong emphasis that this is faster, more power-efficient, and more convenient than Bluetooth or cloud uploads.
  • Use cases: rapid sharing of photos among friends, transferring media from phone to editing workstation, offline emergency scenarios (e.g., wildfire mapping), device migration when cloud is undesirable.

Alternatives and Their Trade-offs

  • Mentioned tools: snapdrop, PairDrop, LocalSend, NitroShare, Flying Carpet, KDE Connect, Syncthing/Möbius Sync, Taildrop (Tailscale), relaysecret, HTTP/QR-based sharing apps.
  • LocalSend, KDE Connect, Syncthing praised for reliability and speed but require app installation and some setup.
  • Snapdrop/Sharedrop/PairDrop are easier (web-based) but typically:
    • Rely on existing LAN or hotspots, don’t autonomously form ad-hoc Wi‑Fi.
    • Can fail on public/corporate networks with client isolation.
  • Taildrop is secure and P2P over WireGuard but only supports transfers between a single user’s own devices.

UX, Security, and Simplicity

  • Strong agreement that mainstream users want “share → tap person,” not running HTTP servers or managing hotspots/QR codes.
  • Some argue simple HTTP+hotspot flows are “no effort”; others counter with:
    • Confusing steps for non-technical users.
    • Security risks of joining arbitrary Wi‑Fi networks / scanning unknown QR codes.
  • Several posters ask why AirDrop is needed if “everything is in the cloud”; replies highlight:
    • Bandwidth, speed, and cost advantages.
    • Keeping data off third-party servers.
    • Situations with poor or no internet access.