Dictionary lookup: keep the reader’s place

A headword is not always the meaning in this passage

iStoria’s Which panel says that translation can vary with position in a sentence and marks one entry Used in this chapter. Its Trees panel shows a part of speech, an Arabic meaning and Learning and I know actions. These details distinguish a contextual interpretation from a bare list of possible translations.

Retain the selected surface text separately from any dictionary headword. A lookup of an inflected verb should not erase the form the reader actually saw. Where you normalize spelling or morphology, show the relationship clearly enough that the result still feels connected to the sentence. Keep the book, passage anchor and language pair with the request so a delayed response cannot appear for a newly selected word.

When several senses are plausible, let the reader inspect alternatives without forcing a false certainty. A contextual recommendation can be labeled Suggested for this passage. Do not promote a generated explanation to a named dictionary entry unless it really came from that source. If the selected phrase is unsupported, preserve the text and offer a narrower selection rather than returning an unrelated popular word.

Make a saved word a visible state

A later iStoria state shows field in the active popup while a toast confirms which was added to known words. Eppika presents escuchó, heard and an explicit Save button above the reading progress. Both raise an important identity question: which word does the feedback refer to when the reader moves quickly?

Associate every save operation with the exact entry and passage it belongs to. If the reader chooses a new word while saving is pending, name the old word in the confirmation. Do not leave a generic Saved message that appears to confirm the newly visible term. Make repeated taps idempotent so a slow response does not create duplicate vocabulary entries.

Clarify whether Save means keep a translation, add to a study deck or simply bookmark a word. If a saved item includes the sentence, explain that scope before synchronizing it. A person should be able to remove a word from their collection without deleting the source book or changing the passage. Keep reading position independent from all of these collection operations.

Explain what the speaker control will play

Readability’s waste panel uses a short definition with plus and speaker controls. Its everything panel shows a minus control and a speaker with a slash. The icons provide a compact interface, but their meaning needs accessible labels and product-specific verification. A slash can mean muted, disabled or unavailable; appearance alone does not establish which.

Differentiate pronunciation of the word from playback of the full definition or passage. Label actions as Hear word, Read definition or Resume story where those are the actual behaviors. Starting a short pronunciation should not unexpectedly resume a whole chapter. If narration was already playing, define whether lookup pauses it and whether closing the panel resumes it.

Keep an audio-unavailable state distinct from a loading state. Provide a text meaning even when a voice asset cannot load. Avoid repeatedly announcing the full definition to a screen reader every time audio buffering changes. Children and second-language readers may need a larger control and a simpler explanation, but they still need a predictable route back to the story.

Teach hidden gestures without making them mandatory

Epic’s recorded tutorial says Tap and Hold for Dictionary Lookup. This is feature education, not a demonstration of a completed lookup. The Bible reading app instead shows a system dictionary sheet with the named New Oxford American Dictionary and Manage Dictionaries. These examples sit at different layers: discovering the action and inspecting the resulting source.

A long press can be a useful shortcut, but it should not be the only way to reach lookup for people who cannot perform the gesture. Offer a text-selection action or another accessible route. Avoid stealing every single tap from normal reading navigation. Test punctuation, tightly spaced lines and words at the screen edge before deciding how the selection handle behaves.

If you use a system dictionary, design the return path and unavailable-dictionary state around its actual behavior. An external Search Web action leaves the contained reading task, so keep it clearly secondary. Source labels help readers understand provenance; they do not automatically establish that the chosen definition is appropriate to this particular sentence.

Let depth be optional

LingQ’s cocinero popup keeps the definition close to the Spanish story and shows separate vocabulary controls. Its restaurante detail screen offers external dictionaries, popular meanings, a custom-meaning input and notes. The second surface supports deliberate study; it need not be the first thing every casual reader encounters.

Use a small first layer for the immediate question and an explicit route to fuller detail. Preserve the selected text and return anchor across that transition. When a reader follows an external reference, keep the app’s pending work safe and show which source opened. A user-authored meaning should remain distinguishable from a publisher-provided entry or another learner’s suggestion.

Lookup failure should be recoverable like other mobile error states. Test an offline dictionary miss, a phrase spanning lines, a delayed response after selecting another word and a custom meaning saved twice. Observe whether people can explain the meaning and resume at the same sentence. A high save count alone does not demonstrate better comprehension.

A lookup test with a delayed response

Use a passage containing two nearby unfamiliar words. Select the first, then select the second before the first definition has loaded. The response for the first word must not replace the second word’s active panel. Check the headword, highlighted passage and audio source together; a correct definition attached to the wrong selection is still an incorrect interface state.

Save the first word while its request is delayed, then move on. The eventual confirmation should name the saved word, while the current panel continues to refer to the newer selection. Repeat Save after reconnecting and inspect the collection for duplicates. This exercise tests the relationship between lookup identity and collection identity rather than only the speed of a popup.

Change the reader’s text size with the lookup open. The passage may reflow, so restoration should use a stable content anchor rather than only a pixel scroll offset. Dismiss the panel and ask the reader to resume the exact sentence. Repeat with a word near the bottom edge and a phrase containing punctuation.

End by opening a deeper dictionary source and returning. Keep the original selection and pending vocabulary state intact. Log the type of recovery failure without copying the reader’s private book text into analytics. The practical success criterion is a correct, inspectable answer followed by an unsurprising return to reading.

Review lookup as an interruption

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

• ✓Retain passage position and selected text while panels open and close.
• ✓Keep surface form, dictionary headword, language pair and source distinguishable.
• ✓Separate checking a meaning from saving or changing learning status.
• ✓Name the word in delayed save or failure feedback.
• ✓Label pronunciation and narration controls by what they actually play.
• ✓Support an accessible alternative to a long-press-only entry gesture.
• ✓Test offline misses, stale responses, large text and external-reference returns.

Related design decisions

For the surrounding study journey, compare the language-learning onboarding article while keeping this in-reading task optional.

If readers later return to saved vocabulary, the saved-item examples help distinguish a collection state from a temporary lookup.