Patterns Reading the BibleFinding a passage

Finding a passage

Browse, type a reference, or start from a need?

Someone hears “John 3” in a sermon. Someone else wants Isaiah but isn’t sure where it sits. A third person only wants today’s reading. One picker rarely serves all three, and sometimes the best picker is none at all. Opening the right page for someone is a small hospitality, and the first step of every reading.

5 working options
59 app screens
5 takeaways
Prototypes awaiting user testing

At a glance

Five routes to a passage, side by side

1
Step by step
Familiar convention
- One question per screen
- Many taps for a known reference
2
Expandable book list
Observed
- Book context stays in view
- Long books push the list down
3
Type a reference
Borrowed
- Fastest for a known reference
- Needs the reference and spelling
4
Start from a feeling
Observed
- A way in without a reference
- Someone else chose the verses
5
No passage picker
Leave it out
- Nothing to decide before reading
- Other passages are out of reach

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

Try it

Try five ways to reach a passage

Someone is reading Mark 3. A friend mentions John 3 and they want to look it up. Every example starts at Mark 3 in the Berean Standard Bible. Try reaching John 3, then change your mind and cancel.

Prototype controls

Option

OpeningNot used here

Open on tapReview, then open

Book listNot used here

ListGrid

Go as far asNot used here

ChapterVerse

Why these settings?

These switches are separate decisions from the options. Opening on tap is faster; reviewing first helps when a mis-tap is costly or the destination is unfamiliar. A book grid fits all 66 books in one view, with no scrolling, at the cost of recognisability: it shows three-character codes (here the USFM identifiers), which suit people who already know the books. A contributed Olive Tree screenshot (undated, captured before May 2026) shows the same idea as a nine-column grid of three-letter codes. A verse step suits study and sermon follow-along, but adds a screen for anyone reading a whole chapter.

Familiar convention

1. Step by step

A widely used structure, generalized here. Not a copy of a particular app.

Try this

Tap “Mark 3”, choose John, then chapter 3. Then switch on the book grid and the verse step and try again.

Makes easier

Each screen asks one question, with large targets. Readers who recognise a book name but do not remember a reference can always get there.

Costs

Several screens for a destination the person already knows. Sixty-six books make a long list; a grid is shorter but relies on abbreviations.

Ask your teamDo most of your readers know where they are going, or are they finding out?

Design considerations

Takeaways

It depends on what the reader already knows
Typing is fastest when the reference is in front of someone, and a wall when it isn’t. Browsing takes more taps but never asks anyone to remember. The expandable list sits between the two: the shape of the book stays in view while you choose.
Leaving it out is a real option
If your product guides people through a plan, a full picker is an exit as much as a feature. Leaving it out keeps the session calm and the scope honest. It also sends someone following a sermon to another app.
A feeling asks a different question
Not “where is it?” but “where should I begin?”. ESV and Glorify both offer it. It welcomes someone with no reference in mind, and hands quiet authority to whoever wrote the lists. Name the curators, open passages in their chapter, and keep acute distress out of a verse menu.
Open on tap; review only when it costs something
Opening on tap is what most people expect. A review step earns its place when a wrong destination is costly, such as changing a group’s shared reading. Going down to the verse helps someone following a sermon and slows down someone reading whole chapters.
Offer both routes, and keep each one plain
Most general Bible readers end up with browsing and typed entry. That works while each route says what it does. A reference field that quietly becomes text search or an AI answer box changes what people expect from it.

Use cases

Which situation, which option?

People come with different needs, sometimes in the same week. Each need fits some options better than others.

How well each option fits each situation
Situation	Needs	1 Step by step	2 Expandable book list	3 Type a reference	4 Start from a feeling	5 No passage picker
Following a sermon or talk	A spoken reference, found before the speaker moves on	Possible	Possible	Good fit	Poor fit	Poor fit
New to the Bible	Seeing which books exist and where, without typing	Good fit	Good fit	Poor fit	Possible	Poor fit
Studying across books	Jumping between references quickly	Poor fit	Possible	Good fit	Poor fit	Poor fit
Carrying on with a book	The saved place, then the next chapter	Possible	Possible	Possible	Poor fit	Good fit
Looking for comfort, with no reference in mind	A place to begin, with its chapter around it	Poor fit	Poor fit	Poor fit	Good fit	Poor fit
A guided plan or group session	Today’s passage without detours	Poor fit	Poor fit	Poor fit	Poor fit	Good fit
Screen readers, large text or limited dexterity	Few, large targets and one decision at a time	Good fit	Possible	Good fit	Possible	Good 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

Finding the place

Finding the place is an old practice
In Nazareth, “the scroll of the prophet Isaiah was handed to Him. Unrolling it, He found the place where it was written” (Luke 4:17). Before chapters and verses, passages were named by what happened in them: “have you not read about the burning bush in the Book of Moses?” (Mark 12:26). Chapters date from the thirteenth century and verse numbers from 1551.
Easy access is a stated commitment
The Second Vatican Council asked that “easy access to Sacred Scripture should be provided for all the Christian faithful”. Protestant Bible societies have pursued the same goal through translation and distribution. A picker is where that access succeeds or fails on a phone.
Second Vatican Council

How people arrive

Lookup, suggestion and habit

People reach Scripture in several ways
Lifeway’s 2024 survey finds looking up passages, reading ones suggested by others, rereading favourites and reading systematically overlap in the same people. One route will not serve all of them.
Lifeway Research
Apps teach a way of reading
Hutchings shows Bible apps are designed as persuasive technologies that train reading habits. By the same logic, a picker that always opens at a verse teaches verse reading, and one that opens at a chapter teaches passages.
Tim Hutchings
Reading on needs no picker
YouVersion documents continuous chapter scrolling and an optional verse picker: for people reading on, the next chapter matters more than a destination.
YouVersion Support

Interface research

What helps people find

Recognition is easier than recall
Interfaces that show the options ask less of memory than fields that need someone to remember and type. Browsing books and chapters asks people to recognise; a reference field asks them to recall. Offer both.
Raluca Budiu
Forgive the way people type
When input is wrong and a correction is known, suggest it. Accept abbreviations, other languages’ book names and “Psalm” for “Psalms”, and say “Did you mean John 3?” instead of “Not found”.
W3C USFM documentation
Many small targets
A grid of 150 Psalms or 176 verses packs many targets into a phone screen. Keep each at least 24 pixels with space between, and let the grid reflow when text is enlarged.
W3C W3C WAI

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

Where to start

Which fits your product?

IfPeople follow references from a speaker, a book or a study guide
Start withA typed reference, with browsing as the fallback
IfPeople are new to the Bible, or think in books rather than references
Start withStep by step, or the expandable list
IfPeople arrive with a need rather than a reference
Start withStart from a feeling, with named curators and the whole chapter one step away
IfYour product is a guided plan, devotional or group session
Start withConsider no picker, with a clear route to a full Bible elsewhere

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

In real apps

Examples in real apps

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

Annotated examples

YouVersion · Desktop web

Continuous prose with reader controls

Direct web capture · cropped

Mere Bible (formerly NeuBible) · Mobile interface · device and OS not independently verified

Chapter navigation beside the reading text

User-contributed screenshot · unedited

Mere Bible (formerly NeuBible) · Mobile interface · device and OS not independently verified

Book list with an inline chapter grid

User-contributed screenshot · unedited