If something is E2EE it is deeply inconvenient and fragile. If something is easy to use, it cannot be E2EE.
Another fairly good rule of thumb is that any product specifically marketed based on privacy fears is probably snake oil.
Another fairly good rule of thumb is that any product specifically marketed based on privacy fears is probably snake oil.
The only difficult part of E2EE is establishing trust. As in: how do I securely exchange encryption keys with this other entity in a way I know isn’t being spoofed?
The online banking I do all the time is E2EE from my device to my bank and it’s convenient and not fragile at all. I message friends over iMessage and there’s nothing inconvenient or fragile about that.
If a developer can’t put together a solution that’s convenient and robust, it’s likely due to lack of experience, not anything inherent to E2EE.
E2EE is often difficult because it involves 2 or more parties at either end. You must exchange keys in some secure way and that should occur over a P2P/alternate channel. That is really hard to do when you're not in physical proximity.
In this case, you own both sides _and_ it's likely that both devices will be on the same network to connect P2P. Many of these wifi devices handle initial setup with a device2device connection that then does the Wifi hand-off.
https://en.m.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_e...