How much text at once

One word, a verse, a passage or a whole chapter?

People increasingly read Scripture on phones, in short and frequent sessions. Apps answer with verse cards, focus modes, read-along highlighting and even speed readers. Each decides how much of the Bible someone holds in mind at once, from a single word to a whole chapter. The church has read in many measures. An app should help people hear the word, not just get through it.

The spectrum

From one word to a whole chapter

  1. 1One word at a timeBorrowed Total focus, no lost place No looking backTry it →
  2. 2One verse at a timeObserved Slow, meditative, memorable Context out of sightTry it →
  3. 3One verse in focusObserved Attention with context Moving text needs controlTry it →
  4. 4One passageObserved A natural beginning and end Boundaries are editorialTry it →
  5. 5Whole chapterFamiliar convention The story stays whole Long on a phoneTry it →

Stills from the working example below. Choose one to try it.

Try it

Try five amounts of text

Someone has a few minutes before work and opens Mark 4 at the storm on the sea (4:35–41). Every option starts there, in the Berean Standard Bible. Read to the end of the passage, then try to find what Jesus was doing just before.

Prototype controls

Option

Verse numbersNot used here
Read aloudNot used here
Why these settings?

Verse numbers are a sixteenth-century addition: helpful for finding and citing, and a reason people read sentences apart from their argument. Hiding them gives a reader’s-edition feel. Read-aloud is simulated: nothing plays, but the focus or highlight moves at about 180 words a minute, as it would with narration. One word at a time has its own speed control and ignores both settings.

Borrowed

1. One word at a time

Borrowed from speed-reading tools such as Spritz and Kindle Word Runner, which flash one word at a time at a chosen speed.

Try this

Press Start at 250 words a minute. Halfway through, try to look back at what the disciples said.

Makes easier

No eye movement and no lost place; it can feel fast and very focused for short, familiar text.

Costs

You cannot glance back, and readers reread 10–15% of the time; comprehension tends to drop. It also turns Scripture into a speed.

Ask your teamIs there any reading in your product that should be faster rather than slower?

The example contains Mark 4 only, in the Berean Standard Bible. Passage titles are our own editorial labels. Timing is simulated. Real implementations also need text size, contrast, screen-reader and reduced-motion testing. Switching options restarts the example from the same starting point.

What we noticed

Takeaways

  1. Phones invite shorter, more selective reading

    Screen reading involves more scanning, keyword spotting and selective reading, and less sustained reading (Liu). Comprehension on screens falls behind paper mainly under time pressure, not when people read at their own pace (Delgado et al.). Dyer found app readers completed more days of a plan, while men understood less than in print. Smaller units fit the sessions; they do not guarantee understanding.

  2. One word at a time removes looking back

    Readers look back at earlier words 10–15% of the time, and taking that away tends to reduce comprehension (Rayner et al.). For Scripture, which rewards rereading, it is the weakest fit; it also invites reading as a speed. If you offer it, keep it for short, familiar text, with a rewind.

  3. A smaller unit has a long devotional history

    Lectio divina reads a few verses slowly and repeatedly. A verse at a time, or a verse in focus, can support that kind of attention and memorisation, as long as the passage is one tap away. Verse numbers date from 1551; a verse was never meant to stand alone.

  4. Focus with context is the middle path

    A highlighted verse with the passage dimmed around it keeps attention and context together, and works best with audio: read-along highlighting helped children with dyslexia follow, and karaoke-style subtitles have supported literacy at scale. Let readers choose the window, as Immersive Reader does with one, three or five lines.

  5. Passage and chapter carry the argument

    A passage gives a reading its natural shape, the unit preachers and plans use, but its boundaries and titles are editorial. Reader’s editions such as the ESV Reader’s Bible remove numbers and headings so people read longer and follow the story. Make the longer mode calm and easy to enter, and keep the reader’s place across modes.

Use cases

Which reading, which unit?

People read Scripture for different reasons, sometimes in the same week. Each reason fits some points on the spectrum better than others.

