3
7 Comments

Building a privacy-first way to transfer text, code, and files between devices

Hey Indie Hackers,

I’ve been working on Textunnel, a small tool built around a simple idea:

Moving something from one device to another should be instant and frictionless.

I often found myself needing to send code snippets, notes, links, or small files between my laptop and phone. The existing solutions usually involved cloud storage, accounts, or extra steps that felt unnecessary for quick transfers.

So I started exploring whether WebRTC could provide a simpler approach.

Textunnel uses peer-to-peer technology to connect devices directly and transfer content without relying on traditional file upload workflows.

Some things I focused on:

  • No account required

  • Browser-to-browser transfers

  • Text, code, and file sharing

  • No permanent file storage

  • Simple cross-device workflow

The most interesting part of building this was not creating the connection itself, but making the experience reliable across different networks and devices.

Some challenges I worked through:

  • WebRTC signaling

  • NAT traversal and ICE candidates

  • Handling connection failures

  • Making file transfers feel smooth

  • Designing a simple user experience

I’m continuing to improve it and learn from how people use it.

Would love to connect with other indie hackers building productivity tools, privacy-focused apps, or projects using peer-to-peer technology.

https://textunnel.com/

posted toAvatar for product Textunnel
Textunnel
  1. 1

    How do you currently handle your analytics and would you mind reading my indiehacker pots on how crawlers and bots are ruining analytics data?
    https://www.indiehackers.com/post/i-just-discovered-my-analytics-numbers-are-mostly-fake-here-is-why-8197e3ff9d

  2. 1

    What stood out to me is that for quick cross-device transfers, the real competitor may not be another file-sharing tool — it's the workaround people already use without thinking about it.

    That makes reducing the number of decisions before something reaches the other device especially important.

    1. 1
      “Couldn’t agree more. The friction of opening an app or typing a code is usually what pushes people back to their messy workarounds (like self-chatting). That’s why we focused on 1-click LAN discovery and direct clipboard handoff. If it takes more than 5 seconds, people will just default to email. Appreciate the thoughtful feedback!”
      1. 1
        That makes sense. Happy to continue the conversation privately — what’s the best email to reach you on?
  3. 1

    The fact you chose browser to browser with no account and no permanent storage is what makes this feel different. It solves the quick transfer problem without asking people to change how they work.

    Reading this I kept thinking it feels like it could be getting a lot more organic traffic than it probably is right now. At $1K MRR that would probably give you a much clearer picture of what people actually keep using.

    Have you had that feeling yourself yet?

    1. 1
      “That feeling hits us every single day! You nailed why we're so bullish on the organic traffic potential. Millions of people search daily for 'AirDrop for Windows', 'no login file sharing', and 'cross-device clipboard', but they get pushed toward bloated apps, cloud storage paywalls, or messy self-emails. Because Textunnel is built on a 100% client-side serverless P2P architecture, our infrastructure cost is virtually zero — which lets us keep the core tool friction-free while we scale up organic SEO and AI visibility. To make browser-to-browser feel truly reliable (rather than just a novelty), we had to engineer a few hardcore 'under-the-hood' capabilities that classic WebRTC tools lacked: 50GB+ Zero-OOM Streaming Engine: Legacy browser tools buffer whole files into RAM as Blobs, causing instant tab crashes on anything over 2GB. We built chunk backpressure flow control (RTCDataChannel.bufferedAmount), keeping memory usage strictly under 40MB even while streaming a 50GB 4K video library. Screen Wake Lock Integration: Uses HTML5 Wake Lock to prevent iPhones and laptops from going to sleep midway through multi-gigabyte transfers. Camera Snap ➔ Direct PC Clipboard: You snap a whiteboard sketch or doc on your phone, and it streams straight to your computer's system clipboard — ready for instant Ctrl+V into Figma or Word without saving files. Smart LAN Radar: Zero code typing when on the same Wi-Fi — devices auto-discover each other like native AirDrop and stay persistently paired. Once we reach that critical traffic threshold, we plan to layer on Pro power-features (like encrypted team relays, custom STUN/TURN clusters, and persistent clipboard history vaults). Would love to hear your thoughts — if you were to see a Pro tier, what's one capability you'd gladly pay for?”
  4. 1

    A little background:

    I originally built this because I wanted a faster way to move small pieces of information between my own devices.

    The goal is not to replace cloud storage, but to make those quick "I need this on another device right now" moments easier.