TreeTalk Node - Private file sharing and messaging. Android + Windows.
by•
Local-first file sharing and messaging for Android and Windows. Send files, photos, videos, text and PTT-style voice over Wi-Fi, LAN, hotspot or VPN, with no cloud relay or account required for ordinary local use. No cloud server or internet required.
Replies
We first launched TreeTalk Node on Product Hunt in January. At the time, it was a small Windows-only tool.
Eight months later, the biggest change is sitting in your pocket.
Android is now public on Google Play, and TreeTalk Node can move files, messages and recorded voice directly between Android phones, tablets and Windows PCs on the same reachable Wi-Fi, LAN, phone hotspot or private VPN.
A few things changed with that:
• Select photos or videos in Android Gallery, tap Share, choose TreeTalk Node and send them directly to another phone, tablet or Windows PC.
• Android and Windows devices discover each other automatically on the local network.
• Files, private and group text messages, and PTT-style voice messages use the same communication system.
• Ordinary local communication needs no cloud relay, account or signup, and keeps working when the Internet connection disappears.
The phone-hotspot case became more useful than I originally expected. One phone can create the network even with no Internet connection, and nearby Android and Windows devices can still find each other and communicate.
We also made a deliberate choice with pricing.
Free is not a screen whose main purpose is asking you to upgrade. You can install it on your own devices, test peer discovery, text messaging and ordinary file transfer on your actual network, and decide from there.
Pro is for the heavier workflow: larger files, multi-file sending and regular voice use. It is a one-time purchase rather than another monthly subscription.
The original reason for building TreeTalk Node hasn't changed much: if two devices are already a few metres apart, sending a file between them shouldn't require uploading it to somebody else's server first.
The part I'm most interested in testing now is discovery on messy real networks. Multiple adapters, VPNs, guest Wi-Fi isolation and segmented networks all create interesting edge cases.
If you've built or used local-first software, which network setup would you expect to break peer discovery first?