How well each option fits each reading
ReadingNeeds1 One word at a time2 One verse at a time3 One verse in focus4 One passage5 Whole chapter
Finding or checking a verseThe verse, in its passagePoor fitPossiblePossibleGood fitGood fit
Skimming for a themeHeadings and boundaries to jump betweenPoor fitPoor fitPoor fitPossibleGood fit
A daily reading or devotionalA clear beginning and endPoor fitPossiblePossibleGood fitPossible
Meditation and lectio divinaSlowness, repetition, room to pausePoor fitGood fitGood fitPossiblePoor fit
Memorising a verseRecall, not rereadingPossibleGood fitPossiblePoor fitPoor fit
Listening alongText that follows the voice, with pausePoor fitPossibleGood fitGood fitPossible
Study or preparing to teachContext, cross-reference, notesPoor fitPoor fitPossibleGood fitGood fit
Reading a book throughContinuity and a kept placePoor fitPoor fitPoor fitPossibleGood fit

Editorial judgments drawing on the research below, not test results.

The research behind it

Theology, practice and science

Scripture and tradition

How the church has read

  • Read aloud, together, and whole

    Israel heard the law read publicly: “they read from the Book of the Law of God, explaining it and giving insight” (Nehemiah 8:8). Paul’s letters were read aloud to whole congregations, “after this letter has been read among you” (Colossians 4:16), and Timothy is told, “devote yourself to the public reading of Scripture” (1 Timothy 4:13). For most of Christian history, Scripture was heard in continuous portions.

  • Silent, private reading came later

    Augustine was struck that Ambrose read with his eyes on the page and his voice silent. Personal reading spread with literacy, printing and vernacular Bibles. A phone continues that private line, and can also reconnect people with reading aloud and together.

    Translation and commentary at Sententiae Antiquae

  • Small units for prayer and memory

    “I have hidden Your word in my heart” (Psalm 119:11). Lectio divina dwells on a few verses read slowly and repeatedly; memorisation works verse by verse. Small units are not a modern shortcut; they have their own devotional history.

    University of St Andrews, School of Divinity

  • Context guards meaning

    Chapter divisions date from the thirteenth century and verse numbers from 1551. Fee and Stuart’s principle, that a text cannot mean what it could never have meant for its first readers, depends on reading a verse within its passage, book and genre.

    Zondervan, 4th edition 2014 (quotations listing)

Digital reading today

What people actually do

  • Most Bible reading is now on screens

    Two-thirds of US Bible users access the Bible digitally. YouVersion reports over a billion installs and named Isaiah 41:10 its most engaged-with verse of 2025, the fourth time in six years: much digital engagement happens one verse at a time.

    American Bible SocietyChurchLeaders, reporting YouVersion

  • Screen reading is more selective

    People report more browsing, scanning, keyword spotting and one-time reading on screens, and less concentrated reading (Liu). Hutchings shows Bible apps are designed to train particular reading habits.

    Ziming LiuTim Hutchings

  • Completion is not comprehension

    In Dyer’s church study, app readers finished about two more days of a ten-day plan than print readers, while men understood less on screen. A unit that is easy to finish may not be the one that is understood.

    John Dyer

Reading science

Different readings, different needs

  • Normal reading is about 240 words a minute

    Adults read non-fiction at about 238 words a minute, most between 175 and 300. The storm on the sea takes about a minute to read: short enough for any morning.

    Marc Brysbaert

  • Skimming finds, deep reading understands

    Skimmers jump ahead once a section stops paying off; they catch the main points but understand less. Speed-reading displays remove the looking back that comprehension relies on.

    Duggan and PayneRayner, Schotter, Masson, Potter and Treiman

  • Listening is reading too

    One study found no difference in comprehension between reading, listening, and doing both. Read-along modes serve people who listen as much as people who read.

    Rogowsky, Calhoun and TallalInternational Journal of Emerging Technologies in Learning

  • Memory grows by recall

    Students who practised recalling a passage remembered 61% a week later; those who reread it remembered 40%. A verse-at-a-time mode for memorisation should ask, not just show.

    Roediger and Karpicke

  • Pace matters more than medium

    Screens fall behind paper mainly when people read under time pressure. Let readers set the pace.

    Delgado, Vargas, Ackerman and Salmerón

Accessible reading

