Earlier quoted context omitted.
I disagree--it doesn't feel resolved. I've been trying to use Matrix for so long now, and just recently gave another shot at helping my partner get up and running with Element X on her M4 iPad. It's still so clunky and so difficult to get off the ground. To start, E2E key verification just wouldn't work on Element X; she had to install Element, verify my key there, and go back to Element X. That would be easy to over…
This sounds very strange. Element X on iOS is a native Swift UI app, and for me (even in an enormous account) it’s super snappy - similar to WhatsApp or Telegram or iMessage. It’s not Electron, which is only for desktop apps; is there a chance you’re mixing up Element X with Element Web/Desktop (which is still sluggish, but should get much-needed upgrades this year)?
If I'm using a mobile app, chances are I'm on-the-go. I probably have a slow, high-latency, or otherwise unreliable connection. It's possible it comes down to protocol differences that hinder UI responsiveness.
Edit: As a test, I just sent a message from my phone while on a cell connection with good service. Hitting the send button felt unresponsive: it took a bit for the message to appear in the chat history (maybe 100-200ms). That's on a stable 300 Mbps connection mere miles from my homeserver.
For contrast, Telegram doesn't wait to clear my text area. I can queue further messages to send even if my first hasn't gone through. Same for Slack and Discord.