<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Akshay Kumar Dadheech</title>
    <description>The latest articles on DEV Community by Akshay Kumar Dadheech (@akshay_kumardadheech_14f).</description>
    <link>https://dev.to/akshay_kumardadheech_14f</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3965387%2Fc4c70924-3ad0-42f9-9bd7-3483a26ea608.png</url>
      <title>DEV Community: Akshay Kumar Dadheech</title>
      <link>https://dev.to/akshay_kumardadheech_14f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/akshay_kumardadheech_14f"/>
    <language>en</language>
    <item>
      <title>I built an open-source AirDrop alternative that works in any browser — no app, no account, no cloud</title>
      <dc:creator>Akshay Kumar Dadheech</dc:creator>
      <pubDate>Tue, 02 Jun 2026 21:33:56 +0000</pubDate>
      <link>https://dev.to/akshay_kumardadheech_14f/i-built-an-open-source-airdrop-alternative-that-works-in-any-browser-no-app-no-account-no-cloud-1af4</link>
      <guid>https://dev.to/akshay_kumardadheech_14f/i-built-an-open-source-airdrop-alternative-that-works-in-any-browser-no-app-no-account-no-cloud-1af4</guid>
      <description>&lt;p&gt;AirDrop only works between Apple devices. Most alternatives require an app install, a cloud account, or route files through a third-party server.&lt;/p&gt;

&lt;p&gt;I wanted something simpler:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Open a URL → discover nearby devices → send files.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;So I built &lt;strong&gt;LocalDrop&lt;/strong&gt; — a peer-to-peer file transfer app that works entirely in the browser over local Wi-Fi.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/akshaykdadheech/localdrop" rel="noopener noreferrer"&gt;https://github.com/akshaykdadheech/localdrop&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Live Demo:&lt;/strong&gt; &lt;a href="https://localdrop-4fddd39fb6ad.herokuapp.com" rel="noopener noreferrer"&gt;https://localdrop-4fddd39fb6ad.herokuapp.com&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  How It Works
&lt;/h2&gt;

&lt;p&gt;Devices connected to the same Wi-Fi network automatically discover each other through a lightweight signaling server.&lt;/p&gt;

&lt;p&gt;Once discovered, WebRTC establishes a direct peer-to-peer connection:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Browser A ──► Signaling Server ◄── Browser B
      └──────── WebRTC P2P ────────┘
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The signaling server only helps devices find each other. File transfers happen directly between browsers via WebRTC and are DTLS encrypted, so the server never sees your files.&lt;/p&gt;

&lt;h2&gt;
  
  
  Interesting Challenges
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Backpressure Handling
&lt;/h3&gt;

&lt;p&gt;WebRTC DataChannels on Chromium have a ~16 MB buffer limit. Sending data too aggressively can crash the tab.&lt;/p&gt;

&lt;p&gt;I solved this using:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;bufferedAmountLowThreshold&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Flow control based on drain events&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Cross-Platform Compatibility
&lt;/h3&gt;

&lt;p&gt;Different browsers expose different capabilities.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Android Chrome supports the File System Access API&lt;/li&gt;
&lt;li&gt;iOS Safari does not&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This required separate file-receiving flows for each platform.&lt;/p&gt;

&lt;h3&gt;
  
  
  Large File Transfers
&lt;/h3&gt;

&lt;p&gt;Keeping multi-gigabyte files in memory isn't practical.&lt;/p&gt;

&lt;p&gt;On Chrome, &lt;code&gt;showSaveFilePicker()&lt;/code&gt; is triggered after the transfer completes, allowing transfer progress to remain visible throughout the process without buffering everything in RAM.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tech Stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Svelte 5 + Vite&lt;/li&gt;
&lt;li&gt;TypeScript&lt;/li&gt;
&lt;li&gt;WebRTC DataChannel&lt;/li&gt;
&lt;li&gt;Node.js + ws&lt;/li&gt;
&lt;li&gt;Docker&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Self-Hosting
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/akshaykdadheech/localdrop
&lt;span class="nb"&gt;cd &lt;/span&gt;localdrop
docker compose up &lt;span class="nt"&gt;-d&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then open:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;http://your-ip:3001
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;from any device connected to the same Wi-Fi network.&lt;/p&gt;

&lt;p&gt;I'd love feedback from anyone who's worked with WebRTC DataChannels, especially on mobile browsers. If you find the project useful, a ⭐ on GitHub would be greatly appreciated.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>opensource</category>
      <category>showdev</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