Best practice

  • Anything that moves needs a pause

    Content that moves or updates for more than five seconds needs a way to pause, stop or hide it: auto-advancing verses, read-along and word-by-word display all qualify.

    W3C

  • Measure, spacing and size

    Aim for lines under 80 characters, line spacing of at least 1.5, unjustified text and resizing to 200% without sideways scrolling.

    W3C

  • Let readers choose the window

    Immersive Reader lets people focus on one, three or five lines. Offer the size of the focus as a setting, and respect reduced motion.

    Microsoft

Every source, with what it can and cannot show, is listed under Go further → Sources and their limits.

Where to start

Which fits your product?

These are editorial judgments from design review, not results of user testing.

In real apps

Examples in use

Attributed screenshots with dates and review limits. A screenshot shows an implementation; it does not show that it works for every audience.

Explore the growing app-example collection

Theological reflection

What is this practice for?

What attention is for

Mary “sat at the Lord’s feet listening to His message” (Luke 10:39), and Jesus said she had chosen the good part. Lectio divina dwells on a few verses slowly; reading a whole letter at once shows its argument. Both are forms of attention, and attention is a form of love.

Where Christians differ

Devotional traditions favour short passages for meditation and memory. Biblical scholars and many teachers urge reading whole books, warning that verse numbers invite reading sentences apart from their context. Silent private reading, which Augustine found remarkable in Ambrose, is itself a later development beside public reading aloud.

What follows for design

The question is not which unit is more spiritual, but whether the screen keeps a verse connected to its passage and leaves the reader’s attention free. Design for the reader to finish, put the phone down and live what they read (James 1:22).

In conversation with

Scripture is quoted from the Berean Standard Bible. This reflection is the editor’s, written from within the Christian tradition and open to correction. How we approach theology here →

Three ways to build

What would each way do here?

The three ways are Praxis’s frame for redemptive entrepreneurship; their application here is ours. Why we use it, and its limits →

Take into your next review

What unit of Scripture does this screen ask someone to hold in mind, and how do they reach the rest?

Exercise

Ask two people to read Mark 4:35–41 in different modes, then retell it and say what Jesus was doing just before. Time how long it takes each to find the verse before 4:35. Repeat with a screen reader and with reduced motion switched on.

Choose the unit that helps someone hear the word, not the one that helps them finish.

Record the decision with the worksheet →

Something missing or wrong here? Send a correction or suggest a topic.

Details

Go further

This deep dive brings together 1 earlier patterns. Their guidance, wireframes and sources are kept below; their old addresses lead here.

Edge cases to design for

Decide which reading this screen serves. For meditation or memory, show a verse at a time or a verse in focus with the passage dimmed around it. For listening, move the focus with the audio. For a daily reading, show one passage with its reference, what comes before and after, and a way into the chapter. For a book read through, offer calm long-form text. Keep the same place when someone changes mode, and never strand a verse without a route to its context.

What tends to go wrong

A verse shown alone with no way to its chapter; editorial headings presented as Scripture; word-by-word display used for study; auto-advancing text with no pause or rewind; focus modes that hide the text from screen readers; losing the reader’s place when switching modes.

How to test it

Ask people to read the same passage in two modes, then retell it and answer a question that depends on the verse before. Time how long it takes to find the context of a single verse. Test focus and read-along with screen readers, reduced motion and people with dyslexia or attention difficulties.

Earlier pattern: A bounded passage with a route to wider context

Choose the reading unit by the task while keeping its boundaries and context visible.

Guidance

Present the full chosen passage, its reference and edition. Explain editorial headings and passage boundaries. Offer preceding and following context and continuous reading without losing the original selection.

What tends to go wrong

Clipping a passage without notice; treating one boundary as universal across editions; replacing source text with an AI summary; making context available only through chat.

How to test it

Compare focused and continuous layouts for orientation, comprehension, voluntary rereading and context access. Include poetry and passages crossing chapter boundaries.

Earlier wireframe comparison for A bounded passage with a route to wider context
Earlier wireframe comparison, kept for reference.

Sources

Sources and their limits

Research-informed design proposal. Editorial review, not user validation.

Faith and interpretation

Verse numbers date from the sixteenth century and chapter divisions from the thirteenth; neither is part of the inspired text, and both make it easy to read a sentence apart from its argument. Smaller units also have a long devotional history: lectio divina dwells on a few verses read slowly and repeatedly. The question is not which unit is more spiritual, but whether the screen keeps the verse connected to the passage it belongs to.