Changelog

Reactions, read receipts, and stickers in chat

Discussion happens where the record lives. Chat now supports reactions, read receipts and stickers, so the lightweight signalling a team does all day, acknowledging, agreeing, confirming somebody saw it, does not have to move to Discord and take the context with it. The reason to care is not that chat is a missing feature. It is that every conversation which leaves takes the decision with it, and six months later the record says a choice was made and nothing says why.

#005Collaboration
Try itChat

Reactions and read receipts

React to a message beside the bubble, and see who has read it. Reactions do more work than they look like they do: a thumbs up on a proposed number is a decision recorded in one tap, by someone who would not have written a sentence. Read receipts sound trivial until you are the lead chasing four people for a sign-off, where knowing the message landed is the whole difference between following up and waiting. Both are the cheapest kind of signal a team sends and the first thing missing chat drives to another tool.

A thread with the parts that used to live in Discord

Stickers, uploaded or drawn in the app

A team can build its own sticker pack, either by uploading an image or by drawing one in the app with a brush and a small palette. Stickers are shared across the organisation rather than owned by whoever made them, so the running joke about the nose cone becomes a thing everybody has. This is not a serious feature and it is not pretending to be one. A tool a team actually lives in has room for that, and a tool with no room for it is one people keep a second tab open next to.

Screenshots, photos, files and GIFs

Messages carry attachments, and most of what gets posted is a picture: a screenshot of the error the ground station threw, a photo of the part on the bench, a frame from a test video. Any of them explains in one message what would otherwise take four paragraphs and still be misunderstood. Files, images, GIFs and stickers all attach the same way, and because they land in the chat attached to the project rather than in somebody's direct messages, the screenshot of the failed run is still there in six months when the review asks what actually happened.

Delivery fixes

Messages appear as they are sent rather than on the next reload, and grouped messages no longer reserve empty space for a toolbar that is not there. Small, but this is the difference between a chat people trust and one they refresh to check, and a chat people refresh is one they eventually stop using.