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

The reason historically for multiple concurrent implementations is because we're building a protocol, and multiple implementations dogfoods that - plus the different implementations service different segments. In practice, Hydrogen and Dendrite are currently deprioritised in favour of focusing on polishing Element X and Synapse. And Element Mobile is in security-maintenance mode only in favour of Element X.

Meanwhile, we massively fixed Element Mobile's UI a year ago: https://element.io/blog/an-unrecognisable-improvement-elemen... - and Element X is essentially the same UI... but on a different engine. So I'd argue that we were very aware that Element's UI was crap, which is why we fixed it. Rewriting the Element mobile apps as Element X is unquestionably the right thing to do in terms of sharing the same rust codebase between the two platforms and letting the app layer focus on UI.

Agreed that our progress has been slow, and our focus been has very broad at points. But we got there in the end, and certainly have learned from the journey (and built Matrix to be a much broader and successful heterogenous ecosystem as a result).

I'm sure your projects are all much more successful though - I'm jealous! :D



As a very longtime user, I can say that the progress has been noticeable to me, especially in the last year or two.

Having had a look at Element X (Android), it actually feels to me like that responsiveness is pretty much the last thing I was missing.

Oh, and the call bug already mentioned in the thread.

I'm really happy with Element and thankful for all the work you guys put into it.




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

Search: