Activity Feed

An activity feed is the time-ordered record of what has happened to one thing: what people said about it, what the system did to it, and what got attached along the way: held together by a rail down the side so the entries read as one thread rather than a pile of notifications. The six blocks here run from whole thread pages down to the rows they are built from.

Two kinds of row live in every feed and they should not look alike. A person's row carries an avatar, a name, a time, a body and the reactions it drew. A system's row carries a glyph where the avatar would be and a single sentence naming the object it acted on. Give them the same weight and a channel of conversation reads like an audit log. Read state is the other thing to settle: marking the whole feed read the moment it opens is convenient for the badge and useless for the person, who came back to find the line they had got to.

18 blocks

Thread feed

Team channels and project threads: a day of activity with one place to answer it

Thread feed, open in place

Busy threads where the replies should stay beside the message

Thread feed, catch up

Returning to a channel: what you missed, and where it starts

Pull request thread

Code review: commits, a diff and the checks that gate the merge

Pull request thread, merge box

Code review that ends in a merge: the checks run, then the button wakes

Pull request thread, inline review

Code review on the lines: comments live under the code they are about

Event rows

The rows a system writes: something happened, nobody said anything

Message rows

The row a person writes: what they said, who reacted to it and what you can do with it, in a live channel

Quoted entry

Anything an integration posts: a message pulled in from another surface

Event rows, stacks

Busy threads: a burst of changes folded into one line

Event rows, rail

The quietest feed: a timeline you glance down

Quoted entry, pull quote

A quote worth keeping: the message is the entry

Quoted entry, context

Quotes you want to check against the conversation around them

Message rows, quick react

A busy channel where one tap is the whole reply

Message rows, calm

A channel that is mostly reactions: the thread stays readable

Thread entries

Threads that carry something: an upload, under the replies it drew

Thread entries, by file

Threads about uploads: filter the replies by the file they are about

Thread entries, moments

Feedback on a capture or a document: replies pinned to a second or a page

01

Using Activity Feed

Reach for it when

  • A record whose history mixes system events with what people said
  • Code review, where commits, a diff and check results belong to one thread
  • Team channels that need one place at the foot to answer from
  • Threads where the reply count matters more than every reply

Reach for something else when

  • Alerts a person triages and clears: a notifications inbox with read state fits better
  • Dated milestones with no conversation around them: a timeline is lighter
  • Logs people filter, sort and export: give them a table
02

Where it shows up

01

Pull request threads

Commits with their hashes, a diff people argue about, the checks that gate the merge and the merge itself, all on one rail so the order of events is never in question.

02

Project channels

A day of a team's work in one scroll: who joined, what was said, what was uploaded, which replies are still unread, and a composer at the foot to answer any of it.

03

Record history panels

The panel on a deal, a ticket or a document that answers what happened to this: status changes and renames written by the system, sitting beside the notes people left by hand.

04

Integration posts

Something an outside service dropped into the thread, quoted in a card of its own with its source mark and its time, so it is clear that nobody in the room typed it.

03

Questions

Should an activity feed be newest first or oldest first?

A conversation runs oldest first, with the newest at the bottom and the composer under it, because that is where the reader is already looking when they reply. A monitoring or audit feed runs newest first, because the latest event is the reason anyone opened it. Pick one per surface and keep it; do not flip the order behind a filter.

How should a feed handle threads with many replies?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.