Zulip definitely needs more UX design work. I also wouldn't call it great either. Perhaps in comparison to the competition it would be, but it's awful compared to native chat applications.
Invisible scroll bars keep making me miss new messages just because indicators were out of the viewport. Having the browser stall routinely causes full reloads (after a delay, making it more annoying), then the reload is invarialy interrupted by the server due to request overload. Not to mention that the reload is slow already. Long messages show up collapsed, and uncollapsing them often devours whatever text was in the input field, an especially useful feature when trying to write a thoughtful reply cross-referencing multiple posts. Email notifications send out the same message multiple times, and presents author's name the same way as the rest of the text. Constant hitting on the CPU. Confusing notion of threads and forums. I could go on - Zulip is not nice.
I'd be curious to hear more about these concerns, because they're largely not things others have reported. Would you be up for dropping by chat.zulip.org to provide more detail? A few initial thoughts:
* Notification emails for PMs don't include the sender in the body at all. Those that do have the sender bolded on a line by itself. So I am not sure what you're referring to here. Maybe you're using a self-hosted server running an old version? We did a total redesign of missed-message emails in 2019.
* When closing the compose area, Zulip saves message content in the "drafts" feature, so one never loses partially composed work: https://zulipchat.com/help/view-and-edit-your-message-drafts.
* I was able to reproduce the uncollapsing bug as https://github.com/zulip/zulip/issues/15808, and fixed it a couple minutes later. Thanks for the report!
* The issues around CPU load, reloading and server issues are probably best discussed interactively, since I'd like to see browser profiles for your situation and understand if you're using a self-hosted server that might be underprovisioned, which seems a bit much to work out on a HN thread :)
Thanks for replying! I didn't expect the lead dev to actually reply. I will certainly drop by when I find enough time.
- yes, this is self-hosted. I can't check the version, but I think it was recently updated
- notification emails in non-html mode don't carry over the bold, not even in the form of asterisks, so it all blends in with multiple messages
- the "drafts" feature took me a year to discover. Sadly, messages were recomposed. I think it's useful when the composing is interrupted due to external reasons, but not something to work around user action causing clears
- thanks for fixing the collapsing bug, I'll see how my opinion on the composing workflow changes
- CPU load is not that bad, but still way worse than my IRC client or a non-JS forum, so
- I may be somewhat unique in that I automatically `kill -STOP` and `kill -CONT` the browser when not using it, sometimes keeping it frozen for days at a time. That is causing the server issues. Notably, I haven't yet seen any other software or pages having problems with that.
One thing I always respect is the desire to keep improving! Kudos!
> yes, this is self-hosted. I can't check the version, but I think it was recently updated
Well, 3.0 comes out tomorrow (hopefully) so your administrators may want to upgrade once it does :).
> the "drafts" feature took me a year to discover. Sadly, messages were recomposed
Yes, we're planning to add an onboarding notice the first time a draft is saved to avoid this failure mode :).
> notification emails in non-html mode don't carry over the bold, not even in the form of asterisks, so it all blends in with multiple messages
Oh, interesting. Non-HTML emails are hard to do much good with; if you have specific ideas for what we could change to make that better, let us know: https://github.com/zulip/zulip/issues/new
- thanks for fixing the collapsing bug, I'll see how my opinion on the composing workflow changes
Happy to! We generally fix any easy bug as soon as it's reported as a general practice, since users can really tell how buggy a product is, so hopefully this will encourage you to report more :).
Yeah but if you want truly self hosted AND full feature set (notably search and archives) AND owning your data, there isn't much available putting Zulip far on top.
IRC could do it, but IRC never got a clean and prettified client that bob from accounting knows how to use properly, and finding the proper server software sucks.
Fwiw self hosting Element and a Matrix homeserver like Synapse provides a full Matrix feature set (including search, archiving and everything else). You don't lose out for self hosting.
Invisible scroll bars keep making me miss new messages just because indicators were out of the viewport. Having the browser stall routinely causes full reloads (after a delay, making it more annoying), then the reload is invarialy interrupted by the server due to request overload. Not to mention that the reload is slow already. Long messages show up collapsed, and uncollapsing them often devours whatever text was in the input field, an especially useful feature when trying to write a thoughtful reply cross-referencing multiple posts. Email notifications send out the same message multiple times, and presents author's name the same way as the rest of the text. Constant hitting on the CPU. Confusing notion of threads and forums. I could go on - Zulip is not nice.