Mobile text formatting: protect the selection

Distinguish a text object from a text range

Noteshelf shows a text box with resize handles and a formatting menu containing headings, lists and font settings. Motion shows a document body with a mention and a keyboard-adjacent inline toolbar. A box is a selected canvas object; a cursor or highlighted passage is a position inside authored text. Those contexts need different behavior.

Do not make the same selected outline stand for both. A person moving a note box should not accidentally select its words, and a person formatting a phrase should not change every text object on the page. Provide a clear entry into text editing and a separate route back to moving or resizing the object.

For a collapsed cursor, define whether a style affects future input or the current paragraph. For a range, decide how mixed styles are represented. A highlighted Bold button should not falsely imply that every character is bold when only part of the range is. Accessible state should convey this distinction rather than relying on a subtle icon tint.

Make paragraph styling different from character styling

Craft presents Heading, Body, Page and More choices with list, indentation and alignment controls. Bear displays a selected passage and a writing-focused formatting keyboard. The surfaces differ, but both bring paragraph-level decisions close to text editing rather than hiding everything in a distant settings page.

A heading action should identify the paragraph or block it changes. Applying it to a selected word should not leave the person guessing whether the result is a large inline phrase or a semantic heading. Keep visual style and document structure aligned where the product supports structured content. If the editor only changes appearance, avoid implying more than it stores.

Lists need explicit rules for Return, an empty item, indentation and Backspace. Test nested lists and a range that crosses a list and a normal paragraph. A toolbar button is only the entry point. The difficult part is preserving content and a sensible cursor position as the structure changes under normal typing.

Keep authored edits separate from generated content

Gizmo shows an active audio context, a Generate Notes card and a manual note composer with formatting tools. HyNote shows a formatted summary with a Save action and a keyboard toolbar. Both place authored text near generated or summarized material, which makes the revision boundary especially important.

Generating or refreshing notes should not silently overwrite a passage the person has edited. Decide whether the result is a new version, a proposed replacement or an insertion at a known location. Show that scope before the action. Preserve manual text until the person accepts a replacement, and offer a recovery path when the resulting content is not useful.

Do not conflate formatting with rewriting. Applying a heading should not trigger new language generation, and asking for a summary should not secretly normalize away deliberate emphasis or list structure. The recorded screens do not prove either product’s merge behavior. A product team needs to define and test these rules with an edited draft, not just an untouched generated example.

Keep focus and context when opening a second panel

Planner Pro displays a Text & Background Color panel with a grid and Apply. Evernote keeps a broad editing toolbar above the keyboard, alongside undo, redo and document metadata. Opening a deeper panel can be useful, but it should not detach the command from the range that led to it.

Capture the intended selection before moving focus into a color field or another sheet. Keep a clear way to dismiss that panel and resume typing. If Apply confirms only a color choice, do not make it look like saving the entire note. When a panel closes, restore the selection or cursor predictably rather than jumping to the top of a long document.

Choose toolbar order around the actual writing task. Frequently used commands should not require repeated horizontal searching, but advanced controls can remain available in a labeled overflow. UpNote’s product help documents an above-keyboard bar and configurable icon order, a useful example of treating access to tools as a workflow choice rather than a fixed decorative row.

Do not let extra assistance hide the editing target

Prodrafts edits a canvas text object over an image and shows font and size controls above the keyboard. Grammarly shows a document with suggestion underlines and a formatting toolbar, plus a Copy Text action. A canvas background or an assistance layer can compete with the selected text for attention.

Retain enough context to judge the edit. In an image composition, show the text against its real background rather than only inside a detached field. In an assisted document, distinguish a spelling or grammar suggestion from a selected range. Accepting a suggestion should not unexpectedly change the formatting target or move the cursor to an unrelated paragraph.

Explain what copying or exporting preserves. Plain-text destinations cannot represent every style, while rich formats may support only a subset. Do not promise that a Copy Text button retains headings, lists or colors without checking the destination. Where formatting will be simplified, preserve the authored words and make the difference understandable instead of presenting the loss as an editing error.

Treat formatting as a reversible document operation

Keep document structure, selection and pending input as explicit state. A formatting command should receive a known range or block, not recover its target from whichever view happens to have focus after a sheet opens. When the document changes asynchronously, remap or validate the saved range before applying the command.

Group undo by meaningful writing operations. Typing a phrase, toggling a style and applying a color should have understandable recovery boundaries. Avoid one giant undo step that removes an entire writing session or hundreds of tiny steps for one toolbar action. Preserve composed input until the input system completes it rather than prematurely formatting an intermediate character sequence.

Define paste and conversion rules. Content arriving from another app can include unsupported marks, nested lists and invisible structure. Normalize safely without losing the words, and make plain-text paste a deliberate option if it serves the product. Test save and reopen with the same document model; a correct-looking editor is not enough if persistence drops structure.

Test editing sequences, not isolated toolbar taps

Write a sentence, format one phrase, move the cursor, add a list and open a color panel. Ask the tester to predict what the next keystroke will inherit. Repeat with a range containing mixed styles. A clean empty document can hide selection and insertion bugs that appear immediately in a realistic note.

Use long content, large text, a hardware keyboard where supported and multiple input methods. Verify that the selected passage stays reachable when toolbars wrap or the keyboard changes height. Check an interrupted session and a regenerated summary after manual edits. Recovery should preserve authored content even when another service or a saved document is temporarily unavailable.

Measure wrong-range changes, cursor jumps and undo failures separately from document creation. More formatting taps do not necessarily mean a better editor; they may indicate repeated correction. A useful test ends with the person able to explain what changed, continue writing and restore the previous state without reconstructing the note.

A writing-focused formatting review

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

• ✓Object selection, text ranges and insertion points have distinct states.
• ✓Inline and paragraph commands identify the content they affect.
• ✓Mixed formatting does not appear falsely uniform in toolbar state.
• ✓Opening a sheet preserves the intended range and a route back to typing.
• ✓Generated replacements cannot silently erase authored revisions.
• ✓Lists, paste, composition and undo preserve content through normal editing.
• ✓Copy, persistence and export are tested with their actual supported formats.

Connect formatting to capture and recovery

The AI note-taking design examples cover the wider capture and generated-note flow. This article focuses on the authored document after text exists.

Use the mobile error-state examples to keep failed saving or generation from becoming a loss of the editing draft.

For one product’s documented toolbar behavior, see UpNote’s formatting help. Its instructions are product-specific rather than a universal editor specification.