Although you could use local storage, you would have to do that with every browser you logged into and also somehow make it user-account-specific. I definitely see the challenges there for them.
What would you think about using a user's password to encrypt the browser keys and store them on Facebook's servers? Is that too large a compromise for usability?
What did the OP mean by "No secure way to verify code or store keys (in web browser) without routing through mobile" ?
This is why Signal and WhatsApp require the client to run on the phone - the phones are doing the decryption for the web apps.
This is flaky, consumes a lot of battery and generally is somewhat error-prone - probably not something FB wants to deal with.
You could even register only the browser, without having a smartphone at all.
Installing a malicious extension, tricking users into typing commands in the developer tools, XSSing FB, all of these are much easier to do than attacking a native app on a phone.
Certainly it can be important to know when you have a "no compromises" security option versus "mostly better than plaintext but maybe not secure".
It could be a UX judgment to not confuse users they have a "secure connection" when in fact they might not. Look at all the various attempts over the years browsers have made to keep the UX semi-reliable and easy for users to understand whether or not their SSL connection is secure.
- Signal does have some multi-device support (the Android and Desktop clients, iOS not yet). I still sometimes have minor issues but overall it works very well.
- Signal does include end-to-end encrypted voice calls (what used to be called RedPhone) that also work quite well. It's my go-to "call from Wifi abroad" solution to avoid roaming charges, and also works very well with a good 4G/3G signal
- The browser issue seems unsolved as of now, WhatsApp's web thingy (routing through the phone) seems to work quite well but obviously only if the phone is on, and WhatsApp requires a phone while FB messenger doesn't so this isn't an option for them.
- FBM is multi-device, and we'd like to see E2E usability improve to support this. For now, pick one device and keys never leave it
- Secret conversations don't currently support popular features like searching message history, switching devices, voice/video, etc
- Hundreds of millions use Messenger from a web browser. No secure way to verify code or store keys without routing through mobile.
"We don't want to disrupt people's current experience."
Source: https://twitter.com/alexstamos