Hacker News new | ask | show | jobs
by rpm91 2236 days ago
Do you know why the decision was made to rewrite rather than do an incremental migration, given the increased pain to users? I have some guesses from looking at the codebase, but I'd love to know the actual answer.
1 comments

The old app had bad layering, and no explicit storage layer. We wanted to experiment with different storage layers, use rx for data flow, switch from java to kotlin, and use all the latest androidx/jetpack best practices. This amounted to a whole new app, and it was easier to start from scratch, despite the disruption to users.
I have to say riotx is miles ahead of riot android. If only it could do voice and video yet. For desktop I have to say riot has been really on and off. In particular voice/video calls are hit and miss. Sometimes it rings but one can't pick up, sometimes it just does not ring. I actually have been experimenting with some of the alternative clients (I particularly like nheko reborn) unfortunately non do voice video yet.
the 1:1 voip in Matrix has never been properly fleshed out. we’re planning to fix this over the next few months however.