Interresting project!
So basically, peer discovery is through Cloudflare, until a connection is made, and then it gets sent through google? And since there are a lot of AI generated assets: How much of your code was AI generated?
Discovery is through standard webRTC signalling done using Cloudflare, then all the user messages are sent peer to peer, no server in the middle. I have used AI mainly to troubleshoot and correct bugs.
Wow, this certainly seems way more robust than Briar. I especially like the Bluetooth integration. However, I'm wondering about why the white paper says nothing about offline devices. For example, what happens if you try to send a message while the other person is offline and then you yourself end up going offline when they're online? Does that mean that the message will just never get sent until both of you are online at the same time? That's how Briar works. Briar also warns about battery drain because of the devices' constant searching of each other.
By the way, we can all also tell that the website is clearly vibe-coded, but you at least have the open source code going for you.
You got it right. Messages are sent as soon as both the devices are online. The retry pipeline runs on Android's WorkManager, which cooperates with Doze and App Standby instead of fighting them, so the app doesn't sit in a tight loop draining battery while waiting. Testing with friends and family hasn't shown any battery drain so far, but honestly that's a small sample, maybe a dozen devices total, and friends and family are always a little bit biased. That's exactly why I've gone to Open Testing on Google Play. I need real people, on real networks, on real battery profiles, to find the cases I can't reproduce alone. If you (or anyone reading) wants to poke at it, that's the most useful thing you could do for the project right now.