Moving through the text

Feeds, cards and stories

How should a reader move from one verse to the next?

A growing number of Bible apps borrow the vertical feed from TikTok and Instagram: one verse per full-screen card, a swipe up to the next, sometimes with a background, likes and a share button. Some go through the Bible in order; others shuffle verses chosen for you and never end. Others offer a small daily set of stories, or pages to turn like a book. The question here is not how much text a screen shows, but how the reader gets from one verse to the next, how far each verse stays from its setting, and where the reading ends. A feed can help a new reader begin. It can also turn the Bible into one more thing to scroll.

The spectrum

From a page you turn to a feed that never ends

  1. 1The pageFamiliar convention The story stays whole Long on a phoneTry it →
  2. 2Pages to turnFamiliar convention A place and an end Breaks mid-thoughtTry it →
  3. 3Cards in orderObserved One verse, then a clear end Context a tap awayTry it →
  4. 4A daily set of storiesObserved Small and finished Someone else choseTry it →
  5. 5A feed in order, without endObserved Reads on easily No end to stop atTry it →
  6. 6A shuffled, endless feedWarning case Effortless and familiar Out of context, endlessTry it →

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

Try it

Try six ways to move through the storm on the sea

Someone opens Mark 4 at the storm on the sea (4:35–41) in the Berean Standard Bible, with a few minutes to spare. Move through the passage in each design with the buttons, the arrow keys or a swipe. Watch what happens after Mark 4:41, the last verse of the chapter, and open the verses around a card.

Prototype controls

Option

The verses around a cardNot used here
On each cardNot used here
Advance on its ownNot used here
Why these settings?

Every view moves with Previous and Next, with the arrow keys and with a swipe, so nobody needs a gesture to read; each card is announced to screen readers with its position, and with reduced motion switched on nothing slides. “The verses around a card” opens the passage the card belongs to, with its verse marked. The shuffled feed always shows likes and shares, as the feeds it stands for do; the counts are written for this example. Stories that advance on their own move every six seconds and can be paused.

Familiar convention

1. The page

A familiar convention in Bible apps and e-books: the chapter as one continuous text, opened where the reader stopped. Section titles here are our own.

Try this

Scroll up to the parable before the storm, then down to the end of the chapter.

Makes easier

The story and the argument stay whole, and the context is simply there, above and below.

Costs

Long on a phone, and a reader can lose their place; it asks for more attention to begin.

Ask your teamDo your readers mostly read through, or dip in?

The example contains Mark 4, the start of Mark 5 and a few verses from other books in the Berean Standard Bible. The order of the shuffled feed, the like and comment counts, the story question and the end cards were written for this example; no app is copied. Nothing is sent, liked or shared. Switching options restarts the example from the same starting point.

Design considerations

Takeaways

  1. Let the text set the order

    Cards in the order of the text keep a story and an argument together, one step at a time. A shuffled feed sets each verse beside whatever comes next, chosen by popularity or by what you liked. Some verses survive that; others, read without the verse before, say something the passage does not.

    Scripture and harm →
  2. Give the reading an end

    Show the position (“card three of seven”) and end with the passage or the chapter: an end card that names what was read, offers to read it again or see the whole passage, and plays nothing next. People leave an endless feed only when life interrupts; a reading can let them go.

    Make room for rest →
  3. Keep the context one tap away

    Every card needs a route to the verses around it and to the chapter, as short as the swipe to the next card. Mark the card’s verse in the passage, and say where a verse comes from when it is out of order. A card is also a decision about how much text is shown.

    How much text at once →
  4. Keep counts off the text

    Likes, comment counts and trending numbers turn a verse into content and make some verses winners. If people may respond, let them save, note or share the passage, and leave popularity out of the reading view.

    Comments on verses →
  5. Every swipe needs a button

    Give Previous and Next buttons and keys for every gesture, announce each card with its position, honour reduced motion, and pause anything that advances on its own. A feed that only moves by swiping shuts out people who cannot swipe.

  6. Cards can be a welcome

    For a new reader, someone with little time or someone who finds long text hard, one verse at a time in order can be the easiest way in. Make it a door into the passage, and make the page or pages to turn one tap away when they want more.

    First use →

Use cases

Which reader, which movement?

People come to the text with different time, attention and purposes, sometimes in the same week. Each fits some movements better than others.

