Keeping control when rewriting text
A rewrite can sound better while quietly changing a condition. In Simplify, the macOS menu bar app I’m designing and building, I made reading a suggestion and replacing the original two separate actions. This case study covers the October 23, 2026 development build.
A shortcut opens a result beside the selected passage. The person can inspect it, copy it or explicitly replace the selection. The difficult part is making sure that the text they approve is still the text the app is about to change.
Keep the task attached to the selected text
Simplify processes the selected passage and any context the person explicitly adds. It does not automatically collect the surrounding conversation from the other app. This gives the interaction a visible scope: the passage the person selected is the material being worked on.
Changing the output language starts again from that original passage. Translating an already rewritten result would introduce another transformation and make it harder to trace a changed meaning back to the source.
A replacement must still belong to its source
Clicking the result copies it. A separate replacement button appears for supported editable fields. Copying leaves the document alone; replacing writes into an editor where the selection, content or focus may have changed while generation was running.
Before writing, Simplify checks the original text, selection range, field contents and focused editor again. A mismatch stops the replacement and asks the person to reselect the passage. That interruption is deliberate: an old suggestion should not overwrite a newer edit.
현재 상황을 고려했을 때 일정을 다시 확인하는 것이 필요합니다.
지금은 일정을 다시 확인해야 합니다.
The result must remain attached to the same selection while a request is running. Closing the result cancels the request, an older response cannot take over a newer result, and the language control is unavailable during processing or replacement. If the app cannot confirm that a write succeeded, it asks the person to inspect the field instead of displaying a success message.
Position the result around a real selection
Keeping the result near the passage is intended to make comparison easier, but a selection is rarely a neat rectangle. It may wrap across lines, cross differently styled text or end near the edge of a display.
In a WebKit test document, one accessibility lookup returned only the first styled span of a longer selection. I changed the lookup to use the complete text-marker range, the editor’s representation of the selected text. That gave the popover an anchor corresponding to the whole passage.
The popover chooses its position using the available space and result height; long results scroll inside it. When an app does not expose usable selection coordinates, it falls back to the source window or input area. Precise placement depends on what the host app exposes.
Native text-field checks and nine synthetic WebKit cases covered selection direction, paragraph boundaries and editable fields. They establish specific placement and replacement behavior, not compatibility with every app. The next development step is to try ordinary passages in the intended apps, particularly sentences containing names, amounts and conditions.
The design will earn its convenience only if people can understand a suggestion and confidently decide where it belongs. Generating the text is one part of that interaction.