Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

No, there's no chance I'm mixing them up. It's Element X from the App Store. The app label is "Element X".

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.



Same here. I really like Matrix protocol but Element on desktop and Android is... Still beta? Recovering keys is not user friendly. Many family members use unverified devices after upgrade. Editing is laggy, new channels connect for ages...


I’m not sure I’m seeing what you’re describing. Here’s a screen recording of send performance (on fast internet, a few ms ping to the homeserver): https://github.com/element-hq/element-x-ios/issues/3810

The first msg does take a little longer to clear the composer, but it’s barely noticeable. And as the recording shows, it queues up msgs fine if the first hasn’t gone through.

How does this compare with what you’re seeing?


It's hard to say because I can't see when you're clicking, but that looks snappier than what I'm seeing. I'll comment further in the issue and attach a screen recording of my own.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: