Element is a Matrix client, so you connect to the global open Matrix decentralised network, rather than just closed-source servers run by a (newly-sold) company like Threema. Typical Matrix implementations are entirely Apache licensed open source, so you get full control and visibility both clientside and serverside. Matrix also already provides synchronised multi-device conversations, as well as more advanced cross-signing verification for E2EE key validation than Threema. Finally, Matrix is an open standard protocol maintained by the non-profit Matrix.org Foundation, that anyone can contribute to via the open governance process (https://matrix.org/foundation, https://matrix.org/docs/spec/proposals etc) - the Matrix standard gives developers full freedom to write their own clients/servers/bots/bridges/whatever.
Personally I'd say that Element & Threema have similar levels of UX polish these days (but I'm biased, working on Element). It's perhaps true that Threema's relatively limited featureset means that polish is easier to achieve.
The box I'm missing in Threema (unless I'm wrong of course) is the "not centralized" one. If for some reason (and admittedly, there aren't many realistic ones), Threema's servers/organisation are corrupted, the whole networks falls, right?
There are still major, glaring and game-breaking bugs and UX quirks in Element even after a full frontend rewrite (that, by the way, made security UX significantly worse).
(this is a US-centric comment, as phone numbers are rather static here; unlike other countries, not having a number isn't really how it works for most people on the big 4 carriers and their secondary MVNOs)
48hour refunds on google play should have addressed this conundrum but it seems people just aren't aware of it :(
But there's not a single non-German contact on there.
> a) always end to end encrypted (unlike Telegram)
> b) supports account creation without any phone number (unlike Signal)
Wire (wire.com) has had these for a long time with multi-device sync and also being open source.
much more annoying it's unreliable message delivery especially when your switch frequently between wifi and Mobile data, there are some other issues, but they killed it for me with PIN code nag
Though, sure, it would be better for the server software to be open source and rehostable too.
Also, the hardest part of such apps is the client component, not the server component. If need arises it shouldn't be hard to build one compatible to the clients.
a) always end to end encrypted (unlike Telegram)
b) supports account creation without any phone number (unlike Signal)
c) supports phones without google messaging service (unlike Signal, it formally supports it as well but in reality it's just a big battery drain)
It not being open source was always a bit sad for me, because most of the other apps on my phone are open source.
I'm curious about the multi device sync. I hope that it will be implemented in a way that doesn't use passwords but pair syncing. This is bad from a usability perspective (firefox abandoned it because of usability), but the only way I'm aware of how syncing can be made secure.