To me the proof that the paradigm is good and it's a 'just' a UI problem is MS Teams. Teams has basically the same thread system - every message in a Teams channel is in a 'conversation'. When a whole org adopts Teams sometimes it takes some people a little time to learn not to create a conversation for every reply (my partner's company is non-technical and had this for a couple of people) but once you're going the system is clear to a new joiner. At my company (an engineering org) the thread system is universally used, works extremely well, and I've never encountered anyone who wasn't clear how it worked.
The big difference is that in Teams you don't have to name your 'conversation'. You can optionally give it a title if you want, but it's not necessary and that "what do I call it" step was always a bit of a mental speedbump in Zulip for my team.
We are actively working on several ideas in this space. (One of the most important that was released in 4.0 is the redesign of the Reply button to make starting a reply feel like it does in other chat tools).
I expect we'll be able to get into a really nice place with a combination of new settings with some mixture of "Easy mode" defaults, design changes, and onboarding adjustments. (We will do this while carefully preserving model/paradigm, in case anyone's worried). Feel free to stop by chat.zulip.org if you want to discuss specifics.
FWIW, we regularly hear from large organizations, including some with thousands of nontechnical users, about their having great luck migrating to Zulip. Usually they tell us they did a 30-minute training and then things went smoothly from there, or they didn't and it took a couple weeks for some users to get the hang of it.
In the scheme of things, doing a training is a pretty minimal investment to be able to use a better product for hundreds of hours a year. But of course Zulip would grow a lot faster if nobody worried whether their nontechnical users will thrive on it, so this area is a priority for us.
Your proposals would get rid of its main feature and go completely against one of its core ideas.
I just don't get how it's difficult to reply or quote someone's message when it's such a basic chat feature.
Instead they invent weird code like "shrug" thinking it's funny during business chat.
Also I often get logged out of mobile app and notifications stop reaching which makes it very unreliable as a business tool.
They need to fix where it matters.
On logging out of mobile apps, often that's from an IT security policy to have sessions last only a fixed number of days from the last login.
We added a feature to automatically extend the session length based on the last login of a user--so inactive users get their sessions expired for security, and active users don't.
If you're a long time user of Mattermost you might need your IT admin to switch on the setting: https://mattermost.com/blog/session-expiry-experience/
It was set to be on by default in Mattermost v5.24.
Regarding replying, we've been working with our community on adding different options for threading: https://mattermost.com/blog/dev-sneak-peek-collapsed-reply-t...
From the blog post you can join the discussion on the topic if you like as well. We're very open to your feedback,
Just curious, have you enabled the GitLab-Mattermost plugin? https://github.com/mattermost/mattermost-plugin-gitlab#confi...
If it wasn't easy to find, that's on us, and we need to do a better job in making things more discoverable.
tabbot: if you happen to see this, please please consider some kind of easy-mode which:
I'm convinced with a bit of work to make it easier for new users you'll have a big boost in growth.