Text annotation UX: keep notes anchored

Keep the selected passage identifiable while choosing an action

GrowMe shows selection handles with Copy, Highlights and Add note in a contextual menu. Bible App Read Study presents a Highlight sheet with a verse reference and translation alongside named colors. The first keeps the action close to the selection; the second carries the source identity into the annotation surface.

Do not lose the selection when a sheet opens or the keyboard appears. Keep enough context to confirm what will receive the highlight or note. For a short passage, a preview can be useful; for a longer selection, show a clear range or source reference rather than truncating it so aggressively that two different passages become indistinguishable.

If the selection spans paragraphs, pages or sections, explain any limit before saving. Preserve the attempted range when asking for an adjustment. A silent trim to the current page can create an annotation on the wrong text. Selection handles should remain usable near screen edges, and the action menu should avoid covering the only visible evidence of the selected passage.

Decide whether highlight colors have names or meanings

Fable offers categories such as Important, Quote, Favorite and Poetic for a selected passage. Instaread shows system text actions alongside a separate Highlight action. The comparison exposes a product choice: annotation can be a simple visual mark, or it can assign a category that later supports retrieval.

If colors stand for categories, show the category name and allow people to understand it without color perception. A yellow mark alone cannot reliably communicate Important. If categories are user-defined, preserve the category identity when its display color changes. Renaming a category should not make old annotations become unclassified or rewrite their source anchors.

Keep basic actions available without forcing a taxonomy. A person who only wants to mark a sentence should not have to invent a tag system first. Offer a sensible default highlight, with richer organization as an optional step. Distinguish Copy, Highlight and Add note through labels and predictable results rather than relying on nearly identical small icons.

Keep the active annotation tool separate from saved marks

Apple Books shows a compact palette with several colors and an underline option. Documents exposes annotation tools and a separate highlight-color sheet. A selected tool describes what the next gesture will do; a selected annotation describes an existing saved object. Mixing those states can make a color change affect the wrong thing.

Make the editing context explicit. When a saved highlight is selected, a palette can change that highlight. When no annotation is selected, a palette may set the color for future highlights. The interface should not use the same visual treatment for both without a contextual cue. Otherwise someone adjusting a default can unexpectedly recolor a passage they meant to keep.

Provide an understandable route out of annotation mode. Document tools often remain active across several selections, while a reading menu may close after one action. Either model can work if the next gesture is predictable. Keep page scrolling available without accidentally adding marks, and make undo target the last annotation operation rather than unrelated document navigation.

Carry source identity into notes and related actions

Logos presents a selected verse with a translation label and actions including Copy, Note and Search. Bible Note shows a chapter context, selected verse and options including Notes and Comparison. Those contexts matter because the same visual position can refer to different text in another edition, translation or document revision.

A note should retain a stable source reference and enough quoted context to be recognizable if the surrounding layout changes. Page numbers alone can fail when font size or pagination changes. For structured texts, a chapter or verse reference can help, but the edition or translation can still matter. For ordinary documents, source version and text anchors may be needed.

Do not silently attach a note to approximately similar text after a source update. If the anchor becomes uncertain, show the saved excerpt and ask the person to review its location. Keep the note itself recoverable even when the original document is unavailable. An orphaned annotation with a clear source explanation is better than a confidently misplaced highlight.

Make removing a mark different from deleting content

Holy Note offers Copy, Highlight, Note, Card and Share beside a selected passage. WPS includes a No Fill choice in its highlight palette. Both demonstrate how annotation and output actions can live close together, which makes clear naming important. Removing a highlight must not sound like deleting the underlying passage.

Use Remove highlight for the mark and Delete note for a saved note body. If an annotation combines both, explain whether removing its color preserves the note. A No Fill choice can remove the visual treatment while leaving another property intact, but that relationship should be visible. Avoid a generic trash icon with no indication of what it affects.

Keep sharing separate from private annotation. Opening Share should make the outgoing content and destination clear rather than assuming a saved personal note is public. If the product creates an image card, preview the excerpt and any included note. Preserve attribution and source context as appropriate to the workflow without claiming that a share action grants rights to redistribute any text.

Persist annotations independently from rendered coordinates

Give an annotation its own identifier, source identifier, source version and text anchor. Include the saved excerpt and surrounding context where useful. Keep display geometry as a rendering result, not the only record of location. A highlight stored solely as screen coordinates will drift when text size, line spacing, orientation or viewport width changes.

Save the annotation and any note body through a recoverable state. A locally pending mark can remain visible with a sync cue, but do not imply cross-device persistence before it is confirmed. If a save fails, preserve the selected range and note text. A second tap should not create duplicate annotations because the first response was slow.

Define overlapping marks, cross-section selections and imported annotations. Two highlights on the same words need an understandable selection mechanism, not an invisible stack that makes one impossible to edit. If a source revision cannot be matched, keep the original excerpt and note instead of discarding them. These are data-integrity choices that need product rules as well as UI controls.

Check whether a saved thought can be found again

Highlight a passage, add a note, change text size and reopen the source. Confirm that the mark follows the same words and the note remains reachable. Repeat across a page boundary and after changing the display theme. A screenshot of the initial selection cannot demonstrate that the anchor survives reflow.

Test offline saves, interrupted sync, duplicate taps and source updates. Check how the app explains a note whose original document has been removed. Let someone find all notes in a category, return to a source passage and edit one annotation without changing its neighbors. Those retrieval tasks reveal whether the color system is useful beyond the moment of marking.

Review selection handles, contextual menus and palette controls with assistive technology. Announce selected text and saved annotation state without relying only on fill color. Large text must not hide the commit or close action. A person should be able to remove a mistaken mark and retain their note without performing a precise long-press gesture.

Check selection, persistence and retrieval separately

Use these checks on a working build, not only on the polished reference state.

• ✓The selected source and range remain identifiable while a menu or sheet is open.
• ✓Color meanings are named and accessible without color perception.
• ✓The active tool and an existing selected annotation have distinct states.
• ✓Source identity survives font changes, reflow and edition differences.
• ✓Removing a highlight does not ambiguously delete text or a note.
• ✓Failed saves preserve the note body and original selection.
• ✓Orphaned and overlapping annotations remain discoverable and editable.

Connect annotations to reading and personal collections

The Bible-app design review provides the wider reading and study context. Annotation needs a more specific source-identity contract within that experience.

Compare saved-items interfaces when designing the collection where people return to highlighted passages and notes.