Threads was one of the features of Fibery that really caught my eye when we were looking for an alternative to Notion. Now that we have had a few weeks working within Fibery, I have finally put together Threads for our team.
I was a bit apprehensive at first because I was not sure if it was a feature that was still going to be developed or supported. I posted on Reddit a few weeks ago asking about this and got a positive response. Yesterday I implemented Threads, creating some simple channels for our team to move our internal discussions into Fibery.
A little backstory on our company communication. We dropped Slack about a year ago, used Google Chat for a while, and then moved all internal chat to Missive. Missive has been a solid communication tool for our agency, but the chats and discussions have always been pretty weak: no nested views, no rich text editor. When we tested Fibery, we were impressed by how powerful it could be and already is. I already see it as a strong replacement for Slack, especially with support for connectors and automations (which I think it already has, though we have not tested them much yet).
Having everything within Fibery is brilliant because when we are discussing something, we can mention a task and see it right within the panel. That context is incredibly powerful.
However, the biggest thing missing from Threads at the moment is mobile support. It would make so much sense for us if it were well supported in the mobile app, allowing us to keep discussions moving when away from the desk. I am out of the office a lot, but I still want to keep track of discussions.
I know it is still a beta feature, but I would like to see if other users feel the same, so perhaps the Fibery team might consider this a more urgent priority.
I would also love to get a sense of what the future of Threads looks like: how will it change and evolve?
That’s interesting. On my mobile app (I’m using a Google Pixel 9 running the latest version of Fibery on Android), I don’t see the Threads view at all.
I’ve tried restarting the phone, refreshing, and logging out, but it still doesn’t show. We have a space set up specifically for the Threads channels, and a view that lets you see the channels within the space, but I can’t see the Threads view itself.
Can you clarify whether you’re talking about creating a new thread view or trying to view a thread view that already exists? On my phone (where the threads view toggle under experimental lab is turned off) I’m still able to see the thread views that have already been created.
I find this a bit concerning. If users have to turn on the experimental lab feature in order to view already created threads in mobile, that makes it less useful for mission critical conversations. Though we can direct people to turn the feature on, it’s ultimately in the users’ hands whether they do so or not.
Yes, I’m an admin. I didn’t need to get any of our users to turn on the experimental feature on desktop, so maybe they did, but I didn’t ask them to and they could see the threads views.
I’d like to provide some more feedback. We’ve been using it for a few days now, and I’ve got to be honest: even with the bugs, I absolutely love it. It’s such a great feature.
A couple of things:
Read state sync across windows:
One annoying thing happens when I have multiple Fibery windows open (which I often do, running Fibery desktop alongside a browser window opened from a link). If I’ve already viewed all the threads in the desktop app, it correctly clears them: there’s no unread counter or indicator left. However, when I go to my browser, even after a refresh, it still shows threads as unread.
Mobile notification policy:
I don’t get any notifications on mobile, which would be a great addition for Threads, perhaps as a separate notification policy. It would be nice to enable Threads notifications on mobile only when I’m offline on desktop. For example, if I’m active on desktop Fibery, don’t notify my phone; but if my desktop is inactive and someone messages in a thread, ping me on mobile.
