Summary

Google Docs has one of the clearest and most mature inline comment experiences. The interaction is optimized for document review: users select a text range, add a comment, and the discussion appears in a dedicated margin thread while the selected text remains highlighted in the document.

The overall UX feels structured, explicit, and review-oriented.

Interaction Flow

The user selects a text range.

A comment action appears near the selection or in the toolbar.

The user clicks the comment button.

A comment composer opens in the right margin.

The selected text is highlighted in the document.

The user writes and submits the comment.

The comment becomes a persistent thread aligned with the selected text.

UX Pattern

Pattern name: Margin-based annotation thread

The comment is visually connected to the selected text, but the conversation lives outside the main document body. This keeps the document readable while still making feedback visible.

What Works Well

The relationship between text and comment is very clear. The highlighted range shows exactly what the comment refers to, and the margin card gives the discussion its own dedicated space.

The right-margin layout is excellent for review workflows because multiple comments can be scanned quickly without opening each one individually.

The model is also very familiar. Many users already understand Google Docs comments, so the learning curve is low.

Potential Friction

The experience depends heavily on horizontal space. It works very well on desktop, but less naturally on narrow screens.

The comment UI can also become visually busy when many comments are active. In dense review sessions, the margin can feel crowded.

Another limitation is that comments feel more like a formal review layer than a lightweight conversation. This is powerful for editing documents, but may feel heavier inside more fluid knowledge-base or block-based apps.

Design Takeaways

Ideas worth borrowing:

Keep the document body clean.

Use persistent text highlights for commented ranges.

Place discussion threads outside the writing flow.

Align comment cards spatially with the related text.

Make comments easy to scan in bulk.

Support resolve/reopen as a first-class review workflow.

Inspiration for Seed

Google Docs is a strong reference if Seed wants comments to support serious review, editing, and collaboration around long-form documents.

The strongest idea to borrow is the separation between content and discussion: the document remains readable, while comments live in a structured review layer.

For Seed, the main challenge would be adapting this pattern to a more flexible, block-based, local-first environment where users may not always have a wide document canvas.