Hosted onhoraciohdev.dev.hyper.mediavia theHypermedia Protocol

Linear Inline Comments UX

Summary

Linear's comment experience feels extremely focused and efficient. The interaction is designed for speed and minimal disruption, staying consistent with Linear's overall philosophy of reducing interface complexity and keeping users in flow.

The experience is built around text selection, contextual actions, and lightweight discussion. Rather than drawing attention to the commenting system itself, the interface emphasizes the document content and makes commenting feel like a natural extension of editing.

Interaction Flow

    The user selects a text range.

    A contextual toolbar appears near the selection.

    The comment action is available alongside formatting controls.

    Choosing the comment action opens a compact composer.

    The user writes and submits the comment.

    The selected text becomes visually annotated.

    The discussion remains associated with the selected range and can be revisited later.

UX Pattern

Pattern name: Contextual annotation

The key characteristic of this pattern is that commenting is treated as a contextual action rather than a separate mode.

The user never has to leave the editing workflow to create feedback. Comments emerge directly from interaction with the content itself.

What Works Well

Minimal interruption

The workflow requires very few steps and does not force navigation away from the document.

The user remains focused on writing or reviewing.

Consistent interaction model

The comment action appears in the same place as other text editing operations.

This creates a predictable mental model:

"Anything I want to do with this selection is available here."

Users do not need to learn a separate commenting workflow.

Clean visual hierarchy

The document remains the primary focus.

Comments exist, but they do not dominate the screen or compete with the content for attention.

This makes the interface feel calm and lightweight.

Fast review workflow

The interaction is optimized for situations where users need to leave many comments in a short period of time.

The selection → comment → submit flow feels efficient and repeatable.

Potential Friction

Discoverability

Because comments are initiated through text selection, users may not discover the feature immediately unless they already understand how annotation systems typically work.

Reduced visibility of discussion

The interface prioritizes cleanliness over visibility.

This can make active conversations less noticeable compared to systems that expose comments more prominently.

Fewer visual cues

The lightweight approach works well when comment volume is low or moderate.

In heavily reviewed documents, users may need additional navigation tools to understand where discussions exist.

Design Characteristics

Strong emphasis on flow

The interface minimizes context switching.

Users can:

    select

    comment

    continue writing

without feeling like they entered a different mode.

Low visual weight

Comments feel lightweight and non-invasive.

The document remains readable even when annotations exist.

Editor-first philosophy

The interaction suggests that the document is the primary artifact and comments are secondary metadata attached to it.

This makes the experience feel closer to writing than to discussion.

Design Takeaways

Ideas worth borrowing:

    Surface comment creation through text selection.

    Place commenting alongside formatting actions.

    Keep the comment composer lightweight.

    Preserve focus on document content.

    Minimize modal dialogs and navigation changes.

    Make annotation creation feel as fast as formatting text.

Inspiration for Seed

Linear's approach would work particularly well if Seed wants comments to function as lightweight review annotations rather than full discussions.

The strongest aspect of the experience is its efficiency. The interaction introduces almost no friction between identifying something worth discussing and starting that discussion.

If collaboration in Seed is expected to happen frequently while users are actively writing, this pattern provides a strong example of how to integrate comments without making the editor feel heavier.

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime