The NAT traversal angle is honestly the most compelling part here, WebRTC's ICE/STUN/TURN stack handles weird network topologies pretty gracefully without you having to think about it.
That said I think spzb's point is real, the signaling server is still a trust boundary even if the p2p channel itself is encrypted. Tailscale sidesteps a lot of that by having a more battle-tested auth model tbh.
On the "why would you even want this on phone" thing though, I guess I disagree a bit, I've been building something related: Xtro, terminal + source control + AI agent on iPhone connected to Mac, and like the use case is surprisingly legit once the layout is actually designed for mobile. Emergency deploys, quick fixes, that kind of thing.
That said I think spzb's point is real, the signaling server is still a trust boundary even if the p2p channel itself is encrypted. Tailscale sidesteps a lot of that by having a more battle-tested auth model tbh.
On the "why would you even want this on phone" thing though, I guess I disagree a bit, I've been building something related: Xtro, terminal + source control + AI agent on iPhone connected to Mac, and like the use case is surprisingly legit once the layout is actually designed for mobile. Emergency deploys, quick fixes, that kind of thing.