Finding passages

On the reading page, the label at the top already makes promises. A single “Mark 3 · KJV” control is the most compact, but people have to guess what tapping it changes. Separate reference and translation controls make two frequent actions distinct: changing the edition should keep the passage, and changing the passage should keep the edition. Separate book, chapter and translation controls give the fastest access to a known level, as long as long book names don’t squeeze the targets.

Some readers hide navigation behind a gesture to keep the page quiet, as Mere Bible’s chapter rail does. That needs a visible, accessible way to open it as well. A bounded passage with a quiet “Read in context” link is a legitimate choice too, when the task is one reflection rather than open reading.

A chapter grid is one step in a longer path: know where you are, choose a route, pick a destination, open it, and be able to get back. A chapter control should skip choosing the book again; cancelling should leave the reader exactly where it was. “Back to where I was” and “Previous chapter” are different actions and deserve different controls.

Verses are optional precision. Don’t require a verse to open a chapter, but when someone does choose one, open the chapter at that verse and mark it briefly, so they can see where they have landed.

One search field can filter book names, recognise a typed reference and suggest passages with AI. These can share an input, but they are different kinds of answer: a recognised reference is a destination, and an AI suggestion is a proposal. Label results by what they are, and only promise text search if the product actually searches the text.

The trigger matters. In the Video Study Bible prototype, book filtering is instant and local, a complete reference resolves locally, and other input asks the AI for suggestions after a short pause, so even a half-typed book name leaves the device. Automatic suggestions save a step but add latency, cost and privacy questions; an explicit “Find related passages” action gives people more control. Either way, keep local results useful offline and don’t let a slow answer replace what the person is now typing.

Start from the chosen edition’s actual books and order. Not every Bible has the same 66 books, and the same position in a list is not the same book in another edition. Edition order supports familiarity; alphabetical order helps find a known name but changes with language; genre groups can help exploration if the headings explain the classification. Colour can reinforce a group label, never replace it.

When someone switches edition, keep the book and reference wherever a valid mapping exists. If the book or verse is missing or numbered differently, say so and offer a clear destination rather than silently opening whatever sits at the same index.