Pattern 17
The player works without the screen
Support listening as a complete mode of use.
Concrete takeaway
Make current passage, playback, interruption and resumption available through suitable device and accessibility controls.
Choose an approach
These are editorial decision conditions to validate. Some alternatives are successive states or can be combined; they are not always exclusive choices.
| Alternative | Use when | Tradeoff or requirement |
|---|---|---|
| A · Listening player | Listening is the primary activity | The screen still needs clear edition and position |
| B · Screen-free controls | The user is screen-free | Device controls may expose fewer settings |
| C · Resume in text | Listening leads back to reading | Playback and reading positions must not be conflated |
The problem
An audio Bible may depend on a visual reader for basic navigation and lose usefulness when the device is locked.
The pattern
Make current passage, playback, interruption and resumption available through suitable device and accessibility controls. Offer speed and sleep options where supported. Preserve the last listening position and a route into reading.
Compare the alternatives
Support listening as a complete mode of use.
A · Listening player
The essential actions fit a listening task.
B · Screen-free controls
The device surface retains passage identity.
C · Resume in text
Listening and reading share a reliable anchor.
Original wireframe proposals · No live controls · Grey rows represent schematic text, not loading states · Labelled placeholders are not Scripture quotations
Download this wireframe as SVGFailure modes
Voice-only stopping; a hidden player; resuming at the wrong chapter; treating listening as microphone consent.
What to validate
Test lock-screen use, interruptions, headphones, connectivity loss and switching to text. Confirm what the selected edition actually supports.
Research-informed design proposal. These visual alternatives have not been tested with users in this atlas. Source findings, documented behaviour and this proposed adaptation are different kinds of evidence.
Sources and adaptation
This card is an original design synthesis. The following sources inform its content distinctions, interaction approach or review requirements; they do not validate the whole pattern.
- Android Audio BibleOfficial help article reviewed · Documented behaviour; no direct product usability audit performed.
- Designing Audio AI People Actually TrustArticle reviewed · The author scopes this to responsible audio AI, not a complete conversational-agent guideline.
- 8 voice AI UX patternsArticle reviewed · A design analysis rather than a clinical or Bible-app validation study. The original short link leads through another Friedman post.
Common scenarios and flows
- Listen, pause narration and repeat — Create a bounded listening-and-reflection session.
- Listen to an AI overview and inspect a claim — Use explanatory audio while retaining access to the source material and control of the session.
Examples in use
Attributed app evidence with dates and review limits. A screenshot illustrates an implementation; it does not establish that the proposal works for every audience.
Design principles in this decision
Editorial application of Missional by Design. These values frame review questions; they do not validate a pattern’s effectiveness.
- Hospitality — Who can use this approach in their actual context, and what complete alternative exists for someone who cannot?
Compare alternatives using the task and evidence above. Record competing needs instead of treating a principle as an automatic verdict.