How well each option fits each reader
ReaderNeeds1 The page2 Pages to turn3 Cards in order4 A daily set of stories5 A feed in order, without end6 A shuffled, endless feed
Reading a chapter or a book throughThe story whole, and a kept placeGood fitGood fitPossiblePoor fitPossiblePoor fit
A few minutes on the trainAn easy start and a clear endPossibleGood fitGood fitGood fitPossiblePoor fit
New to the Bible, or reading littleOne thing at a time, and the story around itPossiblePossibleGood fitGood fitPossiblePoor fit
Finds long text hard (attention, dyslexia, literacy)Short units, own pace, no timerPoor fitPossibleGood fitPossiblePossiblePoor fit
Meditation, or memorising a verseSlowness, and the passage close byPossiblePossibleGood fitPossiblePoor fitPoor fit
Study, or preparing to teachContext, references and the argumentGood fitPossiblePoor fitPoor fitPoor fitPoor fit
Uses a screen reader, switch or keyboardButtons, headings and a known positionGood fitGood fitGood fitPossiblePossiblePoor fit

Suggested fits based on the research below. Test these choices with people in your context.

The research behind it

Theology, practice and science

Scripture and tradition

Reading in order, and in context

  • “It is also written”

    When the devil tempted Jesus, he quoted a psalm without its setting: “For it is written: ‘He will command His angels concerning You’” (Matthew 4:6). Jesus answered with more of Scripture: “It is also written: ‘Do not put the Lord your God to the test’” (Matthew 4:7). A verse alone can be made to say what the whole does not.

  • The whole story

    On the road to Emmaus, “beginning with Moses and all the Prophets, He explained to them what was written in all the Scriptures about Himself” (Luke 24:27). Israel heard the law read and explained, “so that the people could understand what was being read” (Nehemiah 8:8).

  • Reading needs a guide

    Philip asked the Ethiopian official, “Do you understand what you are reading?”, and he answered, “How can I … unless someone guides me?” (Acts 8:30–31). A card that ends a verse and offers the next one is not yet a guide.

  • Slow reading has a long history

    The blessed person meditates on God’s law “day and night” (Psalm 1:2), and lectio divina dwells on a few verses read slowly and repeatedly. One verse at a time is not new; reading it quickly, and moving on, is.

    University of St Andrews, School of Divinity

  • Read the paragraph

    Greg Koukl’s rule of thumb: “Never read a Bible verse. … Instead, always read a paragraph at least”, because “Meaning always flows from the top down, from the larger units to the smaller units”.

    Greg Koukl

Products

What Bible apps do now

  • In order, without end

    Holy Scroll describes “verse-by-verse infinite scroll. Just like your Instagram feed, just like TikTok”: “You look up twenty minutes later and you’ve read three chapters without trying.” Scroll The Bible’s main feed is “a smooth, full-screen, vertical scroll through every book and chapter of the Bible”; HolyScroller is “like TikTok, but for your soul”.

    Discipleship Tech, Inc.Gabriel JacobsonPeter Thomas Hughes

  • Shuffled, and endless

    Scroll The Bible’s Discover page “is a feed of random Bible verses”: “Just keep scrolling.” Verity offers daily verses “through an engaging, infinite scroll experience—like your favorite social apps, but for your spiritual growth”, and Verses: Daily Bible asks people to “Swipe through” a feed of single verses, with a random mode.

    Gabriel JacobsonLouis DerrienWeiyanda (Shanghai) Information Technology Co., Ltd.

  • Daily sets with an end

    In YouVersion, “Swipe up or down to navigate through the sections of Guided Scripture”; “Complete all the slides to reach this page”, where the daily streak is counted. Its Verse of the Day links to “the full chapter the verse is found in”, and “You can heart, comment on, or share the verse of the day”. Glorify shows a short passage one verse per screen under a step bar.

    YouVersion SupportChristian FMGlorify

  • Where people meet the Bible now

    The editor’s Kairos paper reports from NRB and Barna that among younger people “Nearly a quarter engage with biblical content on TikTok”, and calls a verse of the day “Often underestimated, despite its role in everyday formation”. Many will meet Scripture in a feed whatever Bible apps do.

    Tobias Treppmann

Research

Attention, and the place to stop

  • Infinite scroll removes the stop

    Aza Raskin, who designed infinite scroll, later said: “If you don’t give your brain time to catch up with your impulses … you just keep scrolling.”

    Hilary Andersson

  • Caught in a loop

    Infinite scrolling “has been reported to make users feel like they are being caught in a loop, regretfully elongating SM sessions”. In a week-long field study, “most reasons to break SM sessions were not related to the app but the user’s general context”: people stop when life interrupts.

    Jan Ole Rixen and colleagues (Ulm University, TU Darmstadt)

  • Short video and attention

    A meta-analysis of 71 studies with 98,299 participants found that heavier short-form video use was “most consistently linked to poorer attention span and reduced inhibitory control”; “The majority of the studies analyzed were cross-sectional”, so cause is not shown. In a lab study, switching between short videos made people worse at remembering what they had meant to do.

    PsyPostFrancesco Chiossi, Luke Haliburton, Changkun Ou, Andreas Butz and Albrecht Schmidt (LMU Munich)

  • A decision to go on

    Even TikTok gives teenagers a daily limit and asks for a passcode to continue, “requiring them to make an active decision to extend that time”. The end of a passage is a gentler point of decision.

    TikTok Newsroom

  • Constraint forms

    The Kairos paper: “Every historic formation practice works through chosen constraint, not infinite access.” And of the hurried reader: “Someone reading five fragmented minutes on the train isn’t failing spiritually.”

    Tobias Treppmann

