thats one of the main operational challenges. AirDows attempts a direct connection first and only uses TURN when NAT conditions require it. I'm already measuring relay usage and evaluating sustainable TURN providers and limits while keeping the beta free...
you're right, AirDows started as a Spanish first beta, and some pages are not fully localized yet, i'm fixing the language consistency before the next round of promotion thanks for pointing it out
Thanks, bluetooth-based file transfer is not reliable enough across modern web browsers, especially on iOS, i may explore Bluetooth for nearby device discovery in a future native companion, while keeping WebRTC as the actual transfer channel
I built AirDows, a browser-based tool for transferring files between devices using WebRTC.
The idea is simple: open AirDows on two devices, connect them using a QR code or temporary PIN, and send files without creating an account or uploading them for later download.
AirDows attempts a direct peer-to-peer connection first. If the networks cannot establish a direct route, it uses an encrypted TURN relay. The files are not stored by AirDows.
It currently supports:
- Transfers across different networks
- QR code and temporary PIN pairing
- Direct-to-disk writing in supported browsers
- Compatibility mode for other browsers
- Large-file transfers
- Transfer queues, cancellation, and resume support
- PWA installation
It is an early free beta, so both devices need to remain active and performance depends on the browsers and network route.
I would appreciate honest feedback on reliability, privacy, the pairing flow, and large-file transfers.