Use comments for object-attached discussion and review notes, textarea for the field used to write longer text, feed for stream consumption, and activity log for durable event history.
Use comments for object-attached discussion and review notes, textarea for the field used to write longer text, feed for stream consumption, and activity log for durable event history.
Practice the judgment: Imagine this situation: A product puts every object comment into a global feed and loses the exact selected text, file line, or record that the comment was about. Write the person's goal, choose one of these patterns, and show the state that helps the person continue. Use the decision rules and source trail below to explain your choice.
Review the underlying principle →| Dimension | Comments | Textarea | Feed | Activity log | Notification center | Review queue |
|---|---|---|---|---|---|---|
| UI or UX | UI + UX - Object-attached comment composer and comment list with authorship, replies, state, permissions, and moderation | UI + UX - Multi-line freeform writing field | UI + UX - Dynamic stream of article-like updates that may load or insert content at either end | UI + UX - Searchable and exportable record of system, user, or administrative events | UI + UX - Durable user-opened notification history and action drawer | UI + UX - Actionable queue for triaging many items that need human review |
| UI guidance | Render comments as anchored contributions with author identity, timestamp, body, optional attachment or selection context, edited state, reply target, and state labels such as open, resolved, hidden, deleted, or assigned. | Render a persistent label, enough visible rows for the expected answer, optional hint, readable multiline text, visible focus state, and nearby error or count text associated with the textarea. | Render the feed as a labelled stream of item boundaries where each item has a source or author, timestamp, title or body summary, type, actions, and enough context to stand alone as an article-like update. | Render activity logs as evidence-oriented records with event time, actor, action, object, source system, scope, result, and technical context such as IP address or location when available. | Provide a persistent notification entry point, usually a bell or inbox control, with a count that represents new unseen notifications rather than every unread item forever. | Render review queue as an actionable worklist with queue scope, counts, filters, sort order, row reason, owner, priority, age or SLA, status, preview context, selection, and row actions. |
| UX guidance | Preserve comment drafts, anchors, authorship, notifications, edit history, deletion outcomes, and resolved or hidden states so conversation context remains trustworthy across reloads, permissions, moderation, and return visits. | Use textarea when users need to write or paste sentences, paragraphs, explanations, notes, or comments that may wrap across lines. | Use feed when users consume a continuing stream of posts, updates, stories, events, or collaboration activity and need to keep their reading position while new or older content appears. | Use activity log when users need to investigate, audit, verify, or troubleshoot actions across accounts, objects, systems, settings, or security boundaries. | Use a notification center when users receive enough asynchronous system or collaboration updates that they need a durable place to review, triage, and act later. | Use review queue when a team repeatedly processes a changing set of tickets, comments, pull requests, content items, cases, requests, or records that require human inspection and action. |
| Good UI | A document margin comment shows the selected paragraph, author, timestamp, body text, Reply, Resolve, Assign, and Copy link actions with the composer focused on that selection. | A more-detail field has a visible question, sensitive-data hint, five visible rows, wrapping text, remaining-character count, and an error directly above the textarea when needed. | A project feed shows source avatar, actor, timestamp, object name, excerpt, item type, unread marker, reply and save actions, and a visible queued-new-items banner while the reader is midstream. | An organization audit log table shows timestamp, actor, action, target object, app, IP address, result, and a Details drawer with before and after fields. | A bell opens a drawer with Unread and All filters, showing comment mentions, approval requests, export results, and background-job failures in newest-first order. | A moderation queue has Held, Likely spam, Reported, and Escalated tabs, row evidence, policy reason, reviewer claim state, approve/remove/escalate actions, and bulk-action preview. |
| Bad UI | A Notes textarea sits under a record and calls itself comments even though every user overwrites the same field. | A paragraph question is squeezed into a single-line input that hides most of the answer. | New posts appear above the current paragraph and shift the page while the user is reading. | An export button downloads a different date range and timezone than the on-screen filtered log. | Users ignore the center because duplicate low-value messages inflate the badge. | The most urgent or oldest item is buried by default sort. |
| Good UX | A reviewer comments on a selected line, adds an action item for Dana, receives a reply, resolves the comment, and can reopen it from the resolved filter. | A user writes two paragraphs, sees remaining characters update, submits, and the exact line breaks and wording are preserved. | A user pauses live updates, reads three older posts, sees 2 new updates waiting, then chooses Jump to latest when ready. | An admin filters to failed SSO events, expands one entry, copies the event ID, exports the filtered range, and sees that records older than 180 days require a different archive. | Opening the notification drawer clears the new-notification badge while unread items remain available for later triage. | A reviewer claims the oldest SLA-at-risk ticket, opens a preview, assigns it to Billing, returns to the queue with the row removed, and lands on the next oldest item. |
| Bad UX | A user writes a long comment, loses network connection, and the draft disappears when the page reloads. | A user writes a long explanation, hits submit, and the product clears the entire draft after a length error. | The feed jumps to the top whenever a new post arrives. | A user marks a notification read and the corresponding activity evidence disappears from the only log. | Users mark all notifications read and lose the only record of an export job they still need to download. | A reviewer marks a pull request reviewed from an old queue row after the author pushed new commits and re-requested review. |
| Best fit | Feedback must preserve author, timestamp, reply, resolution, assignment, or moderation context. | Users need to write sentences, paragraphs, comments, explanations, notes, or descriptions. | Users consume a continuing stream of updates, posts, stories, comments, media, or collaboration activity. | Users need to inspect recorded user, admin, system, security, or integration events. | Users receive multiple asynchronous updates across objects, jobs, collaborators, approvals, or reminders. | A team or individual repeatedly reviews many independently queued items. |
| Avoid when | The user is simply entering a long answer into a form field. | The answer is a short one-line value. | The content is a finite set of objects that users need to filter, sort, select, compare, or manage. | The goal is only to show a readable milestone history for one case or process. | The product has only occasional current-action feedback that a toast or inline status can handle. | The task is a single request moving through a governed approval route. |
| Required state | Empty comment list and first-comment composer. | Empty untouched state with visible label and optional hint. | Default feed with heading, order label, rendered item count or range, and article-like items. | Default log state with event records, result count, visible timezone, retention window, and permission scope. | Closed entry-point state with zero, new-unseen, and unread-but-seen counts. | Queue loading and count state |
| Accessibility burden | Label the comments region with the object or selection being discussed. | Associate the textarea with a visible label that states the writing prompt. | Give the feed a heading or accessible label and expose the current order or filter in text. | Use table or structured list semantics so actor, action, object, timestamp, result, and scope are perceivable together. | Announce new notification arrival with status semantics when appropriate, but avoid interrupting users repeatedly for low-priority center items. | Use labelled queue name, count, filters, sort, group, row status, selection, preview, and action controls. |
| Common misuse | Using one shared Notes field as a comment system and overwriting prior contributors. | Using a single-line input for paragraph answers. | Calling any vertical card list a feed even when it is a bounded object collection. | Using vague activity labels that omit actor, action, object, timestamp, or result. | Treating the badge count, unread count, and total notification count as one number. | Treating review queue as approval workflow and hiding many-item workload controls. |