This week has been pretty busy at work. Hopefully it has resulted in absolutely awesome results!

✨ Cold start up time for Element X Android has significantly improved from 3-4sec to 100-150ms for accounts with 1000, 2000 or even 4000 rooms (≈30x speed up). That’s awesome! ✨

I’ll explain tomorrow how we did that. Async Rust and immutable data types simply rock.

#matrix #client #Element #ElementX #RustLang #kotlin

@hywan congratulations on the great work, really loving the new app!

Hope you don't mind the question, am sure you are all working very hard on it and do not want to seem inconsiderate, but was hoping you'd know if there is an ETA for better unread messages UX? I find it a bit hard to find where the unread messages start from or which rooms have them right now

@hhg One more performance issue to fix (will start Monday), and I’ll work on providing client-side sorting. We are aware that the current sorting isn’t ideal. It happens on the server-side, and we are going to switch that. Doing it client-side means we will be able to do other kinds of sorting too.

From within a room, you have a _New message_ marker. It works pretty well as far as I know. If you find any bugs, raise it on GitHub :-).

@hywan I'm excited for client-side sorting. This will make Element X work much better with Conduit servers, because we don't have server-side sorting :)

@timokoesters Is there any chance the DockerHub:next image is ready for Element X? If not, do you know when it will be? I've been hosting my own Conduit deployment for a couple months and I'm very excited with all the development on both it and Matrix 2.0/Element X.

@hywan @hhg @hhg

@DARbarian Conduit next already works with Element X if you specify in the well_known client file that the sliding sync server is your normal conduit server, also see this issue: https://github.com/vector-im/element-x-android/issues/1085
"Homeserver not supported" even though it natively supports Sliding Sync (Conduit) · Issue #1085 · vector-im/element-x-android

Steps to reproduce Try to log in to "conduit.rs" Outcome What did you expect? It should mostly work. Conduit supports the sliding sync endpoint without the proxy, so Element should not require a we...

GitHub

@timokoesters Thanks so much! I thought it was but I couldn't sign into Element X so I was confused. I appreciate it!

@hywan @hhg @hhg