Absolutely true.
Telegram: Best UI. Signal: Best privacy. WhatsApp: Largest userbase.
It's interesting to think about these three dimensions. I could theoretically pinpoint everything that make Telegram's UI the best, and copy it. I could do the same with Signal's privacy. Both of these are technical problems. There's a process for becoming the best at UI, and there's a process for becoming the best at privacy. I don't know a process for becoming the one with the largest userbase.
Other than the 3 big ones, I recently found Jami [1]
Good UI, though not as good as Telegram. Arguably better privacy than Signal - you don't even need an account if you don't want. Zero userbase. Free software.
> There's currently no Matrix to speak of, but it's the thought that counts.
Welp! I was going to ask about it. I’m curious how that goes because Matrix is the natural thing to support, but I’ve been quite critical of that being too hard to actually do. The Rust SDK supposedly provides a lot of support here, so maybe the experience won’t be too bad. Some inherent protocol stuff may still limit the UX and I‘d love a thorough writeup on it.
This. I can't abide VSCode. I instead use Qt Creator for all my C++ development.
Rust is simply not meant for GUI-based data design but I still want Qt in Rust. That's it. Not QML or Slint or egui or Tauri or gpui or Iced. No markup at all. None of the immediate mode things. No double and triple languages like this C++ mess. Definitely not GTK or the other non-imperative subpar things. There is one option. Until there is more than one, Qt is the best. No one else is worried about this missed opportunity.
I am seeing that you are writing a matrix client UI basically which is nice but I am interested if its possible that you could write it in (agnostic?) UI way if if it makes sense, where I can swap out any other protocol instead of matrix too
I was just interested in something similar once and there are other protocols like session,simplex,signal etc. too which I feel like can definitely benefit from an unified UI perhaps
Personally I am always interested if any messaging app should just create a cli application/api and have someone else create the UI since I feel like the UI bugs and similar can definitely be fixed if its not in house.
I am curious of your opinion regarding it but the project looks cool!
Personally although I can enjoy telegram's UI, nothing beats cinny's UI ever.
Cinny has the best UI of any messaging app I have ever seen personally, there are only very few things I wish to change in that, which can be changed via userstyle and even recent modern element feels good to me personally but cinny is brilliant overall
So I am interested to hear what your thoughts are on cinny too (cinny.in)
I have a similar problem with JetBrains RustRover. For example when I do cargo build and cargo clippy in the terminal after RustRover has done build it seems to start over rebuilding more things than when I edit something in vim and only use cargo from the terminal.