Accessible reading

Best practice

  • A button for every swipe

    “Not everyone can perform complex and multi-touch gestures”: “Provide single-point operation for all functions”, and “Don’t rely on dragging for user actions.”

    Web Accessibility InitiativeWeb Accessibility Initiative

  • A feed screen readers can follow

    A feed is “a dynamic list of articles that often appears to scroll infinitely”; marked up as one, it lets screen reader users “jump forward and backward by article” and know where they are.

    Web Accessibility Initiative

  • Motion the reader controls

    “Support user preferences for motion, and eliminate unnecessary motion effects.” Stories or verses that advance on their own need a pause.

    Web Accessibility Initiative

Find the supporting research under Go further → Sources and their limits.

Where to start

Which fits your product?

Suggested fits based on the research on this page. Test these choices with people in your context.

Trade-offs to hold

Pulls against

Some choices here pull against choices in another deep dive. Each pair below says what pulls and one way to hold both.

See every place the deep dives pull against each other →

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 a feed cannot give

“Why spend money on that which is not bread, and your labor on that which does not satisfy? Listen carefully to Me, and eat what is good” (Isaiah 55:2). A feed promises that the next card will be the one, and so there is always a next card. Scripture is a story with a beginning and an end, told so that we may know the One who speaks in it; the disciples’ question at the end of the storm, “Who is this, that even the wind and the sea obey Him?” (Mark 4:41), is meant to be sat with, not swiped past.

Where Christians differ

Churches have always read Scripture in more than one measure: whole books read aloud in worship, appointed passages in a lectionary, single verses memorised, sung and prayed. Some traditions treasure a verse for the day; others warn that verse numbers, added in the sixteenth century, teach people to read sentences apart from their argument. Many would agree that a verse is safest in the company of the passage it belongs to, and of people who read it together.

What follows for design

The Bereans “examined the Scriptures every day to see if these teachings were true” (Acts 17:11): daily, and with the whole in view. Let the movement through the text serve that: in its own order, with the setting a tap away, at the reader’s pace, and with an end where the reader can put the phone down and live what they read.

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

How does a reader get from one verse to the next here, how far is each verse from its context, and where does the reading end?

Exercise

Read Mark 4:35–41 in your product as cards and as a page with two people, then ask each to retell it and say what Jesus was doing just before. Time how long it takes to reach the verses around a card and to find where the reading ends. Then scroll your feed for ten minutes and list every card that means something different without the verse before it. Finally, try every view with a screen reader, a keyboard and reduced motion.

Let the text set the order and the end, and give every reader a place to stop.

Record the decision with the worksheet →

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

Details

Go further

Edge cases to design for

Choose the movement for the reading. A chapter read through is best as one page or as pages to turn. For a new reader or a few minutes on the train, cards can carry one verse at a time, in the order of the text, with the verses around each card one tap away, a visible position (“card three of seven”) and an end card when the passage or chapter ends that names what was read and plays nothing next. A small daily set of stories can work the same way. If verses appear out of order, say where each comes from and show its setting. Give every gesture a button and a key, announce each card to screen readers, honour reduced motion, and give anything that advances on its own a pause.

What tends to go wrong

A feed that runs from Mark 4:41 straight into a shuffled verse from another book; “Wives, submit to your husbands” on a card with a heart count and no verse before it; no end card, no position and no way back to the chapter; music and backgrounds that start on their own; a like count on Scripture; a streak that counts swipes; stories that advance on a timer with no pause; a swipe-only interface with no buttons; the next card loading while a screen reader is still reading this one.

How to test it

Ask people to read Mark 4:35–41 as cards and as a page, then retell it and say what Jesus was doing just before. Time how long it takes to reach a card’s context and to find the end of a session. Count how many cards people swipe past without reading. Give a shuffled feed to someone who knows the Bible well and ask which cards mean something different in their setting. Test every view with VoiceOver and TalkBack, a switch or keyboard, and reduced motion.

Sources and their limits

Research-informed design proposal · draft for review. Original prototypes await user testing.

Faith and interpretation

When the devil tempted Jesus, he quoted Scripture without its setting: “For it is written: ‘He will command His angels concerning You’” (Matthew 4:6). Jesus answered with more of it: “It is also written: ‘Do not put the Lord your God to the test’” (Matthew 4:7). Verse numbers were added in the sixteenth century to help readers find their way, not to make each sentence a separate saying. A card can serve slow attention, as lectio divina does with a few verses; it serves badly when it cuts a verse loose from the story and the argument it belongs to.