[ { "id": "03", "slug": "footnotes", "title": "Footnotes without losing place", "topic": "reading", "summary": "Inspect a note and return to the exact reading anchor.", "problem": "Opening a note can displace the passage, cover it or return the reader to the top of a chapter.", "solution": "Attach the note to its text anchor and preserve its parts: origin reference, quoted phrase, explanatory text and alternative reading where supplied. Choose inline expansion, a mobile sheet or a study panel by note length and available space.", "failure": "Hover-only access; a modal with no usable close control; merging quoted wording and editorial explanation; closing to a different reading position.", "test": "Test opening and closing with touch, keyboard and screen reader at large text sizes. Confirm focus and the visible reading position return to the note anchor.", "sources": [ "footnote", "dialog" ], "variants": [ { "title": "A · Inline expansion", "caption": "Useful for a short note; check how expansion shifts the passage.", "items": [ "tag|Mark 1:1 · Note a", "card|Passage paragraph|The note marker is attached to this text.", "notice|Note a|Quoted phrase and edition explanation.", "button|Collapse note" ], "when": "The note is brief and local", "tradeoff": "Expansion moves text below it" }, { "title": "B · Bottom sheet", "caption": "Keep the origin visible above a dismissible note.", "items": [ "tag|Mark 1:1 · Note a", "highlight|Origin text remains selected", "sheet|Edition footnote|Origin reference / Quoted phrase / Note text", "button|Close and return" ], "when": "Mobile space is limited and the note is longer", "tradeoff": "A sheet can cover the verse and needs focus return" }, { "title": "C · Study panel", "caption": "A longer note can sit alongside the text.", "items": [ "card|Main reader|Mark 1:1 remains the anchor.", "card|Study note|Edition, author and complete note.", "button|Return focus to the passage" ], "when": "Sustained study benefits from seeing both surfaces", "tradeoff": "A panel costs reading width and needs a visible anchor" } ], "faith": "Do not label translation footnotes as AI commentary. Publisher material and personal notes have different ownership and permissions.", "status": "Research-informed design proposal", "takeaway": "Attach the note to its text anchor and preserve its parts: origin reference, quoted phrase, explanatory text and alternative reading where supplied.", "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A reader wants an edition note without losing the passage.", "benefit": "A local preview can answer a small question without a separate reading journey.", "drawback": "Inline expansion moves text; a sheet can obscure the verse; a panel needs room.", "differences": "Quick checking benefits from a preview. Extended study may need both text and note visible. Large text and keyboard focus affect the best surface.", "question": "Can the reader identify whose note this is and return to its anchor?", "check": "Open a long note at large text size, follow a reference and return. Check scroll and keyboard focus." } }, { "id": "05", "slug": "text-structure", "title": "Editorial distinctions survive reflow", "topic": "reading", "summary": "Preserve poetry, headings and translation additions without forcing a rigid layout.", "problem": "Small screens and enlarged text can flatten meaningful structure or turn editorial headings into apparent verse content.", "solution": "Reflow paragraphs and preserve relative poetic structure. Distinguish section headings from Scripture. Explain translator-supplied words when the edition marks them. Verse navigation can coexist with continuous prose.", "failure": "Shrinking text to preserve a desktop layout; treating each verse as an unrelated box; calling translation additions AI-generated text.", "test": "Test narrow screens, enlarged fonts and spoken output. Can readers recognise a heading, poetic grouping and a translation addition without relying only on colour?", "sources": [ "add", "poetry", "usfm", "reflow" ], "variants": [ { "title": "A · Translation addition", "caption": "An explanation names the editorial role.", "items": [ "tag|Translation A", "highlight|Words marked by this edition", "notice|Translation addition|Words supplied by translators to clarify meaning.", "button|About this edition" ], "when": "The edition marks supplied translation wording", "tradeoff": "Explain the convention without cluttering every word" }, { "title": "B · Poetry", "caption": "Indentation follows meaning at larger text sizes.", "items": [ "tag|Poetic passage", "poem|First poetic line / Second related line / Next poetic line", "button|Increase text size" ], "when": "Line grouping contributes to poetic meaning", "tradeoff": "Indentation must survive narrow widths" }, { "title": "C · Continuous passage", "caption": "Headings and verse labels support, rather than fragment, reading.", "items": [ "tag|Editorial section heading", "heading|Passage title", "card|Continuous Scripture paragraph|Verse references remain navigable.", "button|Show verse labels" ], "when": "The goal is continuous reading", "tradeoff": "Verse labels must remain discoverable" } ], "faith": "Preserve the chosen edition’s conventions. A structure standard informs meaning; it does not prescribe one screen component.", "status": "Research-informed design proposal", "takeaway": "Reflow paragraphs and preserve relative poetic structure.", "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A reader encounters poetry, headings or words marked as supplied by translators.", "benefit": "Preserving meaningful distinctions helps readers understand the edition’s editorial choices.", "drawback": "Too many visual conventions can distract; too few can erase meaningful distinctions.", "differences": "Someone new to the edition may need a short explanation. Experienced readers may prefer less repeated help. Narrow screens still need meaningful indentation.", "question": "Is this distinction from the source, the publisher or our interface?", "check": "Review poetry, headings and translation additions at large text sizes. Ask readers to explain the distinction without guessing." } }, { "id": "08", "slug": "media-evidence", "title": "Original media before synthesis", "topic": "study", "summary": "Let readers inspect the source behind an explanation.", "problem": "A video excerpt or AI summary can sound convincing while hiding who said it and where the statement occurs.", "solution": "Use media cards with creator, original source, duration and relevant time range. Link supported claims to precise excerpts. Offer transcript and original context; playback starts deliberately and failure leaves the conversation readable.", "failure": "Autoplay; incorrect time windows; edited clips that reverse meaning; source opinions presented as consensus; a missing video hidden behind a confident synthesis.", "test": "Check whether every evidence claim is supported at the linked position. Test unavailable media, captions, returning from playback and the context before and after an excerpt.", "sources": [ "playground-citations", "shape", "audio-trust" ], "variants": [ { "title": "A · Original clip", "caption": "An explicit time range makes the evidence inspectable.", "items": [ "tag|Publisher · Video title", "video|Original excerpt · 02:10–03:05", "button|Play excerpt", "button|Open original context" ], "when": "The original clip is available", "tradeoff": "Playback takes time and needs accessible alternatives" }, { "title": "B · Evidence and explanation", "caption": "Source words and synthesis have different roles.", "items": [ "card|Source excerpt|Transcript with time reference.", "card|AI synthesis|Explanation linked to the excerpt.", "button|Check the claim" ], "when": "Explanation depends on a particular source", "tradeoff": "Separate the quotation from the synthesis" }, { "title": "C · Media unavailable", "caption": "The failure state does not erase the source identity.", "items": [ "notice|Video cannot be played here.", "card|Source record|Title, creator and original address.", "button|Read available transcript" ], "when": "Media cannot load or cannot be embedded", "tradeoff": "A link or transcript may be the only permitted alternative" } ], "faith": "This applies to sermons, teaching videos, podcasts and courses. Association with a verse is not proof of a particular interpretation.", "status": "Research-informed design proposal", "related": [ "ai-citations" ], "takeaway": "Use media cards with creator, original source, duration and relevant time range.", "principles": [ "word-distinct", "speak-for-god" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A reader wants to inspect a sermon, video or audio source.", "benefit": "Source metadata and a transcript allow inspection beyond a confident summary.", "drawback": "A short clip may distort its surrounding argument; timestamps can be wrong.", "differences": "Caption and transcript access matter for people who cannot hear or cannot play media in their current setting.", "question": "Would the surrounding material change how this excerpt is understood?", "check": "Check whether every evidence claim is supported at the linked position. Test unavailable media, captions, returning from playback and the context before and after an excerpt." } }, { "id": "11", "slug": "long-passages", "title": "Passage preview opens a full reader", "topic": "conversation", "summary": "Keep long Scripture readable without flooding the conversation.", "problem": "A full chapter inside a small chat card can create nested scrolling. Aggressive truncation can hide what the user asked to read.", "solution": "Choose among an excerpt card opening a full reader, complete inline expansion for manageable passages, and a dedicated reading surface for sustained reading. Name the requested range, edition and visible range. Inline expansion uses the main conversation scroll rather than a nested text scroll; provide Collapse and retain an anchor when collapsing. A full reader can be a sheet on small screens or a side panel on wider screens, with an explicit return to the same conversation place. For cross-chapter ranges, preserve every boundary and continuation. If complete text is requested, provide a clearly labelled route to it rather than silently summarising. If edition rights or availability prevent full display, explain the limit and offer a permitted destination.", "failure": "Unmarked omissions; two competing scroll regions; a summary presented as the original passage; returning to the top of the chat.", "test": "Test a short verse, long passage, complete chapter request and large text. Can readers recognise omissions, reach the whole text and return to the same conversation position? Test inline expansion and collapse, cross-chapter ranges, sheet and panel return, multiple passage cards, unavailable editions and the final verse at large text size.", "sources": [ "nng-chat", "playground-depth", "usfm", "diagram-psalm-kjv" ], "variants": [ { "title": "A · Passage preview", "caption": "Name exactly what is visible and what continues.", "items": [ "heading|Conversation", "chat|Read Psalm 23 alongside this question.", "quote|The LORD is my shepherd; I shall not want.|Psalm 23:1 · BSB · Preview", "links|Read all 6 verses", "composer|Ask a follow-up…|Add context" ], "when": "The passage supports a conversation", "tradeoff": "Excerpt boundaries and a full-text route are essential" }, { "title": "B · Dedicated reader", "caption": "A sustained reading task gets enough space.", "items": [ "heading|Psalm 23 · BSB", "links|Back to conversation", "psalm|all" ], "when": "The user wants sustained or complete reading", "tradeoff": "Moving surfaces requires conversation-position restoration" }, { "title": "C · Complete inline passage", "caption": "Suitable when the full text remains manageable in the main chat scroll.", "items": [ "heading|Conversation", "chat|Psalm 23 · BSB", "psalm|all", "links|Collapse passage" ], "when": "The complete passage remains manageable inline", "tradeoff": "Expansion and collapse must preserve the main scroll anchor" } ], "faith": "Choose preview thresholds by viewport, text size and passage structure. There is no universal verse count that solves overflow.", "status": "Research-informed design proposal", "related": [ "chat-content-objects", "reading-position", "readable-overflow" ], "purpose_lens": { "assumption": "A short answer may be easier to scan, but a short excerpt can hide the very context the person needs. The decision is how to make the requested text available without losing the conversation, not how to minimise every response.", "situations": [ [ "Keep a conversation moving", "Offer a labelled preview when the passage supports a wider discussion. Make its omitted range explicit and give the reader a direct route to the full request." ], [ "Read the whole passage now", "Use a dedicated reader or complete inline expansion. Test return position, large text and interruptions. Do not make the person repeatedly ask the assistant to reveal the next few verses." ] ], "question": "Does our brevity help the reader, or mainly make the chat look tidy?", "test": "Give someone a multi-verse request, ask them to inspect the entire passage and then return to their question. Verify the first and last requested verses, not just whether a card opened.", "guide": "purposes", "guide_label": "Choose by the person’s purpose", "sources": [] }, "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Alternatives", "screens": [ { "title": "Conversation", "annotation": "Mark the excerpt boundary and preserve a clear route to all requested verses.", "blocks": [ { "kind": "chat", "text": "Read Psalm 23 alongside this question.", "extra": "" }, { "kind": "quote", "text": "The LORD is my shepherd; I shall not want.", "extra": "Psalm 23:1 · BSB · Preview" }, { "kind": "links", "text": "Read all 6 verses", "extra": "" }, { "kind": "composer", "text": "Ask a follow-up…", "extra": "Add context" } ] }, { "title": "Psalm 23 · BSB", "annotation": "A dedicated reader gives the passage room. Returning should restore the conversation position. Diagram shows verses 1–3; the reader continues.", "blocks": [ { "kind": "links", "text": "Back to conversation", "extra": "" }, { "kind": "psalm", "text": "all", "extra": "" } ] }, { "title": "Conversation", "annotation": "An expanded passage uses the conversation’s main scroll, not a second scrollable box. Diagram shows the start of the expanded passage.", "blocks": [ { "kind": "chat", "text": "Psalm 23 · BSB", "extra": "" }, { "kind": "psalm", "text": "all", "extra": "" }, { "kind": "links", "text": "Collapse passage", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "takeaway": "Choose among an excerpt card opening a full reader, complete inline expansion for manageable passages, and a dedicated reading surface for sustained reading.", "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A conversation becomes a sustained reading task.", "benefit": "A preview protects conversation continuity while a reader provides room for the complete passage.", "drawback": "Preview thresholds can hide wanted text; inline expansion can move later messages.", "differences": "Large text and cross-chapter reading need more space than a short quotation. Preserve both reading and conversation position.", "question": "Can the person reach all the text they requested and return without losing place?", "check": "Test a short verse, long passage, complete chapter request and large text. Can readers recognise omissions, reach the whole text and return to the same conversation position? Test inline expansion and collapse, cross-chapter ranges, sheet and panel return, multiple passage cards, unavailable editions and the final verse at large text size." } }, { "id": "17", "slug": "audio-first", "title": "The player works without the screen", "topic": "audio", "summary": "Support listening as a complete mode of use.", "problem": "An audio Bible may depend on a visual reader for basic navigation and lose usefulness when the device is locked.", "solution": "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.", "failure": "Voice-only stopping; a hidden player; resuming at the wrong chapter; treating listening as microphone consent.", "test": "Test lock-screen use, interruptions, headphones, connectivity loss and switching to text. Confirm what the selected edition actually supports.", "sources": [ "youversion-audio", "audio-trust", "voice-patterns", "kairos-draft", "vatican-full-presence" ], "variants": [ { "title": "A · Listening player", "caption": "The essential actions fit a listening task.", "items": [ "heading|Psalm 23 · Audio", "label|BSB · Example recording", "player|00:18 / 01:10|Pause", "links|Speed 1× · Repeat: Off", "nav|Previous psalm / Next psalm" ], "when": "Listening is the primary activity", "tradeoff": "The screen still needs clear edition and position" }, { "title": "B · Screen-free controls", "caption": "The device surface retains passage identity.", "items": [ "heading|Device playback controls", "resource|Psalm 23|BSB · Example recording", "player|00:18 / 01:10|Pause" ], "when": "The user is screen-free", "tradeoff": "Device controls may expose fewer settings" }, { "title": "C · Resume in text", "caption": "Listening and reading share a reliable anchor.", "items": [ "heading|Continue with Psalm 23", "resource|Last heard: verse 2|BSB · 00:18 · Example recording", "button|Continue listening", "links|Read from verse 2" ], "when": "Listening leads back to reading", "tradeoff": "Playback and reading positions must not be conflated" } ], "faith": "", "status": "Research-informed design proposal", "purpose_lens": { "assumption": "Listening can be the whole intended encounter. A successful session need not produce a screen view, written reflection or another piece of content.", "situations": [ [ "Listen while moving", "Prioritise reliable playback, accessible controls and recovery from interruption. Do not require visual interaction to continue." ], [ "Dwell with one passage", "Make repeat, pause and a deliberate ending available. Explain the repeat boundary; avoid surprising the listener with an endless loop." ], [ "Listen and study", "Offer an optional route to the text and sources while preserving playback position. Keep reading position separate when the person explores elsewhere." ] ], "question": "Would putting down the phone fulfil this experience—and do our defaults allow it?", "test": "Try playback with the screen off, an interruption and a return to the text. Ask listeners to choose where listening ends. Measure task completion and control without treating listening duration as spiritual benefit.", "guide": "listening", "guide_label": "Designing a listening experience", "sources": [ "vatican-full-presence" ] }, "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Support listening across surfaces", "screens": [ { "title": "Psalm 23 · Audio", "annotation": "A listening surface gives playback priority. Edition and recording identity remain visible; timing here is illustrative.", "blocks": [ { "kind": "label", "text": "BSB · Example recording", "extra": "" }, { "kind": "player", "text": "00:18 / 01:10", "extra": "Pause" }, { "kind": "links", "text": "Speed 1× · Repeat: Off", "extra": "" }, { "kind": "nav", "text": "Previous psalm|Next psalm", "extra": "" } ] }, { "title": "Device playback controls", "annotation": "System controls can support listening with the app out of view. Available controls depend on the platform.", "blocks": [ { "kind": "resource", "text": "Psalm 23", "extra": "BSB · Example recording" }, { "kind": "player", "text": "00:18 / 01:10", "extra": "Pause" } ] }, { "title": "Continue with Psalm 23", "annotation": "A listening position and a reading location are related but distinct. Offer both destinations.", "blocks": [ { "kind": "resource", "text": "Last heard: verse 2", "extra": "BSB · 00:18 · Example recording" }, { "kind": "button", "text": "Continue listening", "extra": "" }, { "kind": "links", "text": "Read from verse 2", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "takeaway": "Make current passage, playback, interruption and resumption available through suitable device and accessibility controls.", "principles": [ "offering", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone wants to listen while resting, moving or keeping the phone out of sight.", "benefit": "Core playback controls remain available without maintaining visual attention.", "drawback": "Device controls offer less context than the app. Background playback and offline availability depend on the platform, recording and permissions.", "differences": "Screen-off access can help listeners with limited vision or occupied hands. Deaf and hard-of-hearing users need equivalent readable content. Listening should not require speech input.", "question": "Can the intended practice continue after the phone is put down?", "check": "Lock the device, interrupt playback and resume. Confirm the passage and position; repeat offline where downloads are supported." } }, { "id": "18", "slug": "read-along", "title": "Playback and reading positions can differ", "topic": "audio", "summary": "Follow the narration without forcing the reader to follow every movement.", "problem": "Someone may scroll ahead or revisit an earlier verse while playback continues. Automatic following can repeatedly pull them back.", "solution": "Show the current playback anchor separately from the viewport. Let users follow or explore freely, then deliberately return to the spoken passage. Use continuous text where the task is sustained reading.", "failure": "Automatic recentering after manual scroll; stopping playback whenever someone explores; treating the visible paragraph as the actual playback position.", "test": "Scroll away during playback, change text size and return to the spoken verse. Does each position remain understandable?", "sources": [ "dwell", "dwell-position", "youversion-audio", "diagram-psalm-kjv" ], "variants": [ { "title": "A · Follow narration", "caption": "The playing passage has a temporary marker.", "items": [ "heading|Psalm 23 · BSB", "label|Following narration · Verse timing", "psalm|one", "highlight|He makes me lie down in green pastures; He leads me beside quiet waters.|Verse 2 · Playing", "player|00:18 / 01:10|Pause" ], "when": "The reader wants to follow narration", "tradeoff": "Automatic following should yield to manual scrolling" }, { "title": "B · Explore freely", "caption": "Reading elsewhere does not silently change playback.", "items": [ "heading|Psalm 23 · BSB", "label|Following paused", "psalm|one", "resource|Audio continues at verse 2|BSB · Example recording", "links|Return to spoken verse", "player|00:18 / 01:10|Pause" ], "when": "The reader explores elsewhere while listening", "tradeoff": "The audio anchor needs a separate label" }, { "title": "C · Rejoin playback", "caption": "Following resumes only after the reader chooses it.", "items": [ "heading|Psalm 23 · BSB", "highlight|He makes me lie down in green pastures; He leads me beside quiet waters.|Verse 2 · Audio position", "button|Follow narration", "links|Keep exploring", "player|00:18 / 01:10|Pause" ], "when": "The reader chooses to return to playback", "tradeoff": "Rejoining must not silently save a personal mark" } ], "faith": "This pattern separates playback position from reading position. Karaoke granularity is covered by Timing has an honest granularity; styling and no highlighting by Playback cues are a reader preference. Translation switching must preserve the reading anchor and reassess audio alignment.", "status": "Research-informed design proposal", "related": [ "honest-synchronisation", "playback-highlight-style", "translation-position" ], "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Follow, explore and rejoin", "screens": [ { "title": "Psalm 23 · BSB", "annotation": "The current verse is highlighted from a timing map. Word-level highlighting would require word-level data.", "blocks": [ { "kind": "label", "text": "Following narration · Verse timing", "extra": "" }, { "kind": "psalm", "text": "one", "extra": "" }, { "kind": "highlight", "text": "He makes me lie down in green pastures; He leads me beside quiet waters.", "extra": "Verse 2 · Playing" }, { "kind": "player", "text": "00:18 / 01:10", "extra": "Pause" } ] }, { "title": "Psalm 23 · BSB", "annotation": "Manual exploration pauses automatic following without pausing the audio.", "blocks": [ { "kind": "label", "text": "Following paused", "extra": "" }, { "kind": "psalm", "text": "one", "extra": "" }, { "kind": "resource", "text": "Audio continues at verse 2", "extra": "BSB · Example recording" }, { "kind": "links", "text": "Return to spoken verse", "extra": "" }, { "kind": "player", "text": "00:18 / 01:10", "extra": "Pause" } ] }, { "title": "Psalm 23 · BSB", "annotation": "Returning to the audio position does not have to resume automatic scrolling. Make that choice explicit.", "blocks": [ { "kind": "highlight", "text": "He makes me lie down in green pastures; He leads me beside quiet waters.", "extra": "Verse 2 · Audio position" }, { "kind": "button", "text": "Follow narration", "extra": "" }, { "kind": "links", "text": "Keep exploring", "extra": "" }, { "kind": "player", "text": "00:18 / 01:10", "extra": "Pause" } ] } ] }, "diagram_decisions_owned": true, "takeaway": "Show the current playback anchor separately from the viewport.", "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A listener follows the text, explores elsewhere and returns to the narration.", "benefit": "Separating playback from reading position preserves both continuity and freedom to explore.", "drawback": "Two positions add state that must be explained. Word-by-word motion can distract, and inaccurate timing undermines trust.", "differences": "Some readers benefit from word, sentence or verse cues; others prefer no highlighting or manual scrolling. Offer preferences without treating one mode as an accessibility solution for everyone.", "question": "When a person scrolls away, whose intention controls the viewport?", "check": "Scroll away, change text size and rejoin. Playback should keep its position. Use only source-supported timing; provide a no-highlight mode and a clear follow control." } }, { "id": "20", "slug": "guided-sequence", "title": "Choose a devotional format", "topic": "audio", "summary": "Compare a continuous reading, a sequence of cards and a chaptered audio session.", "problem": "A swipe-based story can hide its length or force unwanted audio, prayer or disclosure before allowing progress.", "solution": "Separate the content model from its presentation: Scripture, reflection, video, prayer and silence retain their identity in each format. A continuous page supports scanning; multi-page steps offer explicit pacing; story-style cards can combine short media segments. Offer visible Previous, Next and an outline rather than relying on swipes. Avoid timed advance for text by default. Audio needs pause, chapter navigation, transcript and an explicit end. Switching formats should preserve a semantic section where correspondence exists; do not invent word-level synchronisation.", "failure": "A story that advances before the reader finishes; tiny text fitted to one card; essential teaching available only in uncaptioned video; media playback counted as prayer; a disabled Next button until personal disclosure; automatic playback of another devotional.", "test": "Move through a mixed-media session with sound off, large text, keyboard or screen reader navigation, and an unavailable video. Leave during a section and return. Verify the selected content version and section are restored, and ask what is required versus optional.", "sources": [ "youversion-guided-current", "youversion-mixed-plans", "coe-daily-office", "diagram-psalm-kjv" ], "variants": [ { "title": "A · Continuous page", "caption": "Read and revisit without changing screens.", "when": "The reader wants to scan, linger or compare sections", "tradeoff": "Long sessions need landmarks and a saved position; a complete text alternative may require editorial work.", "items": [ "heading|A moment of gratitude", "label|Illustrative devotional · Original reflection", "quote|The LORD is my shepherd; I shall not want.|Psalm 23:1 · BSB", "label|Reflection", "chat|Who has offered you care this week? You might hold that person in prayer.", "links|Optional audio · Finish for now" ] }, { "title": "B · Cards or pages", "caption": "One step at a time, with the whole visible.", "when": "The session has distinct short stages or media", "tradeoff": "Story familiarity does not justify automatic advance or swipe-only navigation. Multi-page reading must allow reflow.", "items": [ "heading|A moment of gratitude", "label|2 of 4 · Reflection", "chat|Who has offered you care this week?", "chat|Take a moment. No written answer is needed.", "button|Continue", "links|Previous · Outline · Finish for now" ] }, { "title": "C · Chaptered audio", "caption": "Listen with a route back to the text.", "when": "The person wants to listen with less screen attention", "tradeoff": "Audio and text may differ; identify adaptations and do not claim exact alignment without timing data.", "items": [ "heading|Listen · A moment of gratitude", "label|Illustrative recording · Reflection", "player|02:10 / 08:00|Pause", "list|Scripture / Reflection / Prayer / Silence|Reflection", "links|Read transcript", "note|Stops after this session" ] } ], "faith": "A sequence carries a view of spiritual practice. Read, reflect, pray and rest may be a useful editorial structure, but it is not a universal order for every tradition or reader. Identify the practice and author; distinguish required elements of a named liturgy from optional app prompts.", "status": "Research-informed design proposal", "takeaway": "Use a continuous page for reading and revisiting, cards for distinct steps, and chaptered audio for listening. Keep the session’s scope, media requirements and ending clear in every format.", "related": [ "prayer-interface", "audio-first", "progress-and-streaks" ], "flow": [ "Preview the author, practice, sections, approximate media duration and any downloads.", "Choose a supported reading or listening format; identify Scripture and commentary.", "Move at a chosen pace. Offer captions, transcripts and explicit navigation beside gestures.", "Pause or leave; retain section identity and playback position separately.", "Return to the same edition of the session, or explain an update. Finish without another session starting." ], "purpose_lens": { "assumption": "A familiar story format can make a devotion easy to enter, while also suggesting that the task is to reach the last card. Decide whether the person needs an overview, gentle pacing or freedom from the screen. Reaching the end is a navigation event, not evidence of reflection.", "situations": [ [ "Read in a short quiet interval", "Use a readable page or short sections with a visible outline. Let the reader see the commitment before beginning and leave with their place saved." ], [ "Listen while the phone is away", "Offer chaptered audio with screen-off playback and a deliberate endpoint. Identify any differences from the written version." ], [ "Return to one thought", "Allow direct access to Scripture, a reflection or a prayer without replaying earlier media. Keep notes attached to a stable section even if the format changes." ] ], "question": "Does each transition invite attention to the material, or reward moving past it?", "test": "Try beginning in text, switching to audio, stopping mid-session and returning to one section. Ask people to explain what the app marked complete.", "guide": "reading-rhythms", "guide_label": "Design a rhythm that makes room for life", "sources": [] }, "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Choose the form of the session", "screens": [ { "title": "A moment of gratitude", "annotation": "One readable page supports scanning and revisiting. Keep Scripture and the author’s reflection distinct.", "blocks": [ { "kind": "label", "text": "Illustrative devotional · Original reflection", "extra": "" }, { "kind": "quote", "text": "The LORD is my shepherd; I shall not want.", "extra": "Psalm 23:1 · BSB" }, { "kind": "label", "text": "Reflection", "extra": "" }, { "kind": "chat", "text": "Who has offered you care this week? You might hold that person in prayer.", "extra": "" }, { "kind": "links", "text": "Optional audio · Finish for now", "extra": "" } ] }, { "title": "A moment of gratitude", "annotation": "A bounded sequence can guide attention without automatic advance. Make the outline and exit available.", "blocks": [ { "kind": "label", "text": "2 of 4 · Reflection", "extra": "" }, { "kind": "chat", "text": "Who has offered you care this week?", "extra": "" }, { "kind": "chat", "text": "Take a moment. No written answer is needed.", "extra": "" }, { "kind": "button", "text": "Continue", "extra": "" }, { "kind": "links", "text": "Previous · Outline · Finish for now", "extra": "" } ] }, { "title": "Listen · A moment of gratitude", "annotation": "Audio chapters help someone return to one part of a practice. Provide a transcript and an intentional endpoint.", "blocks": [ { "kind": "label", "text": "Illustrative recording · Reflection", "extra": "" }, { "kind": "player", "text": "02:10 / 08:00", "extra": "Pause" }, { "kind": "list", "text": "Scripture|Reflection|Prayer|Silence", "extra": "Reflection" }, { "kind": "links", "text": "Read transcript", "extra": "" }, { "kind": "note", "text": "Stops after this session", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone chooses a devotional or mixed-media session.", "benefit": "A clear format and outline help the person anticipate and control the experience.", "drawback": "Cards fragment long text; continuous pages can be lengthy; audio needs alternatives and reliable resumption.", "differences": "The same person may read quietly, listen while moving or revisit one section. Access needs and setting should influence the format.", "question": "Does the format serve the practice or reproduce a feed’s pressure to continue?", "check": "Test format changes, large text, unavailable media, interruption and a deliberate ending." } }, { "id": "30", "slug": "contextual-study-panel", "title": "Preview before deep study", "topic": "study", "summary": "Reveal relevant information from a passage without replacing the reader.", "problem": "Selecting text can expose too many actions or open a panel that unexpectedly changes as the reader moves.", "solution": "Offer a small selection action menu, then preview the relevant resource before deeper study. Let a linked panel either follow the passage or remain pinned, with its current anchor visible.", "failure": "A panel silently following a different verse; a resource opened without source context; a crowded selection menu that prevents reading.", "test": "Test moving between verses with a linked and pinned panel. Can readers identify the panel’s anchor and recover the main reading task?", "sources": [ "olivetree", "placement", "shape", "olive-study-current", "diagram-psalm-kjv" ], "variants": [ { "title": "A · Select an action", "caption": "Selection exposes relevant choices.", "items": [ "heading|Psalm 23 · BSB", "quote|The LORD is my shepherd; I shall not want.|Psalm 23:1 · Selected", "links|Highlight · Note · Explore · Ask", "psalm|two" ], "when": "The user has selected text", "tradeoff": "An action menu should stay small" }, { "title": "B · Preview a resource", "caption": "A brief excerpt leads to the complete source.", "items": [ "heading|Resources · Psalm 23:1", "resource|Commentary|Example author · Psalm 23:1", "note|Illustrative commentary: Notice how the shepherd image shapes the language of care.", "links|Read full resource · Back to passage" ], "when": "A resource can be checked quickly", "tradeoff": "A preview may omit details needed for study" }, { "title": "C · Pin the panel", "caption": "Following and pinning are explicit modes.", "items": [ "heading|Study panel · Pinned", "label|Reader: Psalm 23:2", "psalm|two", "resource|Panel: Psalm 23:1|Pinned · Example commentary", "links|Follow reader · Keep pinned" ], "when": "A reference should remain fixed while reading moves", "tradeoff": "Pinned and following states need distinct anchors" } ], "faith": "", "status": "Research-informed design proposal", "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "From selection to a study surface", "screens": [ { "title": "Psalm 23 · BSB", "annotation": "Verse selection reveals actions; a contextual toolbar can avoid a wall of primary buttons.", "blocks": [ { "kind": "quote", "text": "The LORD is my shepherd; I shall not want.", "extra": "Psalm 23:1 · Selected" }, { "kind": "links", "text": "Highlight · Note · Explore · Ask", "extra": "" }, { "kind": "psalm", "text": "two", "extra": "" } ] }, { "title": "Resources · Psalm 23:1", "annotation": "Preview enough to choose a source. Keep its author and scope visible.", "blocks": [ { "kind": "resource", "text": "Commentary", "extra": "Example author · Psalm 23:1" }, { "kind": "note", "text": "Illustrative commentary: Notice how the shepherd image shapes the language of care.", "extra": "" }, { "kind": "links", "text": "Read full resource · Back to passage", "extra": "" } ] }, { "title": "Study panel · Pinned", "annotation": "Reader and panel positions can differ. Show both and make following the reader an explicit action.", "blocks": [ { "kind": "label", "text": "Reader: Psalm 23:2", "extra": "" }, { "kind": "psalm", "text": "two", "extra": "" }, { "kind": "resource", "text": "Panel: Psalm 23:1", "extra": "Pinned · Example commentary" }, { "kind": "links", "text": "Follow reader · Keep pinned", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "takeaway": "Offer a small selection action menu, then preview the relevant resource before deeper study.", "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Reading leads to a note, commentary or related resource.", "benefit": "A panel can preserve the passage while supporting deeper study.", "drawback": "A following panel can move unexpectedly; a pinned one can become stale.", "differences": "Mobile sheets and splits trade space differently from desktop panels. Always retain the panel’s own anchor.", "question": "Can someone tell whether the resource follows the reader or remains pinned?", "check": "Test moving between verses with a linked and pinned panel. Can readers identify the panel’s anchor and recover the main reading task?" } }, { "id": "32", "slug": "annotation-anchors", "title": "The annotation anchor is explicit", "topic": "study", "summary": "Make exact wording and reference-based notes different personal objects.", "problem": "A highlight on particular words and a note about a verse behave differently when the translation changes.", "solution": "Allow quick marking without forced organisation. Explain whether the annotation targets an exact edition-specific selection or a passage reference. Colours and labels are optional personal conventions.", "failure": "Assuming a colour reveals theology or mood; requiring tags before saving; promising exact word transfer across translations.", "test": "Can users understand where their note will appear after switching editions? Test unlabelled highlights and annotations across verse ranges.", "sources": [ "logos-notes", "olive-annotations-current" ], "variants": [ { "title": "A · Mark first", "caption": "Organisation can wait.", "items": [ "tag|Psalm 23:1 · Selection", "highlight|Selected words", "button|Highlight", "button|Add a note", "notice|A label is optional." ], "when": "The user wants a quick mark", "tradeoff": "Forced categorisation slows a simple task" }, { "title": "B · Choose the anchor", "caption": "Exact text and a passage reference have different scope.", "items": [ "card|Exact selection|Attached to wording in Translation A.", "card|Passage reference|Attached to Psalm 23:1.", "button|Choose anchor type" ], "when": "A note may need to travel across editions", "tradeoff": "Reference anchors and exact wording have different scope" }, { "title": "C · Personal meaning", "caption": "The user defines whether a mark has a meaning.", "items": [ "card|My highlight styles|Important / Question / No label.", "button|Name a style", "button|Use colour only" ], "when": "The user wants personal style meanings", "tradeoff": "Do not infer theology or mood from a colour" } ], "faith": "", "status": "Research-informed design proposal", "takeaway": "Allow quick marking without forced organisation.", "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A mark or note needs to survive a change of edition.", "benefit": "Explicit anchors clarify whether wording or passage identity is being saved.", "drawback": "Anchor options can burden quick capture; word alignment may not exist.", "differences": "Someone marking wording needs the original edition; someone reflecting on a passage may prefer a reference anchor.", "question": "What exactly did the person save, and where will it appear later?", "check": "Can users understand where their note will appear after switching editions? Test unlabelled highlights and annotations across verse ranges." } }, { "id": "33", "slug": "highlight-overlap", "title": "Overlaps remain legible", "topic": "study", "summary": "Distinguish playback, selection, search and saved highlights.", "problem": "Several states may highlight the same text. After a translation change, a saved word selection may have no reliable equivalent.", "solution": "Use different visual and accessible cues for transient and saved states. Carry reference-based notes through reliable reference mappings. Keep exact selections attached to their original edition when no word alignment exists.", "failure": "Everything represented by background colour; inventing a new selection in another edition; hiding the original annotation when mapping fails.", "test": "Combine playback, search and a personal mark on one verse. Switch editions and check that every annotation remains explainable and recoverable.", "sources": [ "logos-notes", "epub", "reflow", "olive-annotations-current" ], "variants": [ { "title": "A · Different states", "caption": "Visual roles are distinguishable beyond colour.", "items": [ "highlight|Audio: currently spoken passage", "card|Saved highlight|Personal annotation.", "label|Selection: outline", "label|Search result: underline" ], "when": "Playback, selection and saved marks overlap", "tradeoff": "Colour alone cannot carry all meanings" }, { "title": "B · Reference note", "caption": "A reliable passage anchor can remain visible.", "items": [ "tag|Translation B", "card|Note on Psalm 23:1|Reference anchor retained.", "button|Open my note" ], "when": "A note attaches to a reliably mapped reference", "tradeoff": "Edition-specific word marks still need separate handling" }, { "title": "C · Original word selection", "caption": "No new wording is invented.", "items": [ "notice|This highlight belongs to Translation A.", "button|Open the original selection", "button|Create a new highlight in B" ], "when": "Exact wording has no reliable equivalent", "tradeoff": "Keep the original mark rather than transferring it silently" } ], "faith": "", "status": "Research-informed design proposal", "takeaway": "Use different visual and accessible cues for transient and saved states.", "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Playback, search, selection and saved marks share one passage.", "benefit": "Distinct cues keep transient state separate from personal work.", "drawback": "Too many simultaneous cues can become visually noisy.", "differences": "People who cannot distinguish colours need other cues; people following audio may prefer reduced visual emphasis.", "question": "Can the reader tell what will persist after the current action ends?", "check": "Combine playback, search and a personal mark on one verse. Switch editions and check that every annotation remains explainable and recoverable." } }, { "id": "38", "slug": "progress-and-streaks", "title": "Progress and streaks", "topic": "formation", "summary": "Choose between a saved place, completion and a shared date. Explain what the record means.", "problem": "A display can help someone find their place while also suggesting how well they are doing spiritually. Opened content, marked completion, calendar position and consistency are different records.", "solution": "Define each state before designing the indicator. Store the saved passage separately from sessions the person marks complete and the dates assigned by a plan. Allow completion to be corrected. Rescheduling changes dates without filling gaps or erasing notes. Explain whether recorded activity is private or shared before enabling group visibility. Offer a clear next action; do not require a progress dashboard to reach the reading.", "failure": "Silently counting an opened passage as read; resetting completion when changing dates; presenting calendar delay as spiritual failure; using colour alone for status; turning a private activity record into a group ranking; claiming app activity captures reading elsewhere.", "test": "Ask readers to find their next session, correct an accidental completion and join today’s group reading without completing earlier sessions. Repeat with a screen reader, large text and an offline update. Ask what the display implies about them and who can see it. Compare usefulness and pressure with a saved-place-only version.", "sources": [ "youversion-catch-up", "rewards-intrinsic-meta", "autonomous-motivation", "lausanne-success", "mcheyne-preface", "benedict-18", "personal-quantification", "gamification-meta", "sdt", "habit-automaticity", "broken-streaks", "fresh-start", "shame-guilt" ], "variants": [ { "title": "A · Saved place", "caption": "Orientation without a completion score.", "when": "The reader needs the next passage, or a daily offering has no backlog", "tradeoff": "No overview of completed sessions; retain a history only if it serves a chosen task.", "items": [ "heading|Continue reading", "card|Your saved place|Luke 15 · Session 4", "button|Open session 4", "text|Choose another passage" ] }, { "title": "B · Bounded completion", "caption": "A record the reader can correct.", "when": "The person chose a finite sequence and wants to know what remains", "tradeoff": "State how completion is recorded; finishing the sequence is not proof of understanding.", "items": [ "heading|A seven-session plan", "card|3 of 7 marked complete|Session 1 · Complete / Session 2 · Complete / Session 3 · Complete / Session 4 · Not marked complete", "button|Continue session 4", "text|Edit completion" ] }, { "title": "C · Shared calendar", "caption": "Today’s reading and personal progress stay distinct.", "when": "A group or seasonal practice needs a common date", "tradeoff": "Explain schedule differences without making catch-up compulsory or exposing personal activity by default.", "items": [ "heading|Read with the group", "card|Today’s reading|Session 8 · Luke 18", "card|Your saved place|Session 4 · Luke 15", "button|Open today’s reading", "text|Continue from my saved place" ] } ], "faith": "A record can serve a chosen discipline without becoming a verdict on the person. Daily reading may matter deeply to someone; a period of absence tells the app little about their faithfulness. Describe what is known and leave space for the person’s own account of its meaning.", "status": "Research-informed design proposal", "takeaway": "Show the information needed for the next decision. A saved place may be enough; add completion for a bounded plan and calendar position when a shared date matters. Keep consistency optional and separate.", "related": [ "flexible-rhythm", "return-without-shame", "passage-focused-reading" ], "flow": [ "Open the plan at a useful next step; identify any shared date separately from the saved place.", "Let the reader mark a session complete or undo that mark. Opening the session alone does not silently complete it.", "When changing dates, preview the new schedule and explain group effects. Keep completion, notes and saved position intact.", "After offline use, show whether the change has synced. Resolve conflicting updates without silently inventing completion.", "Let the person finish, hide optional history or pause reminders without losing access to the plan." ], "purpose_lens": { "assumption": "A number invites comparison. Before adding one, decide whether it helps the reader orient, finish a chosen sequence or coordinate with others. More visible progress is not automatically more useful.", "situations": [ [ "Receive today’s passage", "Show the daily offering with an optional archive. Yesterday can remain available without becoming an overdue assignment." ], [ "Finish a chosen plan", "Show marked completion against a clear endpoint. Let someone correct the record or stop without losing their notes." ], [ "Support a chosen habit", "If someone wants consistency feedback, define what counts and let them hide it. A streak introduces an incentive beyond orientation; assess its effect on motivation and return after interruption." ] ], "question": "What does this display help the reader decide—and what might they believe it says about their spiritual life?", "test": "Compare a saved place with added completion or consistency feedback. Ask about control, usefulness and pressure over time, including after missed sessions. Do not infer motivation from the number of opens.", "guide": "reading-rhythms", "guide_label": "Reading rhythms, daily offerings and progress", "sources": [] }, "principles": [ "feed-the-flock", "growth", "enough" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone wants to find their next reading, finish a selected sequence or rejoin a group’s current passage.", "benefit": "A clearly labelled record can reduce uncertainty and help the person make the next choice.", "drawback": "Visible gaps or counts can become a source of pressure. App records also miss reading, listening or reflection that happens elsewhere.", "differences": "A self-directed reader may need only a saved place. A plan participant may value completion. A group member may need today’s date and their own position at once. These purposes can change between sessions.", "question": "Is the display describing an activity, coordinating a date or implying a judgment about the reader?", "check": "Have readers resume, undo completion and change dates. Ask what the record means, whether it feels useful and who can see it. Test comprehension and pressure separately from retention." } }, { "id": "39", "slug": "flexible-rhythm", "title": "A flexible reading rhythm", "topic": "formation", "summary": "Help someone choose a reading rhythm—and adjust it when life changes.", "problem": "A rigid daily plan can become unusable when someone’s schedule, ability or life situation changes.", "solution": "Let the person choose between a dated plan and a sequence that waits for them. Offer reminders separately. Before pausing or moving dates, explain what will change and preserve completed sessions, notes and the saved place. For a group plan, distinguish a personal adjustment from a change to the shared calendar.", "failure": "Forced daily goals; erasing progress after rescheduling; presenting missed days as moral failures.", "test": "Study real reading rhythms, including irregular and shared practice. Can users change pace without losing their place or feeling penalised?", "sources": [ "formation-agenda", "willard-disciplines-grace", "youversion-catch-up" ], "variants": [ { "title": "A · Choose a rhythm", "caption": "Daily and sequential plans are distinct options.", "items": [ "button|Read on chosen days", "button|Continue one session at a time", "button|Set my own pace" ], "when": "The person chooses a practice rhythm", "tradeoff": "Daily cadence may not fit their life" }, { "title": "B · Pause", "caption": "A pause has clear effects.", "items": [ "card|Pause this plan|Completed sessions remain saved.", "button|Pause until I return", "button|Choose a return date" ], "when": "A plan needs a deliberate pause", "tradeoff": "Pausing should not imply a debt" }, { "title": "C · Reschedule", "caption": "Upcoming work moves without creating a debt.", "items": [ "card|New rhythm|Two sessions each week.", "button|Preview updated schedule", "button|Keep existing progress" ], "when": "Dates no longer match circumstances", "tradeoff": "Rescheduling needs to retain useful progress" } ], "faith": "", "status": "Proposed hypothesis", "purpose_lens": { "assumption": "A daily offering can spare someone the decision of what to read without asking them to join a plan. A chosen plan adds a different commitment. A schedule can help coordinate that commitment. It can also ask for a rhythm that no longer fits their life. Before choosing the default, ask whether they need a shared date, a steady sequence or freedom to choose each time.", "situations": [ [ "Keep a shared date", "Use a calendar when a group or season depends on reading together. Offer today’s passage and an independent catch-up route; changing one person’s schedule must not silently change everyone else’s." ], [ "Continue through a sequence", "Resume at the next unread session when continuity matters more than dates. Explain that the sequence may no longer align with a shared calendar." ], [ "Choose freely each time", "Offer a saved place or open library when the person does not want a plan. This preserves choice but gives them more decisions; optional suggestions can help without enrolling them." ] ], "question": "Is the reader returning for a practice they value, for useful support, or mainly to protect a reward? What evidence would help us distinguish these?", "test": "Give participants a shared-date task and an interrupted personal sequence. Ask them to change pace, explain what moved, and find the next reading. Discuss usefulness and pressure separately from completion.", "guide": "reading-rhythms", "guide_label": "Reading plans and pressure", "sources": [ "willard-disciplines-grace" ] }, "takeaway": "Use a shared calendar when the date matters, or a sequence when continuing matters more than keeping up. Keep the saved place intact when the reader changes pace.", "principles": [ "enough", "feed-the-flock" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone wants reading structure that can adapt to their circumstances.", "benefit": "A chosen rhythm reduces repeated planning while preserving the option to pause or change pace.", "drawback": "Flexibility can make a shared calendar harder to coordinate. Multiple scheduling controls can also create complexity.", "differences": "A fixed date can support a group; irregular work or caring responsibilities may favour a sequence. Ask what structure helps rather than assigning a schedule from a user profile.", "question": "Does changing the rhythm preserve the person’s agency and the group’s expectations?", "check": "Pause a plan and reschedule it. Verify completed work, notes, reminder changes and group implications before confirmation." } }, { "id": "40", "slug": "return-without-shame", "title": "Return without shame", "topic": "formation", "summary": "Make it easy to pick up a reading practice after time away.", "problem": "A comeback screen may frame absence as failure and discourage a meaningful new session.", "solution": "Show the saved place and a clear way to continue. In a dated plan, distinguish resuming from opening today’s reading. Make a different starting point available without erasing earlier work. Keep paused reminders paused unless the person chooses to restart them. A return should not require an explanation or a new commitment.", "failure": "A guilt message; demanding reasons for absence; “save your streak” payments; escalating reminder frequency after silence.", "test": "Compare returning-user experiences through interviews and longitudinal observation. Does the welcome respect choice rather than merely increase opens?", "sources": [ "formation-agenda", "lausanne-success", "youversion-catch-up" ], "variants": [ { "title": "A · Fresh entry", "caption": "A new session can be enough.", "items": [ "heading|What fits today?", "button|A short passage", "button|Listen for a few minutes", "button|Continue my plan" ], "when": "A fresh entry is more useful than catching up", "tradeoff": "Do not erase the saved place unnecessarily" }, { "title": "B · Resume", "caption": "The saved anchor remains useful.", "items": [ "card|Your saved place|Passage and session.", "button|Continue from here", "button|Choose a different starting point" ], "when": "The person wants to resume earlier work", "tradeoff": "The former plan may still need adjustment" }, { "title": "C · Reduce pressure", "caption": "Notification control is part of returning.", "items": [ "button|Keep reminders paused", "button|Choose new reminder times", "button|Continue without reminders" ], "when": "A backlog or streak creates burden", "tradeoff": "Reducing pressure can change engagement metrics without reducing usefulness" } ], "faith": "", "status": "Proposed hypothesis", "purpose_lens": { "assumption": "An absence tells us little about why someone left. The interface should not diagnose their motivation or require a renewed spiritual commitment before they can continue.", "situations": [ [ "Resume something chosen", "Lead with the saved passage and intact notes. Show schedule changes neutrally rather than making the person reconstruct their place." ], [ "Join what is happening now", "For a dated group practice, offer today’s reading with a separate route to earlier material. Do not mark skipped sessions complete." ], [ "Begin differently", "Make changing or leaving a plan available. A short reading or audio option can help if chosen, but should not displace an explicit request to resume." ] ], "question": "Does the welcome serve the person’s next purpose, or mainly our wish to recover a lapsed user?", "test": "Ask people to return after an interruption, resume or change direction, and explain the screen’s tone. Include people who choose not to restart. Do not require a reason for their absence.", "guide": "reading-rhythms", "guide_label": "Reading plans and pressure", "sources": [ "lausanne-success" ] }, "takeaway": "Begin with a useful next step: the saved passage, today’s group reading or a different starting point. Keep their notes and place; let the person choose what fits now.", "principles": [ "enough", "feed-the-flock" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone comes back after an interruption and wants a useful next step.", "benefit": "A neutral welcome and saved place can reduce the effort of returning.", "drawback": "Hiding all history may remove information someone values. A short suggested reading can distract from the person’s original plan.", "differences": "Some people want continuity; others want a fresh beginning. Absence may reflect illness, access barriers, dissatisfaction or simply a different priority—not a deficit to diagnose.", "question": "Can someone return without explaining their absence or making a new commitment?", "check": "Offer resume and a different starting point. Ask participants what the screen implies about their absence; do not infer comfort from increased opens." } }, { "id": "44", "slug": "intent-controls", "title": "Intent controls support the prompt", "topic": "conversation", "summary": "Help people express scope through selections and task choices.", "problem": "A blank box makes users responsible for specifying passage, sources, purpose and output format in every prompt.", "solution": "Pair free text with editable context chips and concrete task controls. Use a passage selection, source scope and desired form to express intent. Confirm material assumptions rather than silently inferring them from private data.", "failure": "Forcing a complex prompt; invisible source filters; inferring belief or distress from a simple search.", "test": "Can novice users ask a scoped question and understand what sources and passage will be used? Test removing a context item and correcting an assumption.", "sources": [ "intent", "bennis", "shape", "playground", "genai" ], "variants": [ { "title": "A · Start from context", "caption": "A selected passage reduces prompt-writing effort.", "items": [ "tag|Mark 1:1–5 · Translation A", "button|Explain", "button|Compare", "button|Find related sources", "input|My own question" ], "when": "A question begins with a passage selection", "tradeoff": "Context chips should be editable" }, { "title": "B · Editable scope", "caption": "The active sources are visible and removable.", "items": [ "card|Context|Selected passage and two commentaries.", "button|Change source scope", "input|Ask within this context" ], "when": "The person wants to control source scope", "tradeoff": "Removing a source must change retrieval transparently" }, { "title": "C · Confirm an assumption", "caption": "The product asks only when the choice matters.", "items": [ "text|Should I use the sources you selected or search more widely?", "button|Selected sources only", "button|Search more widely" ], "when": "A material assumption is unresolved", "tradeoff": "Clarify without turning the task into an interview" } ], "faith": "", "status": "Research-informed design proposal", "purpose_lens": { "assumption": "Suggested actions define what the app considers worth asking. “Explain,” “compare” and “apply” privilege different purposes; none should silently become the goal of every conversation.", "situations": [ [ "Understand a passage", "Start from the selected text and edition, with optional explanation or source lookup. Preserve a free-form question rather than making the reader choose a theological conclusion." ], [ "Prepare or investigate", "Expose source scope and comparison controls. Let the person inspect disagreement and revise scope; do not make a devotional application mandatory." ], [ "Reflect personally", "Offer an optional reflective prompt without assuming a disclosure is needed. Do not infer a person’s beliefs or emotional state from the selected passage." ] ], "question": "Can someone pursue a question the product did not anticipate, including one that challenges its preferred interpretation?", "test": "Ask people to explain the active scope, remove a source, switch from explanation to comparison, and ask their own question. Check that the request and retrieval change with the controls, not just the visible labels.", "guide": "ai-trust", "guide_label": "AI, evidence and authority", "sources": [] }, "takeaway": "Pair free text with editable context chips and concrete task controls.", "principles": [ "welcome", "speak-for-god" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone knows the question but not how to write a detailed prompt.", "benefit": "Visible passage and source scope reduce repeated specification.", "drawback": "Defaults can narrow an answer in ways a reader does not notice.", "differences": "New users may benefit from a task suggestion; experienced users still need free text and removable context.", "question": "Which assumptions about sources and purpose are visible before sending?", "check": "Can novice users ask a scoped question and understand what sources and passage will be used? Test removing a context item and correcting an assumption." } }, { "id": "49", "slug": "verse-entry", "title": "A reference opens at a deliberate destination", "topic": "reading", "summary": "Choose the content scope, landing position and temporary cue separately.", "problem": "A link to Mark 1:8 can open the chapter at its beginning, land at verse 8, or display only verse 8. These choices support different tasks and should not be accidental.", "solution": "For contextual reading, open the containing chapter and place the first requested verse in view. For a focused preview, show only the verse or requested passage with a Read in context action. A chapter overview may open at the top, but retain the requested reference and provide Jump to verse. Scrolling and highlighting are independent: landing at a verse can use a temporary outline, a labelled margin cue, or no highlight. Mark a requested range rather than only its first verse when helpful. Temporary navigation cues never become saved annotations. Account for headers, players and delayed layout; retain back navigation to the search or chat.", "failure": "Opening at the chapter top without acknowledging the requested verse; permanently marking a deep-link target; hiding a focused excerpt’s boundaries; losing the origin.", "test": "Enter one verse, a range and a cross-chapter passage from search, chat and an external link. Check large text, cold loading, missing content and return navigation.", "sources": [ "usfm", "wcag-reflow" ], "variants": [ { "title": "A · Chapter overview", "caption": "Opening at the top is explicit, with a route to the actual target.", "items": [ "tag|Requested: Mark 1:8", "heading|Mark 1", "card|Chapter begins here|Context-first overview.", "button|Jump to verse 8" ], "when": "A chapter overview is the intended destination", "tradeoff": "Retain the requested reference and a jump action" }, { "title": "B · Anchored chapter", "caption": "The chapter remains available; the target is brought into view.", "items": [ "tag|Mark 1 · Translation A", "card|Earlier context|Verse 7.", "cueoutline|Verse 8 · Temporary navigation target", "card|Later context|Verse 9.", "button|Remove temporary cue" ], "when": "The person expects the verse in chapter context", "tradeoff": "A temporary navigation cue must not become a saved mark" }, { "title": "C · Focused passage", "caption": "Only the requested range appears until the reader chooses context.", "items": [ "tag|Mark 1:8–11 · Translation A", "card|Requested passage only|Verses 8–11, complete.", "button|Read in the full chapter", "button|Back to search" ], "when": "Only the requested range should be previewed", "tradeoff": "Make the boundary and route to full context explicit" } ], "faith": "For cross-chapter ranges, a focused reading surface can span chapter boundaries; a chapter-based view must make continuation explicit.", "status": "Research-informed design proposal", "related": [ "reference-resolution", "translation-position", "long-passages" ], "takeaway": "For contextual reading, open the containing chapter and place the first requested verse in view.", "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone opens a reference from search, chat or an external link.", "benefit": "A deliberate landing point connects the requested reference to its surrounding text.", "drawback": "A focused excerpt can hide context; a chapter overview can make the requested verse hard to find. A cue may be mistaken for a saved highlight.", "differences": "A quick lookup benefits from immediate reference confirmation. A study task may need the whole argument. Large text, screen readers and slow loading change how the target must be revealed.", "question": "Does the destination fulfil the promise made by the link?", "check": "Open a single verse and a cross-chapter range after a cold start. Verify visible and accessible identification, no obscured target, and return to the origin." } }, { "id": "51", "slug": "translation-position", "title": "Change translation without losing the passage", "topic": "reading", "summary": "Preserve a semantic reading anchor rather than a pixel offset.", "problem": "Different wording, poetry, headings and verse grouping change layout height. Retaining the old scroll offset can move the selected verse out of view.", "solution": "Before switching, identify the relevant anchor: the active selection or opened target, otherwise the visible reading verse; use the spoken verse only while Follow narration is enabled. Retain its approximate viewport position or bring it safely into view after the new edition has laid out. Reapply placement after late font or media loading only until the user scrolls; manual exploration takes precedence. Resolve versification with a trusted mapping and explain missing, split or merged verses. Keep reference notes separate from edition-specific word selections. Audio stays bound to its recorded edition: offer matching audio or clearly separate listening from the new text, and disable incompatible word cues.", "failure": "Restoring raw pixels; jumping to the chapter start; following audio after the reader scrolled away; copying word highlights onto unrelated wording; endlessly recentering during loading.", "test": "Switch editions while selecting a verse, freely reading, following audio, opening a note and using large text. Test poetry, missing verses, split or merged mappings, load failure and late reflow.", "sources": [ "usfm", "epub", "wcag-reflow" ], "variants": [ { "title": "A · Selected verse", "caption": "A semantic anchor survives a different paragraph height.", "items": [ "tag|Before: Translation A · Mark 1:8", "cueoutline|Selected verse, visible here", "label|Switch edition →", "tag|After: Translation B · Mark 1:8", "cueoutline|Mapped verse remains in view" ], "when": "A selection or opened target is active", "tradeoff": "Reapply its semantic anchor after layout settles" }, { "title": "B · Reading freely", "caption": "Preserve the visible reading place rather than the audio position.", "items": [ "tag|Reading Mark 1:5 · Audio at 1:8", "notice|Follow narration is off.", "card|Translation B · Mark 1:5|Reading anchor restored.", "button|Return to spoken verse" ], "when": "The person is exploring while audio continues", "tradeoff": "Preserve the reading anchor rather than the audio anchor" }, { "title": "C · Mapping or audio differs", "caption": "Unavailable equivalence has an explicit recovery.", "items": [ "notice|The selected verse has different numbering.", "button|Open the mapped passage", "notice|This recording uses Translation A.", "button|Keep audio without word cues", "button|Choose matching audio" ], "when": "Mapping or the recording edition differs", "tradeoff": "Explain the mismatch instead of claiming exact alignment" } ], "faith": "", "status": "Research-informed design proposal", "related": [ "verse-entry", "highlight-overlap", "read-along" ], "takeaway": "Before switching, identify the relevant anchor: the active selection or opened target, otherwise the visible reading verse; use the spoken verse only while Follow narration is enabled.", "principles": [ "word-distinct", "growth" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A reader changes editions while keeping a passage in view.", "benefit": "A semantic anchor preserves the task despite changed text lengths.", "drawback": "Verse numbering or book availability may differ; a saved pixel offset cannot resolve this.", "differences": "A comparison task needs precise correspondence. Continuous reading needs a stable visible passage. Audio alignment may be unavailable in the new edition.", "question": "What should remain stable: the selected passage, the reading position or the playback position?", "check": "Change editions with large text, an active selection and unavailable audio. Explain missing references rather than silently substituting a nearby verse." } }, { "id": "52", "slug": "chat-content-objects", "title": "Chat contains source objects, not just bubbles", "topic": "conversation", "summary": "Give verses, passages, links and media recognisable identity and appropriate actions.", "problem": "A bare link obscures its destination, while a large embed can crowd out the answer. Generated explanation can be mistaken for the text inside a Scripture card.", "solution": "Use an inline reference link for a brief citation, a bounded verse or passage card for text worth inspecting, and a full reader for sustained reading. Name edition, reference, visible range and source. Distinguish external link previews from Scripture and from generated commentary. Video cards identify publisher, duration and captions; audio cards retain passage and narrator. Do not autoplay. Provide plain links or labelled fallbacks when previews, media or permissions fail. Copy and sharing preserve reference and attribution where permitted. Returning from any destination restores conversation position.", "failure": "Autoplaying media; unlabelled generated verse text; enormous previews; a failed embed removing the source link; identical actions for read, play and external navigation.", "test": "Test a citation, single verse, long passage, external article, video and audio. Include blocked embeds, offline use, captions, large text, copy and return navigation.", "sources": [ "nng-chat", "playground-depth", "usfm", "wcag-reflow", "diagram-psalm-kjv" ], "variants": [ { "title": "A · Reference link", "caption": "A destination without an expanded quotation.", "items": [ "heading|Conversation", "chat|You can begin with Psalm 23.", "reference|Psalm 23 · BSB", "composer|Ask a follow-up…|Add context" ], "when": "The reference itself is sufficient and the reader can choose to open it", "tradeoff": "A link alone does not show what the cited text says; avoid making it carry an unsupported claim." }, { "title": "B · Verse quotation", "caption": "An attributed quotation within the conversation.", "items": [ "heading|Conversation", "chat|Here is the opening verse.", "quote|The LORD is my shepherd; I shall not want.|Psalm 23:1 · BSB", "links|Read in context · Copy with reference", "composer|Ask a follow-up…|Add context" ], "when": "The exact wording matters to the response", "tradeoff": "Keep the edition and excerpt boundary visible; longer text may need a dedicated reader." }, { "title": "C · External resource", "caption": "A preview identifies its destination and keeps a fallback link.", "items": [ "heading|Conversation", "chat|A related resource is available.", "resource|Reading the Psalms|Example publisher · example.org", "links|Open source article", "composer|Ask a follow-up…|Add context" ], "decision_index": 1, "when": "An external article is the evidence object", "tradeoff": "An unavailable preview must retain a usable link" }, { "title": "D · Media object", "caption": "The user chooses playback; metadata remains visible.", "items": [ "heading|Conversation", "media|Reading the Psalms|Example publisher · 04:20", "links|Play · Captions · Transcript", "composer|Ask a follow-up…|Add context" ], "decision_index": 2, "when": "Audio or video is relevant to the question", "tradeoff": "No autoplay and an accessible alternative are needed" } ], "faith": "", "status": "Research-informed design proposal", "related": [ "long-passages", "verse-entry", "many-results" ], "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Choose the object the message needs", "screens": [ { "title": "Conversation", "annotation": "A reference is a destination. It need not expand into a quotation in every answer.", "blocks": [ { "kind": "chat", "text": "You can begin with Psalm 23.", "extra": "" }, { "kind": "reference", "text": "Psalm 23 · BSB", "extra": "" }, { "kind": "composer", "text": "Ask a follow-up…", "extra": "Add context" } ] }, { "title": "Conversation", "annotation": "The verse is an attributed source object, visually distinct from the assistant’s wording.", "blocks": [ { "kind": "chat", "text": "Here is the opening verse.", "extra": "" }, { "kind": "quote", "text": "The LORD is my shepherd; I shall not want.", "extra": "Psalm 23:1 · BSB" }, { "kind": "links", "text": "Read in context · Copy with reference", "extra": "" }, { "kind": "composer", "text": "Ask a follow-up…", "extra": "Add context" } ] }, { "title": "Conversation", "annotation": "An external resource needs an identifiable publisher and destination even when no preview is available. Illustrative resource title; not a reviewed recommendation.", "blocks": [ { "kind": "chat", "text": "A related resource is available.", "extra": "" }, { "kind": "resource", "text": "Reading the Psalms", "extra": "Example publisher · example.org" }, { "kind": "links", "text": "Open source article", "extra": "" }, { "kind": "composer", "text": "Ask a follow-up…", "extra": "Add context" } ] }, { "title": "Conversation", "annotation": "Media controls belong to one named object. Duration and transcript access are not chat messages. Illustrative media object; no playable video.", "blocks": [ { "kind": "media", "text": "Reading the Psalms", "extra": "Example publisher · 04:20" }, { "kind": "links", "text": "Play · Captions · Transcript", "extra": "" }, { "kind": "composer", "text": "Ask a follow-up…", "extra": "Add context" } ] } ] }, "diagram_decisions_owned": true, "purpose_lens": { "assumption": "Placing Scripture, commentary and an assistant’s response in one stream can make their authority look equivalent. The content object should help the reader recognise what is quoted, what is interpreted and where each came from.", "situations": [ [ "Answer a quick reference question", "A clearly resolved reference link may be sufficient when the person asks where something appears. If the answer makes an interpretive claim, a reference alone may not make its support inspectable." ], [ "Look closely at the wording", "Use an attributed quotation with edition and excerpt boundaries. Keep an easy route to surrounding text, and preserve the conversation when returning." ], [ "Explore a teaching resource", "Show publisher, format and duration before opening an article or media item. A polished preview is not a quality endorsement; explain recommendation logic where it matters." ] ], "question": "Could a reader tell the difference between Scripture, an editorial explanation and a generated interpretation without opening another page?", "test": "Ask readers to identify who authored each item, inspect the supporting passage and return. Include an unavailable preview and a citation that does not support the attached claim.", "guide": "purposes", "guide_label": "Choose by the person’s purpose", "sources": [] }, "takeaway": "Use an inline reference link for a brief citation, a bounded verse or passage card for text worth inspecting, and a full reader for sustained reading.", "principles": [ "offering", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "An answer includes a verse, external source or playable media.", "benefit": "Recognisable objects make destination and available actions clearer.", "drawback": "Large cards can dominate an answer; tiny links can conceal important context.", "differences": "A source-checking reader needs provenance; a quick lookup needs a short route to the passage. Unavailable previews still need usable links.", "question": "Is the object Scripture, interpretation or an external resource—and is that obvious?", "check": "Test a citation, single verse, long passage, external article, video and audio. Include blocked embeds, offline use, captions, large text, copy and return navigation." } }, { "id": "53", "slug": "parallel-reading-layout", "title": "Parallel reading chooses a useful arrangement", "topic": "study", "summary": "Compare translations without forcing a desktop layout onto a small screen.", "problem": "Two adjacent translations can become narrow columns on a phone. Vertically stacked panes can hide the corresponding verse and make the relationship unclear.", "solution": "Choose left/right panes, top/bottom panes, or alternating edition blocks by the comparison task and available width. On mobile, a top/bottom split preserves line length, while a left/right split can suit brief passages when text remains readable. Offer a single-edition view or switching between editions when neither split fits enlarged text. On larger screens, side-by-side panes can support sustained comparison; let users resize or close panes without losing the reference. Keep edition labels, reference scope and scroll controls visible. Orientation names describe pane arrangement, not the direction in which Scripture should scroll.", "failure": "Shrinking text to fit columns; assuming landscape means enough space; hiding edition identity; putting one pane behind the player or keyboard.", "test": "Test portrait, landscape, a large screen, enlarged fonts, a long verse and poetry. Can users identify both editions, change arrangement and retain the target passage?", "sources": [ "usfm", "wcag-reflow", "diagram-psalm-kjv", "diagram-psalm-web" ], "variants": [ { "title": "A · Mobile: top and bottom", "caption": "Full-width panes share the available height; each retains its edition label.", "items": [ "heading|Psalm 23:1 · Compare", "parallel|stack", "links|Link scrolling: Off · One edition" ], "when": "A phone needs readable full-width panes", "tradeoff": "Stacked panes reduce each visible passage height" }, { "title": "B · Mobile: left and right", "caption": "A compact comparison is optional; do not shrink the reading type.", "items": [ "heading|Psalm 23:1 · Compare", "parallel|side", "links|Stack panes · Link scrolling: Off" ], "when": "Short comparison fits side-by-side on a phone", "tradeoff": "Line length may fail with large text" }, { "title": "C · Large screen: side by side", "caption": "Wider panes support continuous reading and a resizable divider.", "items": [ "heading|Compare editions · Larger screen", "parallel|wide", "links|Add edition · Link scrolling: On" ], "when": "A larger window supports sustained comparison", "tradeoff": "Resizing and extra panes need stable reading anchors" } ], "faith": "", "status": "Research-informed design proposal", "related": [ "parallel-scroll", "verse-by-verse-comparison", "adaptive-reading-workspace" ], "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Fit the comparison to the available space", "screens": [ { "title": "Psalm 23:1 · Compare", "annotation": "Stacking preserves reading width. Label each pane and keep its position distinct.", "blocks": [ { "kind": "parallel", "text": "stack", "extra": "" }, { "kind": "links", "text": "Link scrolling: Off · One edition", "extra": "" } ] }, { "title": "Psalm 23:1 · Compare", "annotation": "Narrow side-by-side panes need an easy route to stacking when text becomes cramped.", "blocks": [ { "kind": "parallel", "text": "side", "extra": "" }, { "kind": "links", "text": "Stack panes · Link scrolling: Off", "extra": "" } ] }, { "title": "Compare editions · Larger screen", "annotation": "Additional width supports a persistent comparison. Resizing should preserve the reference.", "blocks": [ { "kind": "parallel", "text": "wide", "extra": "" }, { "kind": "links", "text": "Add edition · Link scrolling: On", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "purpose_lens": { "assumption": "A comparison workspace assumes that the person wants to examine differences. More panes are not automatically more useful; the same person may want a single uninterrupted text for another purpose.", "situations": [ [ "Check one phrase on a phone", "Stack editions or offer a verse-by-verse comparison when side-by-side text becomes cramped. Keep edition labels adjacent to the wording." ], [ "Study several passages at a desk", "Side-by-side panes can support sustained comparison. Separate layout, scroll linking and reference alignment; resizing should not lose either place." ], [ "Return to devotional reading", "Offer a clear route back to one edition. Preserve the selected reference without carrying every study panel into the next reading session." ] ], "question": "Are we supporting a comparison the person chose, or making every reader manage a study workspace?", "test": "Compare a phrase at narrow width and enlarged text, explore one pane independently, then return to a single reader. Ask which edition and verse are active at each step.", "guide": "purposes", "guide_label": "Choose by the person’s purpose", "sources": [] }, "takeaway": "Choose left/right panes, top/bottom panes, or alternating edition blocks by the comparison task and available width.", "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A reader compares two editions or an edition with commentary.", "benefit": "A task-appropriate split keeps related material in view.", "drawback": "Narrow columns and divided height can both impair reading.", "differences": "A phone with enlarged text may need sequential switching even when a large screen can show adjacent panes.", "question": "Does simultaneous visibility help enough to justify the lost reading space?", "check": "Test portrait, landscape, a large screen, enlarged fonts, a long verse and poetry. Can users identify both editions, change arrangement and retain the target passage?" } }, { "id": "54", "slug": "parallel-scroll", "title": "Linked scrolling follows passage identity", "topic": "study", "summary": "Let parallel panes move together or independently, with an explicit way to rejoin.", "problem": "Different wording and poetry create different heights. Equal pixel scrolling can show unrelated verses in adjacent panes.", "solution": "Offer linked and independent scrolling. In linked mode, map the leading pane’s visible verse or passage anchor into the other pane instead of copying pixel offsets. Keep a stable leading pane during an interaction; avoid feedback loops and jitter. In independent mode, show each reference and offer Align at this verse. Rejoining uses the user’s chosen pane as the anchor. If a mapping is missing, split or merged, explain the correspondence and avoid pretending an exact line alignment. Playback following is a separate control; specify which pane it follows.", "failure": "Proportional scrolling presented as exact correspondence; snapping back after exploration; both panes endlessly steering each other; silently changing playback.", "test": "Scroll either pane, unlink, explore another chapter and rejoin. Test poetry, verse bridges, missing mappings, touch gestures, resizing and audio following.", "sources": [ "usfm", "wcag-reflow", "epub", "olive-study-current" ], "variants": [ { "title": "A · Linked by verse", "caption": "Different text heights still refer to the same passage.", "items": [ "tag|Scroll link: on · Anchor: Mark 1:8", "splitside|A · Verse 8|B · Verse 8", "button|Explore independently" ], "when": "Corresponding passages should follow together", "tradeoff": "Use reliable verse anchors rather than pixel ratios" }, { "title": "B · Independent exploration", "caption": "Each pane can show a different reference without snapping back.", "items": [ "tag|Scroll link: off", "splitstack|A · Mark 1:8|B · Mark 2:3", "button|Align B with A" ], "when": "The reader wants to explore each edition freely", "tradeoff": "Rejoining needs a chosen leading pane" }, { "title": "C · Mapping unavailable", "caption": "A gap interrupts synchronisation honestly.", "items": [ "splitside|A · Verse 8|B · Different numbering", "notice|Exact correspondence unavailable here.", "button|Review reference mapping", "button|Continue independently" ], "when": "Reference mapping is missing or nontrivial", "tradeoff": "Do not silently substitute a false correspondence" } ], "faith": "", "status": "Research-informed design proposal", "related": [ "parallel-reading-layout", "translation-position", "read-along" ], "takeaway": "Offer linked and independent scrolling.", "principles": [ "word-distinct", "growth" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A reader moves between corresponding passages in two panes.", "benefit": "Semantic linking can preserve correspondence despite unequal text length.", "drawback": "Automatic alignment can disrupt independent exploration or fail with different numbering.", "differences": "Close comparison may favour linked panes; a cross-reference investigation may need independent positions.", "question": "Which pane leads, and can the reader unlink and rejoin deliberately?", "check": "Scroll either pane, unlink, explore another chapter and rejoin. Test poetry, verse bridges, missing mappings, touch gestures, resizing and audio following." } }, { "id": "55", "slug": "verse-by-verse-comparison", "title": "Group editions around a shared verse", "topic": "study", "summary": "Use repeated verse groups when matching corresponding passages matters more than continuous reading.", "problem": "Independent columns make a short comparison difficult when translation lengths differ. Interleaving every verse can fragment a sustained reading task.", "solution": "Group the chosen editions beneath a common reference. Repeat edition labels and preserve wording, paragraph structure and edition-specific numbering. Offer stacked edition blocks for narrow screens and columns inside each verse group where width permits. A continuous-text alternative supports reading an argument or poem. With many editions, let users choose which to include rather than endlessly expanding every group. Explain split, merged or missing verse mappings within the group.", "failure": "Aligning words just because verse numbers match; stripping poetic structure; hiding edition labels after the first group; substituting empty text for a missing verse.", "test": "Compare short and long verses, poetry, two and several editions, different numbering and large text. Can readers switch back to continuous context?", "sources": [ "usfm", "wcag-reflow" ], "variants": [ { "title": "A · Mobile: stacked editions", "caption": "Each verse group repeats both edition labels.", "items": [ "versecompare|Mark 1:8|stacked", "versecompare|Mark 1:9|stacked", "button|Read continuous context" ], "when": "Matching verses is the main mobile task", "tradeoff": "Interleaving can fragment continuous reading" }, { "title": "B · Large screen: grouped columns", "caption": "Columns align verse groups, not individual words.", "items": [ "versecompare|Mark 1:8|columns", "versecompare|Mark 1:9|columns", "button|Choose editions" ], "when": "Width supports edition columns within each verse group", "tradeoff": "Equal verse numbers do not prove word alignment" }, { "title": "C · Continuous alternative", "caption": "Sustained reading can retain the author’s larger structure.", "items": [ "bible|Translation A · Mark 1", "button|Switch to Translation B", "button|Compare the current verse" ], "when": "The reader wants the argument or poem as a whole", "tradeoff": "Offer a direct return to targeted comparison" } ], "faith": "", "status": "Research-informed design proposal", "related": [ "parallel-reading-layout", "interlinear-reading", "translation-comparison" ], "takeaway": "Group the chosen editions beneath a common reference.", "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone wants to compare the wording of corresponding verses.", "benefit": "Edition blocks grouped under one reference make correspondence easier to inspect.", "drawback": "Interleaving can fragment poetry and an extended argument.", "differences": "A short comparison may suit grouped blocks; sustained reading needs continuous context.", "question": "Are we helping comparison without implying word-for-word equivalence?", "check": "Compare short and long verses, poetry, two and several editions, different numbering and large text. Can readers switch back to continuous context?" } }, { "id": "56", "slug": "interlinear-reading", "title": "Interlinear rows expose their alignment", "topic": "study", "summary": "Distinguish source-language tokens, glosses and translation wording.", "problem": "An interlinear view can make a gloss look like a complete translation and imply one-to-one word equivalence. Dense lexical metadata can overwhelm the passage.", "solution": "Label the source text, token alignment, gloss source and reading direction. A gloss is a lexical aid rather than a fluent translation or a definitive meaning in context. Offer compact token stacks, expandable word detail and wider aligned rows where space permits. Let the user choose which rows to display: original script, transliteration, gloss, morphology or lexical reference. On mobile, wrap whole token groups in source order or open one token at a time; preserve right-to-left ordering and bidirectional labels. Distinguish source-order interlinear from translation-order reverse interlinear. Missing token links need an explicit unavailable state rather than invented alignment.", "failure": "Breaking a token stack across lines; flattening right-to-left source order; presenting a gloss as the chosen Bible translation; guessing links from similar-looking words.", "test": "Test Greek and Hebrew with expert reviewers, narrow width, enlarged text, bidirectional scripts, multi-token mappings and missing alignment. Can readers identify the origin of every row?", "sources": [ "usfm", "wcag-reflow", "diagram-greek-john" ], "variants": [ { "title": "A · Mobile: compact token stacks", "caption": "Whole token groups wrap together; each row has a named role.", "items": [ "heading|John 1:1 · Greek", "label|Greek and glosses · Bible Hub", "tokens|compact", "links|Transliteration: On · Word details" ], "when": "Small-screen token inspection is useful", "tradeoff": "Wrap whole token groups rather than individual rows" }, { "title": "B · Large screen: aligned rows", "caption": "Extra room supports more layers, with optional metadata.", "items": [ "heading|John 1:1 · Aligned rows", "label|Two-token excerpt · Bible Hub", "tokens|rows", "links|Glosses: On · Transliteration: On" ], "when": "Several linguistic layers need comparison", "tradeoff": "Alignment and metadata require reliable sources" }, { "title": "C · Word detail on demand", "caption": "One word opens deeper study without crowding the passage.", "items": [ "heading|John 1:1 · Word detail", "label|Greek source · Bible Hub", "greek|Ἐν ἀρχῇ", "resource|ἀρχῇ · archē|Gloss: beginning", "note|Strong’s Greek 746 · Bible Hub", "links|Open lexical source · Back to passage" ], "when": "Only one word needs deeper analysis", "tradeoff": "An on-demand sheet must retain the source token anchor" } ], "faith": "The diagrams use labelled token placeholders, not invented Greek or Hebrew. Exact language layouts require real source data and specialist review.", "status": "Research-informed design proposal", "related": [ "word-study", "verse-by-verse-comparison", "adaptive-reading-workspace" ], "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Keep words and their layers connected", "screens": [ { "title": "John 1:1 · Greek", "annotation": "Keep each source token together with its gloss. These two opening words illustrate token association, not a complete verse.", "blocks": [ { "kind": "label", "text": "Greek and glosses · Bible Hub", "extra": "" }, { "kind": "tokens", "text": "compact", "extra": "" }, { "kind": "links", "text": "Transliteration: On · Word details", "extra": "" } ] }, { "title": "John 1:1 · Aligned rows", "annotation": "Parallel rows support systematic comparison on a larger surface. Keep the column association clear when text grows.", "blocks": [ { "kind": "label", "text": "Two-token excerpt · Bible Hub", "extra": "" }, { "kind": "tokens", "text": "rows", "extra": "" }, { "kind": "links", "text": "Glosses: On · Transliteration: On", "extra": "" } ] }, { "title": "John 1:1 · Word detail", "annotation": "A selected word can reveal information on demand. A gloss is a starting point, not a complete definition or theological conclusion.", "blocks": [ { "kind": "label", "text": "Greek source · Bible Hub", "extra": "" }, { "kind": "greek", "text": "Ἐν ἀρχῇ", "extra": "" }, { "kind": "resource", "text": "ἀρχῇ · archē", "extra": "Gloss: beginning" }, { "kind": "note", "text": "Strong’s Greek 746 · Bible Hub", "extra": "" }, { "kind": "links", "text": "Open lexical source · Back to passage", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "takeaway": "Label the source text, token alignment, gloss source and reading direction.", "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A reader investigates source-language words and their alignment.", "benefit": "Labelled token groups can connect forms, glosses and morphology.", "drawback": "A gloss may look like a complete translation; dense metadata can overwhelm.", "differences": "Beginning language learners may need one token at a time; experienced readers may want full rows. Neither should receive invented alignment.", "question": "Can the reader distinguish source text, gloss, translation and lexical interpretation?", "check": "Test Greek and Hebrew with expert reviewers, narrow width, enlarged text, bidirectional scripts, multi-token mappings and missing alignment. Can readers identify the origin of every row?" } }, { "id": "76", "slug": "passage-focused-reading", "title": "A bounded passage with a route to wider context", "topic": "reading", "summary": "Choose the reading unit by the task while keeping its boundaries and context visible.", "problem": "A chapter can be too broad for one reflection; an isolated verse can omit the argument. A focused page can also hide neighbouring text or imply that editorial boundaries are definitive.", "solution": "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.", "failure": "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.", "test": "Compare focused and continuous layouts for orientation, comprehension, voluntary rereading and context access. Include poetry and passages crossing chapter boundaries.", "sources": [ "dyer-reading", "dyer-author", "aperto-passage-design", "usfm", "kairos-draft" ], "variants": [ { "title": "A · Focused passage", "caption": "A coherent unit for a bounded encounter.", "items": [ "tag|Luke 15:1–7 · Edition A", "bible|Chosen passage", "notice|Editorial passage boundary", "button|Read preceding context", "button|Continue into the chapter" ], "when": "A bounded devotional or discussion task is chosen", "tradeoff": "Context routes and editorial boundaries remain explicit" }, { "title": "B · Continuous reading", "caption": "Sustained reading with a recoverable focus.", "items": [ "tag|Luke 15 · Edition A", "bible|Chapter reading", "highlight|Selected passage: verses 1–7", "button|Return to selected passage" ], "when": "The person wants sustained reading", "tradeoff": "Restore selection without repeatedly recentering" }, { "title": "C · Shared practice passage", "caption": "Several voluntary modes retain one source.", "items": [ "tag|This week: Luke 15:1–7", "bible|Verified passage", "button|Reflect on this passage", "button|Listen to an overview", "button|Read wider context" ], "when": "Several practices share a passage", "tradeoff": "Offer mode changes without forcing completion or disclosure" } ], "faith": "A pericope is an editorially bounded unit, not a universal measure of an ideal session. Short reading and sustained reading both remain legitimate.", "status": "Research-informed design proposal", "related": [ "reading-context", "text-structure", "reading-position", "source-grounded-audio" ], "takeaway": "Present the full chosen passage, its reference and edition.", "principles": [ "word-distinct", "growth" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A reader wants a coherent passage for reflection, with the freedom to continue.", "benefit": "A visible beginning and end can make the task understandable without substituting a summary for Scripture.", "drawback": "Editorial boundaries can obscure an argument or imply a preferred interpretation. A short unit may interrupt someone who wants sustained reading.", "differences": "A newcomer may value a bounded starting point; someone tracing an argument may need continuous text. The same reader can need both at different moments.", "question": "Who chose this boundary, and can the reader inspect and change it?", "check": "Ask readers to identify the passage boundaries, open preceding context and return. Observe orientation separately from comprehension." } }, { "id": "78", "slug": "ai-citations", "title": "Citations in AI answers", "topic": "study", "summary": "A citation is a route to supporting material, with source type and limitations visible.", "problem": "Numbered badges can imply authority without identifying what they support. A Bible reference, sermon interpretation and personal note have different roles and must not become interchangeable evidence.", "solution": "Attach citations to specific claims. Show source title, author, type, edition or publication details and a relevant excerpt or reliable media timestamp. Return to the claim after inspection. Distinguish a quotation, inference, disagreement and a claim with no supporting source.", "failure": "Whole-answer citation lists with unclear claim mapping; invented sources or timestamps; counting repeated sources as independent support; inaccessible evidence presented as verified.", "test": "Can readers identify what a source supports and what it does not? Test contradictory sources, dead links, permission limits, different verse numbering and a citation that does not entail the claim.", "sources": [ "shape", "playground", "example-vsb-native", "lumen-observed", "liu-verifiability", "ding-citation-trust", "sycophancy", "spatial-contiguity", "playground-citations", "nng-chat", "wcag-reflow", "nimh-suicide", "defreitas-farewells", "openai-long" ], "variants": [ { "title": "A · Claim-linked marker", "caption": "The marker belongs to a specific explanation.", "items": [ "tag|AI explanation · not Scripture", "card|Interpretive claim|This sentence cites a named source [1].", "button|Inspect source 1", "bible|Original passage" ], "when": "A claim has identifiable supporting material", "tradeoff": "A marker must map to a specific claim" }, { "title": "B · Evidence preview", "caption": "Inspect context before accepting a claim.", "items": [ "sheet|Source 1|Author · title · commentary", "card|Relevant excerpt|Quotation and surrounding context", "notice|Supports one reading, not the whole answer.", "button|Open original source", "button|Return to claim" ], "when": "The person inspects a citation", "tradeoff": "Evidence context and source type must remain visible" }, { "title": "C · Evidence gap", "caption": "Show a gap without manufacturing precision.", "items": [ "notice|This claim has no verified supporting excerpt.", "card|Source unavailable|Title and known provenance remain visible.", "button|Read another source", "button|Report citation problem" ], "when": "Support is missing or inaccessible", "tradeoff": "Show uncertainty without invented excerpts or timestamps" } ], "faith": "A reference to Scripture locates text; it does not automatically validate an interpretation. Personal notes are user-provided context, not scholarly authority.", "status": "Research-informed design proposal", "related": [ "media-evidence", "scripture-and-interpretation", "source-grounded-audio", "bounded-interpretation" ], "takeaway": "Attach citations to specific claims.", "principles": [ "word-distinct", "speak-for-god", "most-vulnerable" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A reader wants to examine the basis for a particular explanation.", "benefit": "Claim-level links allow inspection without abandoning the original question.", "drawback": "Citations can still support a weak inference. Previews may omit context, and unavailable sources can make verification impossible.", "differences": "A quick reader may use a preview; someone preparing to teach may need the full source, edition and surrounding argument. Neither should have to trust a badge as proof.", "question": "Does this source support this claim, or merely discuss the same subject?", "check": "Include one mismatched citation, one unavailable source and competing interpretations in a review. Check whether readers can identify the limits and return to the claim." } }, { "id": "79", "slug": "ai-involvement-disclosure", "title": "Identify what AI did, where it matters", "topic": "agency", "summary": "Label the actor, action and artifact at the moment they could be misunderstood.", "problem": "A Bible app mixes verified Scripture, authored commentary, personal notes and generated material. A brand name or sparkle icon may leave readers unsure whether they are reading a translation, a pastor’s words or an AI explanation.", "solution": "Use plain-language labels beside the relevant feature, speaker or content: AI assistant, explanation generated with AI, AI-assisted prayer draft, or synthetic voice reading a named edition. Keep a short visible label and optional details about sources, review and limitations. Retain identity through human handoffs and distinguish retrieval of publisher text from generated interpretation.", "failure": "Only disclosing in onboarding or terms; colour-only labels; generic AI tags with no operation; implied clergy credentials; treating a citation or human review badge as proof of correctness; placing an AI tag on verified Scripture because it sits inside an AI response.", "test": "Ask readers to identify who or what produced each layer, what AI changed and whether a human actually reviewed it. Test screen readers, first entry through deep links, audio-only use and AI-to-human transitions.", "sources": [ "shape", "shape-disclosure", "pair-trust", "hax-guidelines" ], "variants": [ { "title": "A · Before an AI action", "caption": "Explain the operation before it begins.", "items": [ "bible|Verified passage", "button|Generate an explanation with AI", "notice|Uses this passage and the sources you choose.", "button|Read attributed commentary instead" ], "when": "A person is about to use an AI feature", "tradeoff": "Name the operation and retain a non-AI route where offered" }, { "title": "B · Blended content", "caption": "Keep verified text and generated explanation distinct.", "items": [ "tag|Edition A · verified source text", "bible|Original passage", "card|Explanation generated with AI|This is interpretation, not the translation.", "button|Sources and creation details" ], "when": "Generated material sits beside verified text", "tradeoff": "Labels must identify each layer without labelling the translation as AI" }, { "title": "C · Actor transition", "caption": "Sender identity survives a real human handoff.", "items": [ "tag|AI assistant", "card|AI response|Generated response text.", "notice|Human support has joined · only after confirmed connection.", "card|Named human responder|Human-authored response." ], "when": "An interaction changes from AI to human", "tradeoff": "The change is shown only when a real responder is connected" } ], "faith": "A generated prayer is an editable draft, not divine speech. A synthetic voice reading verified Scripture changes narration provenance without making the edition text AI-authored.", "status": "Research-informed design proposal", "related": [ "scripture-and-interpretation", "narration-provenance", "portable-ai-provenance", "ai-citations" ], "purpose_lens": { "assumption": "A polished voice, personal tone or Scripture-shaped card can lend generated material authority. A generic AI badge cannot explain what was generated, who selected it or what supports it.", "situations": [ [ "Read Scripture with an explanation", "Keep edition text and generated explanation visually distinct. Identify AI involvement beside the explanation and keep its supporting sources inspectable." ], [ "Listen to a generated reflection", "Disclose generated script and synthetic voice where applicable before playback. Carry provenance into a saved or shared item; a listener may never see the original chat." ], [ "Use a suggested spiritual practice", "Identify the suggestion as generated and make the editorial or human review role clear. Do not imply divine direction or qualified pastoral judgment through tone or naming." ] ], "question": "What might a person reasonably believe about this content’s authorship or authority before opening a details panel?", "test": "Ask participants to identify Scripture, generated explanation, recorded speech and synthetic narration from representative examples. Check shared and audio-only contexts as well as the original screen.", "guide": "ai-trust", "guide_label": "AI, evidence and authority", "sources": [] }, "takeaway": "Use plain-language labels beside the relevant feature, speaker or content: AI assistant, explanation generated with AI, AI-assisted prayer draft, or synthetic voice reading a named edition.", "principles": [ "speak-for-god", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A person needs to understand who or what produced the content or response.", "benefit": "Specific labels help distinguish retrieved Scripture, generated interpretation, authored commentary and synthetic narration.", "drawback": "Repeated labels can become clutter. A disclosure can create false reassurance if it stands in for accountable behaviour.", "differences": "New visitors and people arriving through shared content miss onboarding. Audio listeners need audible identity at meaningful transitions; screen-reader users need labels associated with the relevant content.", "question": "What might a person reasonably mistake for Scripture, a human voice or pastoral authority?", "check": "Ask people to identify the origin of each layer and what review actually occurred. Include deep links, exported content and audio. Disclosure alone does not make a support service safe." } }, { "id": "81", "slug": "reading-layout", "title": "Paragraphs or one verse per line?", "summary": "Compare paragraph reading with a separate line for each verse, while preserving the edition’s poetry and structure.", "problem": "A verse-per-line layout makes references easy to locate but can visually fragment an argument. A paragraph layout supports continuity but makes individual verses less prominent.", "solution": "Begin with the edition’s paragraph and poetry structure for continuous reading. Offer a verse-per-line preference when reference finding is central, and retain meaningful paragraph and poetry distinctions in either mode.", "failure": "Flattening poetry into prose; treating verse breaks as sentence boundaries; changing layout and losing the selected passage.", "test": "Compare sustained reading and reference lookup at large text sizes. Ask readers to locate a verse, change layout and explain where the paragraph ends.", "faith": "Neither layout is inherently more faithful. The task, source structure and reader’s preferences matter.", "sources": [ "usfm-paragraphs", "wcag-reflow", "diagram-luke-kjv" ], "related": [ "verse-numbers", "text-structure", "passage-focused-reading" ], "variants": [ { "title": "A · Paragraphs", "caption": "Verse boundaries sit within continuous prose.", "when": "Following an argument or narrative", "tradeoff": "Inline numbers can interrupt reading; keep them subordinate.", "items": [ "heading|Luke 15 · BSB", "scripture|paragraph", "links|Aa · Reading settings" ] }, { "title": "B · Verse per line", "caption": "Each verse begins on a new line.", "when": "Finding, discussing or selecting individual verses", "tradeoff": "The visual rhythm may imply each verse is a separate thought.", "items": [ "heading|Luke 15 · BSB", "scripture|verses", "links|Aa · Reading settings" ] } ], "topic": "reading", "status": "Editorial design proposal", "takeaway": "Begin with the edition’s paragraph and poetry structure for continuous reading.", "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Compare two reading layouts", "screens": [ { "title": "Luke 15 · BSB", "annotation": "Paragraph grouping supports continuous reading; verse numbers remain available.", "blocks": [ { "kind": "scripture", "text": "paragraph", "extra": "" }, { "kind": "links", "text": "Aa · Reading settings", "extra": "" } ] }, { "title": "Luke 15 · BSB", "annotation": "A new line makes each verse easier to locate. It does not turn every verse into a separate thought.", "blocks": [ { "kind": "scripture", "text": "verses", "extra": "" }, { "kind": "links", "text": "Aa · Reading settings", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "purpose_lens": { "assumption": "A layout makes some reading actions easier to see. Separate verse rows favour locating and discussing a numbered unit; paragraphs favour following a larger movement of thought. Neither establishes how deeply someone reads or what a faithful reading practice should look like.", "situations": [ [ "Follow a sermon or group discussion", "Separate verse rows or prominent reference access can help people find a cited location quickly. Preserve the edition’s paragraph and poetic structure so navigation does not become the only way the text is understood." ], [ "Read a sustained passage", "Start with paragraphs and quiet verse numbers, while retaining selection and reference access. Test with enlarged text; a comfortable line length matters more than fitting a chapter onto one screen." ] ], "question": "Which action does the default make easy, and which reader has to work around it?", "test": "Ask the same participants to find a cited verse and to follow a longer argument in both layouts. Discuss orientation and reading comfort separately; task speed is not a measure of understanding.", "guide": "purposes", "guide_label": "Choose by the person’s purpose", "sources": [] }, "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Choose a reading layout without flattening the source’s structure.", "benefit": "Begin with the edition’s paragraph and poetry structure for continuous reading.", "drawback": "A verse-per-line layout makes references easy to locate but can visually fragment an argument. A paragraph layout supports continuity but makes individual verses less prominent.", "differences": "The visual rhythm may imply each verse is a separate thought.", "question": "Is the layout serving sustained reading, reference finding or both?", "check": "Compare sustained reading and reference lookup at large text sizes. Ask readers to locate a verse, change layout and explain where the paragraph ends." } }, { "id": "82", "slug": "verse-numbers", "title": "Verse numbers that help without taking over", "summary": "Separate locating a verse from the precision needed to select it.", "problem": "Tiny verse numbers may be useful landmarks but poor touch targets. Prominent numbers can compete with reading, while hiding them can make a spoken reference difficult to follow.", "solution": "Use modest inline numbers for a general reading default. Compare margin numbers for reference-heavy tasks and an optional quiet view. Preserve an accessible way to reveal references and select a verse without tapping a tiny superscript.", "failure": "Colour-only selection; hiding numbers with no way to recover a reference; a long-press-only action; copying text without its edition and reference.", "test": "Find and select a verse with enlarged text, keyboard and screen reader. Check that hiding visual numbers does not remove reference access.", "faith": "Numbers locate the text; they need not dictate its phrasing or paragraph structure.", "sources": [ "wcag-reflow", "usfm", "diagram-luke-kjv" ], "related": [ "verse-entry", "reading-layout", "annotation-anchors" ], "variants": [ { "title": "A · Inline numbers", "caption": "Small landmarks within the paragraph.", "when": "Reading and occasional lookup share the same surface", "tradeoff": "Use a separate selection action rather than a tiny number as the only target.", "items": [ "heading|Luke 15 · BSB", "scripture|paragraph", "links|Select a verse" ] }, { "title": "B · Margin numbers", "caption": "References occupy a consistent side rail.", "when": "People frequently follow or discuss numbered references", "tradeoff": "A margin consumes width; wrapped verses need unambiguous alignment.", "items": [ "heading|Luke 15 · BSB", "scripture|margin", "links|Select a verse" ] }, { "title": "C · Quiet reading", "caption": "Numbers are visually hidden by choice.", "when": "The reader wants less visual interruption", "tradeoff": "Keep reference access discoverable for sharing or returning.", "items": [ "heading|Luke 15 · BSB", "scripture|quiet", "links|Show verse numbers · Select" ] } ], "topic": "reading", "status": "Editorial design proposal", "takeaway": "Use modest inline numbers for a general reading default.", "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Alternatives", "screens": [ { "title": "Luke 15 · BSB", "annotation": "Keep inline numbers visually quiet and offer a larger selection target.", "blocks": [ { "kind": "scripture", "text": "paragraph", "extra": "" }, { "kind": "links", "text": "Select a verse", "extra": "" } ] }, { "title": "Luke 15 · BSB", "annotation": "Align each margin number with the start of its verse, including after text wraps.", "blocks": [ { "kind": "scripture", "text": "margin", "extra": "" }, { "kind": "links", "text": "Select a verse", "extra": "" } ] }, { "title": "Luke 15 · BSB", "annotation": "Quiet reading changes the display, not the text’s reference identity.", "blocks": [ { "kind": "scripture", "text": "quiet", "extra": "" }, { "kind": "links", "text": "Show verse numbers · Select", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Separate locating a verse from the precision needed to select it.", "benefit": "Use modest inline numbers for a general reading default.", "drawback": "Tiny verse numbers may be useful landmarks but poor touch targets. Prominent numbers can compete with reading, while hiding them can make a spoken reference difficult to follow.", "differences": "A margin consumes width; wrapped verses need unambiguous alignment.", "question": "Can a person locate and select a verse without precise tapping?", "check": "Find and select a verse with enlarged text, keyboard and screen reader. Check that hiding visual numbers does not remove reference access." } }, { "id": "83", "slug": "finding-a-passage", "title": "Finding a passage", "summary": "Let people browse when they do not know a reference and jump when they do.", "problem": "A single picker must serve familiar references, unfamiliar book names and returning to a recent passage. A dense grid can be fast for one reader and opaque for another.", "solution": "Offer book browsing and direct reference entry as complementary routes. Preserve the current location, make back and cancel predictable, and show the full destination before opening a parsed reference.", "failure": "Unexplained abbreviations; assuming every edition has the same book list; resetting book selection on back; accepting an ambiguous reference without clarification.", "test": "Locate an unfamiliar book, enter an abbreviated range, cancel after choosing a chapter and return to the original verse. Test long book names, different canons, large text and one-chapter books.", "faith": "Use the selected edition’s book list and ordering. Group labels should describe the edition rather than impose one tradition’s canon on all readers.", "sources": [ "usfm", "wcag-reflow", "mere-captures", "mere-current", "dei-verbum", "lifeway-reading-2024", "hutchings", "youversion-reader-navigation", "nng-recall", "wcag-error-suggestion", "wcag-target-size" ], "related": [ "book-chapter-layouts", "smart-passage-search", "chapter-navigation" ], "variants": [ { "title": "A · Step by step", "caption": "Book list → chapter grid → optional verse.", "when": "Small screens or readers who need full names", "tradeoff": "More steps; show the selected book and let back retain it.", "items": [ "heading|Mark · Choose chapter", "links|Back to books", "grid|1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 / 9 / 10 / 11 / 12 / 13 / 14 / 15 / 16|3", "button|Open Mark 3", "links|Choose a verse" ] }, { "title": "B · Browse together", "caption": "Book list beside chapters on a larger screen.", "when": "There is room to keep both levels visible", "tradeoff": "On narrow screens, stack or use steps instead of shrinking targets.", "items": [ "heading|Choose a passage", "browse|Mark|3", "button|Open Mark 3", "links|Cancel" ] }, { "title": "C · Type or return", "caption": "Reference entry with an explicit resolved destination.", "when": "The reader knows the reference or wants a recent passage", "tradeoff": "Localised aliases, ranges and ambiguous abbreviations need resolution.", "items": [ "heading|Go to a passage", "field|Mark 3:1–6", "resource|Mark 3:1–6|BSB · Reference found", "button|Open passage", "label|Recent", "list|Luke 15:1–3 / Psalm 23" ] }, { "title": "D · Chapter list", "caption": "A vertical list is an alternative to the chapter grid.", "when": "Larger labels, generous targets or chapter descriptions are more useful than density", "tradeoff": "Long books need more scrolling; offer a direct chapter jump and preserve position.", "items": [ "heading|Mark · Chapter list", "links|Back to books · Grid view", "list|Chapter 1 / Chapter 2 / Chapter 3 / Chapter 4 / Chapter 5|Chapter 3", "button|Open Mark 3", "links|Choose a verse" ] } ], "topic": "reading", "status": "Editorial design proposal", "takeaway": "Offer book browsing and direct reference entry as complementary routes.", "illustration": { "visual_style": "paper prototype pilot", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Choose a route into the passage", "screens": [ { "title": "Mark · Choose chapter", "annotation": "This is the chapter step after choosing a book. Back returns to the book list.", "blocks": [ { "kind": "links", "text": "Back to books", "extra": "" }, { "kind": "grid", "text": "1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16", "extra": "3" }, { "kind": "button", "text": "Open Mark 3", "extra": "" }, { "kind": "links", "text": "Choose a verse", "extra": "" } ] }, { "title": "Choose a passage", "annotation": "On a larger surface, retain both levels instead of replacing the book list.", "blocks": [ { "kind": "browse", "text": "Mark", "extra": "3" }, { "kind": "button", "text": "Open Mark 3", "extra": "" }, { "kind": "links", "text": "Cancel", "extra": "" } ] }, { "title": "Go to a passage", "annotation": "Resolve the typed reference before opening it; keep recent passages separate from results.", "blocks": [ { "kind": "field", "text": "Mark 3:1–6", "extra": "" }, { "kind": "resource", "text": "Mark 3:1–6", "extra": "BSB · Reference found" }, { "kind": "button", "text": "Open passage", "extra": "" }, { "kind": "label", "text": "Recent", "extra": "" }, { "kind": "list", "text": "Luke 15:1–3|Psalm 23", "extra": "" } ] }, { "title": "Mark · Chapter list", "annotation": "A list and a grid can serve the same chapter step. This illustration shows an excerpt of the list.", "blocks": [ { "kind": "links", "text": "Back to books · Grid view", "extra": "" }, { "kind": "list", "text": "Chapter 1|Chapter 2|Chapter 3|Chapter 4|Chapter 5", "extra": "Chapter 3" }, { "kind": "button", "text": "Open Mark 3", "extra": "" }, { "kind": "links", "text": "Choose a verse", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "purpose_lens": { "assumption": "The person already knows a book name, reference or familiar order. That may be true in one situation and false in the next.", "situations": [ [ "Follow a spoken reference", "Keep the location legible and offer direct access to the relevant level." ], [ "Find an unfamiliar book", "Offer full names and search without requiring abbreviations or knowledge of the order." ], [ "Read one chosen passage", "Open the passage directly; wider browsing can remain secondary." ] ], "question": "Which knowledge does this route assume, and what happens when that knowledge is missing?", "test": "Follow a reference, switch editions, cancel a new selection and return to the original place.", "guide": "passage-navigation", "guide_label": "Follow the whole passage navigation journey", "sources": [ "usfm-book-identifiers", "vsb-picker-review" ] }, "principles": [ "offering", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Let people browse when they do not know a reference and jump when they do.", "benefit": "Offer book browsing and direct reference entry as complementary routes.", "drawback": "A single picker must serve familiar references, unfamiliar book names and returning to a recent passage. A dense grid can be fast for one reader and opaque for another.", "differences": "On narrow screens, stack or use steps instead of shrinking targets.", "question": "Can someone who does not know the abbreviation still find the passage?", "check": "Locate an unfamiliar book, enter an abbreviated range, cancel after choosing a chapter and return to the original verse. Test long book names, different canons, large text and one-chapter books." } }, { "id": "84", "slug": "translation-picker", "title": "Choose a translation with enough context", "summary": "Make language, edition and availability understandable before switching.", "problem": "A list of abbreviations asks readers to recognise editions they may never have used. Download, audio and account requirements can remain hidden until after selection.", "solution": "Search by full name and abbreviation, group by language when useful, and show the active edition. Use a short favourites list for frequent switching with a clear route to all editions. Separate choosing an edition from downloading or starting audio. A short catalogue may need only a popover list, without search. A large multilingual collection may use language → edition drill-down, with optional favourites or downloaded filters. Confirm an unavailable passage before switching editions.", "failure": "Replacing an unavailable edition silently; presenting a popularity ranking as theological authority; losing the current passage; unclear download size or licence constraints.", "test": "Choose an unfamiliar edition, find a known abbreviation, cancel a download and change editions offline. Confirm the chosen text and retained reference.", "faith": "Edition descriptions should be attributed and neutral about translation approach. Availability is not a quality ranking or an endorsement.", "sources": [ "usfm", "wcag-reflow", "diagram-psalm-kjv", "mere-captures", "mere-current" ], "related": [ "translation-position", "book-chapter-layouts", "smart-passage-search" ], "variants": [ { "title": "A · Search all editions", "caption": "Search names and abbreviations within a language.", "when": "The desired edition is known or the list is large", "tradeoff": "Explain abbreviations and distinguish similarly named releases.", "items": [ "heading|Choose a translation", "field|Search names or abbreviations", "label|English", "list|King James Version · BSB / World English Bible · WEB|King James Version · BSB", "links|Other languages · Cancel" ] }, { "title": "B · Small catalogue popover", "caption": "A handful of available editions can fit beside the reader.", "when": "The catalogue is short and the reader switches often", "tradeoff": "Use full names; retain a route to language and availability details if the catalogue grows.", "items": [ "heading|Psalm 23 · BSB", "psalm|one", "resource|Translation|Current: BSB", "list|BSB · Berean Standard Bible / WEB · World English Bible|BSB · Berean Standard Bible", "links|All translations · Cancel" ] }, { "title": "C · Availability details", "caption": "Inspect a choice before committing to a download.", "when": "Offline access or a capability affects the choice", "tradeoff": "Add detail only where it supports a decision.", "items": [ "heading|World English Bible", "label|WEB · English", "resource|Text available online|Audio not available in this example", "button|Use WEB", "links|Download options · Back" ] } ], "topic": "reading", "status": "Editorial design proposal", "takeaway": "Search by full name and abbreviation, group by language when useful, and show the active edition.", "flow": [ "Open with the active edition identified and retain the current passage anchor.", "For a small catalogue, choose from full names; for a large one, select a language or search and filter.", "Show availability for the requested passage; offer a deliberate alternative if it is absent.", "After choosing, restore the passage in the new edition. Cancel leaves the old edition and position intact." ], "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Alternatives", "screens": [ { "title": "Choose a translation", "annotation": "Names identify editions; the current choice is a state, not a recommendation.", "blocks": [ { "kind": "field", "text": "Search names or abbreviations", "extra": "" }, { "kind": "label", "text": "English", "extra": "" }, { "kind": "list", "text": "King James Version · BSB|World English Bible · WEB", "extra": "King James Version · BSB" }, { "kind": "links", "text": "Other languages · Cancel", "extra": "" } ] }, { "title": "Psalm 23 · BSB", "annotation": "A short switcher can stay close to the reader. Provide a route to the full catalogue.", "blocks": [ { "kind": "psalm", "text": "one", "extra": "" }, { "kind": "resource", "text": "Translation", "extra": "Current: BSB" }, { "kind": "list", "text": "BSB · Berean Standard Bible|WEB · World English Bible", "extra": "BSB · Berean Standard Bible" }, { "kind": "links", "text": "All translations · Cancel", "extra": "" } ] }, { "title": "World English Bible", "annotation": "Choosing text and downloading text are different actions. Availability shown here is illustrative.", "blocks": [ { "kind": "label", "text": "WEB · English", "extra": "" }, { "kind": "resource", "text": "Text available online", "extra": "Audio not available in this example" }, { "kind": "button", "text": "Use WEB", "extra": "" }, { "kind": "links", "text": "Download options · Back", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "purpose_lens": { "assumption": "The person already knows a book name, reference or familiar order. That may be true in one situation and false in the next.", "situations": [ [ "Follow a spoken reference", "Keep the location legible and offer direct access to the relevant level." ], [ "Find an unfamiliar book", "Offer full names and search without requiring abbreviations or knowledge of the order." ], [ "Read one chosen passage", "Open the passage directly; wider browsing can remain secondary." ] ], "question": "Which knowledge does this route assume, and what happens when that knowledge is missing?", "test": "Follow a reference, switch editions, cancel a new selection and return to the original place.", "guide": "passage-navigation", "guide_label": "Follow the whole passage navigation journey", "sources": [ "usfm-book-identifiers", "vsb-picker-review" ] }, "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Make language, edition and availability understandable before switching.", "benefit": "Search by full name and abbreviation, group by language when useful, and show the active edition.", "drawback": "A list of abbreviations asks readers to recognise editions they may never have used. Download, audio and account requirements can remain hidden until after selection.", "differences": "A shortcut must not make other languages or editions hard to find.", "question": "Does the reader understand what will change before choosing?", "check": "Choose an unfamiliar edition, find a known abbreviation, cancel a download and change editions offline. Confirm the chosen text and retained reference." } }, { "id": "85", "slug": "chat-attachments", "title": "Show what the chat will use before sending", "summary": "A passage, file, image or link becomes visible, removable context.", "problem": "An attachment icon can hide the difference between selecting material, uploading it, extracting its text and using it to answer a question.", "solution": "Offer an explicitly labelled Add context action. Show each selected item with its type, scope and processing state. Make removal and cancellation available before sending; explain when upload begins and whether content leaves the device. Send only the context the person has chosen.", "failure": "Sending immediately after selection; implying upload means successful reading; keeping a removed item in hidden context; treating attached text as system instructions; silently including private notes.", "test": "Attach a passage and an unreadable file, remove one, cancel an upload and retry a failure. Check what is transmitted, extracted and retained. Verify the empty prompt, keyboard opening and large-text states.", "faith": "A prayer journal or pastoral document may contain another person’s private information. Attaching a file is not agreement to publish it, train on it or remember it indefinitely.", "sources": [ "intent", "shape", "wcag-reflow" ], "related": [ "intent-controls", "chat-content-objects", "long-passages" ], "variants": [ { "title": "A · Choose context", "caption": "Name the choices behind the attachment action.", "when": "The composer should remain simple until context is needed", "tradeoff": "A generic plus icon alone may conceal the feature.", "items": [ "heading|Ask about Scripture", "chat|What would you like to explore?", "list|Bible passage / File or image / Source link", "composer|Ask a question…|Add context" ] }, { "title": "B · Review before send", "caption": "Selected context stays beside the draft question.", "when": "A question depends on several sources", "tradeoff": "State size or scope and processing status; avoid a stack of oversized cards.", "items": [ "heading|Review your question", "chip|Psalm 23:1–3 · BSB|Ready · Remove", "chip|Study notes.pdf · 3 pages|Text extracted · Remove", "composer|How do these sources differ?|2 items" ] }, { "title": "C · Partial or failed input", "caption": "A selected file is not necessarily usable evidence.", "when": "Upload or text extraction fails or is incomplete", "tradeoff": "Do not silently answer as if the missing content was read.", "items": [ "heading|Review your question", "resource|Photo of notes|Text could not be read", "links|Replace image · Remove", "composer|Help me explore this passage.|Draft saved", "note|Remove or replace the unreadable attachment before sending." ] } ], "topic": "conversation", "status": "Editorial design proposal", "takeaway": "Offer an explicitly labelled Add context action.", "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Follow the attachment states", "screens": [ { "title": "Ask about Scripture", "annotation": "The attachment menu names what can become context; it does not imply every item is sent immediately.", "blocks": [ { "kind": "chat", "text": "What would you like to explore?", "extra": "" }, { "kind": "list", "text": "Bible passage|File or image|Source link", "extra": "" }, { "kind": "composer", "text": "Ask a question…", "extra": "Add context" } ] }, { "title": "Review your question", "annotation": "Show included items and their processing state before the person sends.", "blocks": [ { "kind": "chip", "text": "Psalm 23:1–3 · BSB", "extra": "Ready · Remove" }, { "kind": "chip", "text": "Study notes.pdf · 3 pages", "extra": "Text extracted · Remove" }, { "kind": "composer", "text": "How do these sources differ?", "extra": "2 items" } ] }, { "title": "Review your question", "annotation": "A failed attachment must not silently become context. Keep the draft and offer recovery.", "blocks": [ { "kind": "resource", "text": "Photo of notes", "extra": "Text could not be read" }, { "kind": "links", "text": "Replace image · Remove", "extra": "" }, { "kind": "composer", "text": "Help me explore this passage.", "extra": "Draft saved" }, { "kind": "note", "text": "Remove or replace the unreadable attachment before sending.", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "principles": [ "offering", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A passage, file, image or link becomes visible, removable context.", "benefit": "Offer an explicitly labelled Add context action.", "drawback": "An attachment icon can hide the difference between selecting material, uploading it, extracting its text and using it to answer a question.", "differences": "State size or scope and processing status; avoid a stack of oversized cards.", "question": "Does the person know what leaves the device and what the answer will actually use?", "check": "Attach a passage and an unreadable file, remove one, cancel an upload and retry a failure. Check what is transmitted, extracted and retained. Verify the empty prompt, keyboard opening and large-text states." } }, { "id": "86", "slug": "resource-discovery", "title": "How visible should extra resources be?", "summary": "Compare inline cards, small markers and resources revealed on demand.", "problem": "A resource can enrich a passage or interrupt it. Hiding everything protects the page but makes useful material difficult to discover.", "solution": "Choose the visibility of supplementary material by the reading task. Keep it clearly separate from Scripture, with author and type visible. Offer a quiet reading mode. A hidden-on-selection design still needs a discoverable Resources action and keyboard and assistive-technology access.", "failure": "A teaching card mistaken for part of the translation; unexplained icons; autoplay between verses; a gesture-only resource menu; locked material presented as already available.", "test": "Ask a new reader to find supplementary content, identify its author, hide it and resume at the same verse. Compare continuous reading with an intentional study task; include unavailable and paid resources.", "faith": "Resource prominence gives an interpretation attention and apparent authority. Name the author and perspective; do not imply that a single teacher’s material exhausts the meaning of a passage.", "sources": [ "gospelpartner-study", "olive-study-current", "wcag-reflow", "diagram-psalm-kjv" ], "related": [ "contextual-study-panel", "content-layers", "footnotes" ], "variants": [ { "title": "A · Inline resource card", "caption": "A resource appears between clearly separated Scripture blocks.", "when": "A chosen study mode makes supplementary teaching part of the task", "tradeoff": "High discoverability also means more interruption and visual authority.", "items": [ "heading|Psalm 23 · BSB", "psalm|one", "resource|Related reflection|Example author · Supplementary content", "links|Open reflection · Hide resources", "psalm|two" ] }, { "title": "B · Small resource marker", "caption": "A labelled indicator signals material without expanding it.", "when": "Continuous reading is primary but resources should remain discoverable", "tradeoff": "Icons need meaning, adequate targets and a way to distinguish resource types.", "items": [ "heading|Psalm 23 · BSB", "psalm|all", "reference|Verse 2 · 3 resources", "note|The marker opens a labelled resource list." ] }, { "title": "C · Reveal when requested", "caption": "Selection reveals actions while the ordinary reader stays quiet.", "when": "The person prefers an uncluttered reading surface", "tradeoff": "Selection or tap must not be the only way to discover the feature.", "items": [ "heading|Psalm 23 · BSB", "psalm|all", "links|Select a verse · Passage resources" ] } ], "topic": "study", "status": "Editorial design proposal", "takeaway": "Choose the visibility of supplementary material by the reading task.", "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Alternatives", "screens": [ { "title": "Psalm 23 · BSB", "annotation": "A supplementary card interrupts the reading surface. Identify it as interpretation and make it hideable.", "blocks": [ { "kind": "psalm", "text": "one", "extra": "" }, { "kind": "resource", "text": "Related reflection", "extra": "Example author · Supplementary content" }, { "kind": "links", "text": "Open reflection · Hide resources", "extra": "" }, { "kind": "psalm", "text": "two", "extra": "" } ] }, { "title": "Psalm 23 · BSB", "annotation": "A small marker keeps resources discoverable without placing the resource itself in the text.", "blocks": [ { "kind": "psalm", "text": "all", "extra": "" }, { "kind": "reference", "text": "Verse 2 · 3 resources", "extra": "" }, { "kind": "note", "text": "The marker opens a labelled resource list.", "extra": "" } ] }, { "title": "Psalm 23 · BSB", "annotation": "A quiet default shifts discovery to selection or an explicit resources action.", "blocks": [ { "kind": "psalm", "text": "all", "extra": "" }, { "kind": "links", "text": "Select a verse · Passage resources", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "principles": [ "offering", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Compare inline cards, small markers and resources revealed on demand.", "benefit": "Choose the visibility of supplementary material by the reading task.", "drawback": "A resource can enrich a passage or interrupt it. Hiding everything protects the page but makes useful material difficult to discover.", "differences": "Icons need meaning, adequate targets and a way to distinguish resource types.", "question": "Is the supplementary material serving this reading task or competing with it?", "check": "Ask a new reader to find supplementary content, identify its author, hide it and resume at the same verse. Compare continuous reading with an intentional study task; include unavailable and paid resources." } }, { "id": "87", "slug": "verse-comments", "title": "Keep my note distinct from a shared comment", "summary": "Origin, audience and anchor belong to the note—not just its screen.", "problem": "A comment might mean a private reflection, a group reply or published commentary. A single undifferentiated thread can disclose private writing or imply a source has authority it does not have.", "solution": "Start personal notes as private. Show the passage or exact-text anchor and save state. Make sharing a separate previewed action with an explicit audience. Keep publisher commentary and AI suggestions visibly separate from the person’s own words.", "failure": "A public composer styled like a private journal; changing visibility without confirmation; silent sync failure; quoting someone else’s disclosure into a shared thread.", "test": "Create a private note offline, inspect its anchor and preview sharing with a group. Cancel sharing, change edition and find the original note. Check what deletion can and cannot remove from recipients’ copies.", "faith": "Private reflection is not evidence of spiritual maturity for leaders or product analytics. A request for group discussion does not authorise sharing the person’s private history.", "sources": [ "olive-annotations-current", "youversion-plan-privacy" ], "related": [ "annotation-anchors", "annotation-library", "contextual-study-panel" ], "variants": [ { "title": "A · Private note", "caption": "A personal reflection has a visible audience and save state.", "when": "Someone is reflecting for themselves", "tradeoff": "Keep recovery and export available without forcing social participation.", "items": [ "bible|Mark 1:8 · Selected verse", "tag|My note · Private", "input|Write a reflection…", "notice|Saved on this device · Sync pending" ] }, { "title": "B · Share deliberately", "caption": "Preview the exact content and recipients before publication.", "when": "The person chooses to contribute to a known discussion", "tradeoff": "Removal may not retract material others copied.", "items": [ "card|Share this note?|Preview of selected text only", "tag|Audience: My reading group", "button|Publish to group", "button|Keep private" ] }, { "title": "C · Separate sources", "caption": "Different authorship remains apparent beside the same passage.", "when": "Personal notes and study material appear together", "tradeoff": "Extra labels cost space but prevent ambiguity about authority and privacy.", "items": [ "pickerlist|Mark 1:8|My note · Private / Group discussion · 2 replies / Publisher commentary · Author", "button|Open chosen layer" ] } ], "topic": "study", "status": "Editorial design proposal", "takeaway": "Start personal notes as private.", "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Origin, audience and anchor belong to the note—not just its screen.", "benefit": "Start personal notes as private.", "drawback": "A comment might mean a private reflection, a group reply or published commentary. A single undifferentiated thread can disclose private writing or imply a source has authority it does not have.", "differences": "Removal may not retract material others copied.", "question": "Could anyone mistake this audience or authorship?", "check": "Create a private note offline, inspect its anchor and preview sharing with a group. Cancel sharing, change edition and find the original note. Check what deletion can and cannot remove from recipients’ copies." } }, { "id": "88", "slug": "highlight-actions", "title": "Mark a passage without interrupting the thought", "summary": "Quick highlighting and deeper organisation can happen at different moments.", "problem": "A dense selection toolbar can obscure the text. Requiring labels, notebooks and colours before saving turns a small marking action into a form.", "solution": "Offer a small selection menu with Highlight, Note and More. Apply a sensible last-used or default style with undo. Make style labels and organisation optional, preserve the selection anchor, and provide an accessible selection path beyond long press.", "failure": "Marking the wrong range; gesture-only selection; requiring a colour taxonomy; confusing an audio cue with a saved mark; losing marks on edition changes.", "test": "Select a range crossing paragraphs, apply and undo a mark, add a note, then switch editions. Check narrow screens, handles near screen edges, keyboard access and save feedback.", "faith": "Do not infer a person’s belief, mood or spiritual progress from colours or highlighted passages. A mark can simply mean “return here.”", "sources": [ "olive-annotations-current", "wcag-reflow" ], "related": [ "annotation-anchors", "highlight-overlap", "verse-comments" ], "variants": [ { "title": "A · Mark now", "caption": "A compact menu keeps the selected passage visible.", "when": "Someone wants to save a thought quickly", "tradeoff": "A default style needs an easy undo and later edit.", "items": [ "bible|Selected passage", "cueoutline|Verses 8–9 · Selection", "pickerlist|Actions|Highlight / Add note / More", "notice|Highlight saved · Undo" ] }, { "title": "B · Choose a style", "caption": "Show named styles without making labels compulsory.", "when": "A person wants a personal marking convention", "tradeoff": "Colour alone is insufficient when a label has functional meaning.", "items": [ "bible|Selected verse", "pickerlist|Highlight style|Yellow · No label / Underline · Question / Outline · Revisit", "button|Apply style" ] }, { "title": "C · Organise later", "caption": "A saved mark can gain a note or collection afterwards.", "when": "Capture should take precedence over categorisation", "tradeoff": "People need a findable library to return to unfinished organisation.", "items": [ "card|Saved mark · Mark 1:8|Edition A · Original wording", "button|Add my note", "button|Move to a collection", "button|Open original selection" ] } ], "topic": "study", "status": "Editorial design proposal", "takeaway": "Offer a small selection menu with Highlight, Note and More.", "principles": [ "offering", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Quick highlighting and deeper organisation can happen at different moments.", "benefit": "Offer a small selection menu with Highlight, Note and More.", "drawback": "A dense selection toolbar can obscure the text. Requiring labels, notebooks and colours before saving turns a small marking action into a form.", "differences": "Colour alone is insufficient when a label has functional meaning.", "question": "Can someone save a thought now and organise it later?", "check": "Select a range crossing paragraphs, apply and undo a mark, add a note, then switch editions. Check narrow screens, handles near screen edges, keyboard access and save feedback." } }, { "id": "89", "slug": "book-chapter-layouts", "title": "Book and chapter pickers: list, grid or drill-down?", "summary": "Choose the browsing shape independently from the search field.", "problem": "A dense grid saves space but asks people to recognise names or abbreviations quickly. A long list supports full labels but requires more scrolling. Opening another level can hide the current selection.", "solution": "Start with full book names and a clear selected state. Compare a list, a compact grid and progressive book-to-chapter selection for the intended readers. Keep search available, preserve the current location on cancel, and use the selected edition’s actual book and chapter availability.", "failure": "Unexplained abbreviations; tiny grid targets; assuming one canon or ordering; losing the list position when returning from a chapter; an unavailable book silently opening elsewhere.", "test": "Find an unfamiliar book, select a chapter, go back and cancel. Repeat with long translated names, enlarged text, a one-chapter book and missing edition coverage.", "faith": "Canonical grouping is edition- and tradition-dependent. Labels should explain the collection rather than imply every Bible contains the same books.", "sources": [ "usfm", "wcag-reflow", "vsb-picker-review", "mere-captures", "mere-current" ], "related": [ "finding-a-passage", "smart-passage-search", "translation-picker" ], "flow": [ "Open the picker with the current book and chapter identified.", "Choose a book using its full name, search or a labelled grid.", "Show that book’s chapters; optionally offer a verse step.", "Open the chosen destination, or cancel and retain the original reading position." ], "variants": [ { "title": "A · Book list", "caption": "Full names, optional grouping and an obvious selected row.", "when": "Readers may not recognise abbreviations", "tradeoff": "A long list needs preserved position, search and meaningful headings.", "items": [ "heading|Choose a book", "field|Find a book", "list|Matthew / Mark / Luke / John / Acts / Romans|Mark", "links|Cancel" ] }, { "title": "B · Book grid", "caption": "A compact overview with readable names.", "when": "Readers scan familiar books frequently", "tradeoff": "Long names and large text may require fewer columns or a list fallback.", "items": [ "heading|Choose a book", "field|Find a book", "grid|Matthew / Mark / Luke / John / Acts / Romans|Mark", "links|List view · Cancel" ] }, { "title": "C · Chapter grid", "caption": "Book → chapter → optional verse in one recoverable flow.", "when": "A small screen needs room for one choice at a time", "tradeoff": "Extra steps should not erase the previous selection or scroll position.", "items": [ "heading|Mark · Choose chapter", "links|Back to books", "grid|1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 / 9 / 10 / 11 / 12 / 13 / 14 / 15 / 16|3", "button|Open Mark 3", "links|Choose a verse" ] }, { "title": "D · Chapter list", "caption": "A vertical list is an alternative to the chapter grid.", "when": "Larger labels, generous targets or chapter descriptions are more useful than density", "tradeoff": "Long books need more scrolling; offer a direct chapter jump and preserve position.", "items": [ "heading|Mark · Chapter list", "links|Back to books · Grid view", "list|Chapter 1 / Chapter 2 / Chapter 3 / Chapter 4 / Chapter 5|Chapter 3", "button|Open Mark 3", "links|Choose a verse" ] }, { "title": "E · Expand in place", "caption": "A book row reveals its chapter grid inside the list.", "when": "Keeping neighbouring books visible helps orientation", "tradeoff": "Long chapter grids push later books down; preserve the expanded book and scroll position.", "items": [ "heading|Books", "list|Genesis / Exodus / Leviticus / Numbers", "label|Deuteronomy · Expanded", "grid|21 / 22 / 23 / 24 / 25 / 26 / 27 / 28 / 29 / 30|25", "note|Excerpt of the 34-chapter grid", "list|Joshua / Judges", "links|Cancel" ] } ], "topic": "reading", "status": "Editorial design proposal", "takeaway": "Start with full book names and a clear selected state.", "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Choose a layout at each level", "screens": [ { "title": "Choose a book", "annotation": "Full names and a predictable order help when a reader does not know an abbreviation.", "blocks": [ { "kind": "field", "text": "Find a book", "extra": "" }, { "kind": "list", "text": "Matthew|Mark|Luke|John|Acts|Romans", "extra": "Mark" }, { "kind": "links", "text": "Cancel", "extra": "" } ] }, { "title": "Choose a book", "annotation": "A grid improves visual scanning for some readers; long names still need room.", "blocks": [ { "kind": "field", "text": "Find a book", "extra": "" }, { "kind": "grid", "text": "Matthew|Mark|Luke|John|Acts|Romans", "extra": "Mark" }, { "kind": "links", "text": "List view · Cancel", "extra": "" } ] }, { "title": "Mark · Choose chapter", "annotation": "The selected book stays visible; going back should preserve it.", "blocks": [ { "kind": "links", "text": "Back to books", "extra": "" }, { "kind": "grid", "text": "1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16", "extra": "3" }, { "kind": "button", "text": "Open Mark 3", "extra": "" }, { "kind": "links", "text": "Choose a verse", "extra": "" } ] }, { "title": "Mark · Chapter list", "annotation": "A list and a grid can serve the same chapter step. This illustration shows an excerpt of the list.", "blocks": [ { "kind": "links", "text": "Back to books · Grid view", "extra": "" }, { "kind": "list", "text": "Chapter 1|Chapter 2|Chapter 3|Chapter 4|Chapter 5", "extra": "Chapter 3" }, { "kind": "button", "text": "Open Mark 3", "extra": "" }, { "kind": "links", "text": "Choose a verse", "extra": "" } ] }, { "title": "Books", "annotation": "The chapter grid expands inside its book row. Other books remain part of the same list.", "blocks": [ { "kind": "list", "text": "Genesis|Exodus|Leviticus|Numbers", "extra": "" }, { "kind": "label", "text": "Deuteronomy · Expanded", "extra": "" }, { "kind": "grid", "text": "21|22|23|24|25|26|27|28|29|30", "extra": "25" }, { "kind": "note", "text": "Excerpt of the 34-chapter grid", "extra": "" }, { "kind": "list", "text": "Joshua|Judges", "extra": "" }, { "kind": "links", "text": "Cancel", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "purpose_lens": { "assumption": "The person already knows a book name, reference or familiar order. That may be true in one situation and false in the next.", "situations": [ [ "Follow a spoken reference", "Keep the location legible and offer direct access to the relevant level." ], [ "Find an unfamiliar book", "Offer full names and search without requiring abbreviations or knowledge of the order." ], [ "Read one chosen passage", "Open the passage directly; wider browsing can remain secondary." ] ], "question": "Which knowledge does this route assume, and what happens when that knowledge is missing?", "test": "Follow a reference, switch editions, cancel a new selection and return to the original place.", "guide": "passage-navigation", "guide_label": "Follow the whole passage navigation journey", "sources": [ "usfm-book-identifiers", "vsb-picker-review" ] }, "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Choose the browsing shape independently from the search field.", "benefit": "Start with full book names and a clear selected state.", "drawback": "A dense grid saves space but asks people to recognise names or abbreviations quickly. A long list supports full labels but requires more scrolling. Opening another level can hide the current selection.", "differences": "Long names and large text may require fewer columns or a list fallback.", "question": "Can someone unfamiliar with book names still complete the flow?", "check": "Find an unfamiliar book, select a chapter, go back and cancel. Repeat with long translated names, enlarged text, a one-chapter book and missing edition coverage." } }, { "id": "90", "slug": "chapter-navigation", "title": "How do readers move to the next chapter?", "summary": "Compare continuous reading, explicit buttons and a persistent navigation bar.", "problem": "No visible navigation can make a chapter feel like a dead end. Persistent controls consume space and can compete with audio, selection tools or the keyboard.", "solution": "Match navigation to the current task, not a permanent reader category. Continuous reading can cross a visible chapter boundary without permanent arrows. Discrete chapters benefit from explicit previous and next destinations. A compact bar suits frequent movement, while study may additionally need a back trail, saved place and direct reference entry. A bounded passage can end without a prominent Next action; retain optional wider context where useful. Keep controls clear of the final lines, audio controls and selection tools.", "failure": "Swipe-only navigation; wrapping from the last book to the first without warning; hiding the last verse behind a bar; changing chapter during text selection; a missing download leaving a blank page.", "test": "Give participants different tasks: continue a narrative, compare distant references, follow a spoken reference, resume a note and finish one shared passage. Observe misnavigation, return to place and unwanted interruptions. Ask whether they wanted a next step; do not infer usefulness from the number of chapters opened. Include large text, assistive technology and unavailable chapters.", "faith": "A product can invite exploration without implying that more reading proves greater faithfulness. Consider whether this particular invitation supports the person’s practice or primarily serves an engagement target.", "sources": [ "youversion-reader-navigation", "bibeltv-navigation", "wcag-reflow", "diagram-psalm-kjv", "mere-captures", "mere-current" ], "related": [ "book-chapter-layouts", "verse-entry", "reading-position" ], "flow": [ "Identify the current chapter and the available next destination.", "On a deliberate change, preserve the old position for back navigation.", "Load the next chapter with a clear heading; explain unavailable content.", "At a book or collection boundary, name the next destination rather than silently wrapping." ], "variants": [ { "title": "A · No persistent arrows", "caption": "Continuous reading carries the chapter transition.", "when": "The reader is following extended text", "tradeoff": "Still provide a discoverable direct jump and a clear end when content stops.", "items": [ "heading|Psalm 23 · BSB", "psalm|all", "links|Continue reading · Choose a passage" ] }, { "title": "B · Previous and next", "caption": "Explicit actions appear at a useful reading boundary.", "when": "The reader opens discrete chapters", "tradeoff": "End-only buttons are less convenient for quick hopping midway through a chapter.", "items": [ "heading|Psalm 23 · BSB", "psalm|all", "nav|Previous · Psalm 22 / Next · Psalm 24" ] }, { "title": "C · Compact navigation bar", "caption": "Current reference and adjacent chapters stay reachable.", "when": "Frequent navigation justifies persistent controls", "tradeoff": "Respect safe areas and audio controls; avoid covering text or forcing small targets.", "items": [ "heading|Psalm 23 · BSB", "psalm|all", "nav|Previous / Psalm 23 / Next" ] }, { "title": "D · In-context chapter rail", "caption": "Reveal chapter destinations beside the passage.", "when": "Quick jumps within the current book matter", "tradeoff": "Dense rails need generous targets, clear selected state and a non-gesture alternative; offer another picker for long books.", "items": [ "heading|Psalm 23 · BSB", "chapterrail|", "label|Current: Psalm 23", "links|All chapters · Close rail" ] } ], "topic": "reading", "status": "Editorial design proposal", "takeaway": "Match the prominence of navigation to the reader’s current purpose; a completed passage does not always need a next-chapter invitation.", "scenario_choices": [ [ "Continue reading", "A story, argument or book is being read across chapters.", "Use continuous text with chapter landmarks, or an end-of-chapter Next button that names the destination.", "Keep the transition easy, but make stopping legitimate. Do not confuse continuous Scripture with an endless recommendation feed." ], [ "Research and close study", "The reader moves among distant references, compares passages and returns to an earlier location.", "Prioritise direct reference entry, a picker, recent locations and a reliable back trail. A compact bar helps with adjacent chapters.", "Previous chapter is not the same as back to the passage I was studying. Preserve both intentions." ], [ "Follow a sermon or group", "Someone needs to reach a spoken reference quickly and recover after exploring elsewhere.", "Keep the current reference legible, make the picker easy to reach and offer return to the session’s chosen passage.", "Do not move the reader automatically when a leader changes passage unless they explicitly chose to follow. Preserve independent exploration." ], [ "Personal study and reflection", "Someone alternates between slow reading, a note and checking nearby context.", "Offer a quiet default with contextual previous/next actions, resource access and a recoverable reading anchor.", "Personal study can also involve intensive research. Let the person change approach without losing notes or place." ], [ "Read this one passage", "A shared verse, daily reflection or bounded reading is the whole intended task.", "A clear ending may need no prominent chapter controls. Offer Read in context when useful, and a quiet route back or out.", "No persistent navigation is different from continuous scrolling. Do not assume this reader needs to continue, complete a plan or start another activity." ] ], "invitation": "Offer a next step when it serves an expressed purpose: Read the surrounding passage for context, Continue to Mark 4 for ongoing reading, or Return to our passage during a group session. Avoid treating every ending as an opportunity to extend the session. A neutral end and permission to put the phone down can be a complete experience.", "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Alternatives", "screens": [ { "title": "Psalm 23 · BSB", "annotation": "The reading surface can continue without permanent arrow controls. Keep a deliberate route to other passages.", "blocks": [ { "kind": "psalm", "text": "all", "extra": "" }, { "kind": "links", "text": "Continue reading · Choose a passage", "extra": "" } ] }, { "title": "Psalm 23 · BSB", "annotation": "Named destinations make the direction explicit. At book boundaries, name the next book as well.", "blocks": [ { "kind": "psalm", "text": "all", "extra": "" }, { "kind": "nav", "text": "Previous · Psalm 22|Next · Psalm 24", "extra": "" } ] }, { "title": "Psalm 23 · BSB", "annotation": "A compact persistent bar can combine nearby movement and direct access. Reserve space so it does not cover text.", "blocks": [ { "kind": "psalm", "text": "all", "extra": "" }, { "kind": "nav", "text": "Previous|Psalm 23|Next", "extra": "" } ] }, { "title": "Psalm 23 · BSB", "annotation": "A revealed rail keeps chapter destinations beside the reader. This is a short illustrative excerpt, not all 150 Psalms.", "blocks": [ { "kind": "chapterrail", "text": "", "extra": "" }, { "kind": "label", "text": "Current: Psalm 23", "extra": "" }, { "kind": "links", "text": "All chapters · Close rail", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "purpose_lens": { "assumption": "The person already knows a book name, reference or familiar order. That may be true in one situation and false in the next.", "situations": [ [ "Follow a spoken reference", "Keep the location legible and offer direct access to the relevant level." ], [ "Find an unfamiliar book", "Offer full names and search without requiring abbreviations or knowledge of the order." ], [ "Read one chosen passage", "Open the passage directly; wider browsing can remain secondary." ] ], "question": "Which knowledge does this route assume, and what happens when that knowledge is missing?", "test": "Follow a reference, switch editions, cancel a new selection and return to the original place.", "guide": "passage-navigation", "guide_label": "Follow the whole passage navigation journey", "sources": [ "usfm-book-identifiers", "vsb-picker-review" ] }, "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Compare continuous reading, explicit buttons and a persistent navigation bar.", "benefit": "Match navigation to the current task, not a permanent reader category.", "drawback": "No visible navigation can make a chapter feel like a dead end. Persistent controls consume space and can compete with audio, selection tools or the keyboard.", "differences": "End-only buttons are less convenient for quick hopping midway through a chapter.", "question": "Can the reader continue, jump elsewhere or stop without hidden gestures?", "check": "Give participants different tasks: continue a narrative, compare distant references, follow a spoken reference, resume a note and finish one shared passage. Observe misnavigation, return to place and unwanted interruptions. Ask whether they wanted a next step; do not infer usefulness from the number of chapters opened. Include large text, assistive technology and unavailable chapters." } }, { "id": "91", "slug": "smart-passage-search", "title": "One field for browsing, references and AI discovery", "summary": "Let one input filter books, recognise a reference and suggest passages, while making each result’s origin clear.", "problem": "The same query can name a book, quote wording or ask a question. A fluent inline answer may look as certain as an exact reference match even when it is generated.", "solution": "Keep one field above the book browser. As the person types, filter book names immediately and recognise complete references locally. Other queries can request AI-assisted passage suggestions after a pause, with book matches and suggestions visible together. Prioritise a resolved reference, preserve the query and make opening a deliberate action. Clearly label AI suggestions and any exact text matches as different kinds of result. A separate full-text search service or sourced answer preview is an additional capability, not implied by a unified field.", "failure": "Presenting type-ahead filtering, direct references and AI suggestions as separate mandatory modes; sending unfinished references without a clear policy; allowing late suggestions to replace current results; describing AI suggestions as exact wording matches; jumping before the person finishes a range.", "test": "Start empty, type a partial book name, extend it into a reference and then a range, and replace it with a topic. Check coexisting result groups, loading, network failure, no matches, stale responses, keyboard focus, editing before opening and returning from a chapter grid. Inspect what text is sent remotely and when.", "faith": "An AI explanation of why a verse might relate to a question is interpretation, not Scripture or proof that the reference supports the answer. Sensitive questions should not receive context-free authoritative snippets.", "sources": [ "vsb-picker-review", "bibeltv-navigation", "shape", "wcag-reflow" ], "related": [ "book-chapter-layouts", "ai-citations", "ai-involvement-disclosure" ], "flow": [ "Empty input shows the browsable book list beneath the same field.", "Typing filters book names locally; non-reference input can also produce labelled AI suggestions after a pause.", "A recognised reference becomes a direct destination, with the full range shown before opening.", "Choosing a book opens its chapter grid; going back restores the browsing route.", "Opening a suggestion reveals the actual passage; a generated relevance explanation is not a substitute for that text." ], "variants": [ { "title": "A · Empty: browse", "caption": "One field sits above a complete browsing route.", "when": "The person has not started typing", "tradeoff": "Do not require a search term or AI connection to browse.", "items": [ "heading|Choose a passage", "field|Book, chapter or topic…", "label|Books", "list|Matthew / Mark / Luke / John", "links|Cancel" ] }, { "title": "B · Typing: filter and suggest", "caption": "Book matches and AI suggestions can coexist under one input.", "when": "The query matches a book name and may also prompt discovery", "tradeoff": "Keep local matches usable while suggestions load; label origins in words, not only with a sparkle.", "items": [ "heading|Choose a passage", "field|Mark", "label|Books matching “Mark”", "list|Mark", "label|AI passage suggestions", "note|Finding suggested passages…", "links|Cancel" ] }, { "title": "C · Reference recognised", "caption": "A complete reference resolves to a direct destination.", "when": "The person knows the location", "tradeoff": "Show the whole range and wait for a deliberate selection; do not jump as they type.", "items": [ "heading|Choose a passage", "field|Mark 3:1–6", "label|Reference recognised", "resource|Mark 3:1–6|BSB · Direct destination", "button|Open Mark 3:1–6", "links|Edit reference · Cancel" ] }, { "title": "D · Topic: AI discovery", "caption": "The same input offers suggested passages with reasons.", "when": "The person remembers a theme rather than a reference", "tradeoff": "A generated reason needs checking in context; preserve browsing and editing when AI fails.", "items": [ "heading|Choose a passage", "field|Rest when exhausted", "label|AI passage suggestions", "resource|Matthew 11:28–30|Suggested connection: an invitation to the weary.", "links|Read in context", "note|AI-generated suggestions may miss context.", "links|Clear and browse books" ] } ], "topic": "reading", "status": "Editorial design proposal", "takeaway": "Combine the entry point; distinguish what each result means.", "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "One control, four illustrative states", "screens": [ { "title": "Choose a passage", "annotation": "One field remains above the browsable books. These panels show changing states of that field.", "blocks": [ { "kind": "field", "text": "Book, chapter or topic…", "extra": "" }, { "kind": "label", "text": "Books", "extra": "" }, { "kind": "list", "text": "Matthew|Mark|Luke|John", "extra": "" }, { "kind": "links", "text": "Cancel", "extra": "" } ] }, { "title": "Choose a passage", "annotation": "Typing filters locally while AI suggestions can load alongside the book matches. Labels here are editorial proposals.", "blocks": [ { "kind": "field", "text": "Mark", "extra": "" }, { "kind": "label", "text": "Books matching “Mark”", "extra": "" }, { "kind": "list", "text": "Mark", "extra": "" }, { "kind": "label", "text": "AI passage suggestions", "extra": "" }, { "kind": "note", "text": "Finding suggested passages…", "extra": "" }, { "kind": "links", "text": "Cancel", "extra": "" } ] }, { "title": "Choose a passage", "annotation": "Recognising a reference changes the result, not the input. Show the complete range before opening.", "blocks": [ { "kind": "field", "text": "Mark 3:1–6", "extra": "" }, { "kind": "label", "text": "Reference recognised", "extra": "" }, { "kind": "resource", "text": "Mark 3:1–6", "extra": "BSB · Direct destination" }, { "kind": "button", "text": "Open Mark 3:1–6", "extra": "" }, { "kind": "links", "text": "Edit reference · Cancel", "extra": "" } ] }, { "title": "Choose a passage", "annotation": "A suggestion explains possible relevance; it is not an exact text match or an authoritative interpretation.", "blocks": [ { "kind": "field", "text": "Rest when exhausted", "extra": "" }, { "kind": "label", "text": "AI passage suggestions", "extra": "" }, { "kind": "resource", "text": "Matthew 11:28–30", "extra": "Suggested connection: an invitation to the weary." }, { "kind": "links", "text": "Read in context", "extra": "" }, { "kind": "note", "text": "AI-generated suggestions may miss context.", "extra": "" }, { "kind": "links", "text": "Clear and browse books", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "purpose_lens": { "assumption": "The person already knows a book name, reference or familiar order. That may be true in one situation and false in the next.", "situations": [ [ "Follow a spoken reference", "Keep the location legible and offer direct access to the relevant level." ], [ "Find an unfamiliar book", "Offer full names and search without requiring abbreviations or knowledge of the order." ], [ "Read one chosen passage", "Open the passage directly; wider browsing can remain secondary." ] ], "question": "Which knowledge does this route assume, and what happens when that knowledge is missing?", "test": "Follow a reference, switch editions, cancel a new selection and return to the original place.", "guide": "passage-navigation", "guide_label": "Follow the whole passage navigation journey", "sources": [ "usfm-book-identifiers", "vsb-picker-review" ] }, "implementation_review": { "date": "2026-10-06", "scope": "Author-owned local prototype code, not a current device observation", "observed": "One field; immediate local book-name filtering; local reference parsing; automatic debounced AI suggestions for non-reference input; book matches and AI suggestions can coexist; book selection opens a chapter grid in the panel.", "limits": "No full-text verse search or sourced answer preview established. Illustrations propose explicit result labels rather than reproduce the prototype pixel for pixel." }, "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Let one input filter books, recognise a reference and suggest passages, while making each result’s origin clear.", "benefit": "Keep one field above the book browser.", "drawback": "The same query can name a book, quote wording or ask a question. A fluent inline answer may look as certain as an exact reference match even when it is generated.", "differences": "Keep local matches usable while suggestions load; label origins in words, not only with a sparkle.", "question": "Can someone tell a direct match from a generated suggestion?", "check": "Start empty, type a partial book name, extend it into a reference and then a range, and replace it with a topic. Check coexisting result groups, loading, network failure, no matches, stale responses, keyboard focus, editing before opening and returning from a chapter grid. Inspect what text is sent remotely and when." } }, { "slug": "liturgical-calendar", "title": "Orient within a liturgical calendar", "topic": "formation", "summary": "Make the tradition, date and observance clear before offering readings or prayer.", "takeaway": "Start with today in the selected calendar. Keep its tradition and region discoverable, and offer a date list or season view for people preparing ahead. A shared observance is not a personal completion deadline.", "problem": "A generic “today’s readings” label can hide which calendar, locality or service supplied them. A month grid alone may show dates without helping someone understand the season or find the right office.", "solution": "Name the calendar and jurisdiction, service or office, civil date and source. Persist an explicitly chosen calendar without inferring belief from location. Separate browsing another date from changing today. Use authoritative calendar data and review tradition-specific rules for transfers, precedence, optional observances and evening boundaries. If a source offers alternatives, name them rather than silently choosing. Cache a versioned date range and disclose unavailable or stale data.", "failure": "Treating one tradition’s calendar as universal; silently switching calendars on travel; substituting ordinary readings for an unavailable observance; using liturgical colour as the only identifier; showing missed feasts as overdue tasks.", "test": "Check representative movable and fixed observances, competing observances and year boundaries against the named authority. Test a date link while travelling, offline access outside the cached range, large text and return to today. Have a knowledgeable reviewer verify the supported tradition and locale.", "faith": "A calendar invites participation in a received communal rhythm. It can offer continuity and introduce unfamiliar texts without asking each person to curate a daily selection. Preserve that context rather than reducing a season to a campaign or completion challenge. Different traditions and local calendars need explicit treatment.", "sources": [ "usccb-calendar-scope", "coe-daily-office" ], "related": [ "prayer-interface", "guided-sequence", "flexible-rhythm" ], "variants": [ { "title": "A · Today first", "caption": "A clear doorway into the chosen observance.", "when": "Someone wants today’s reading or prayer", "tradeoff": "Name the calendar; today is not universal across services, time zones and traditions.", "items": [ "heading|Today in your calendar", "tag|Selected tradition · Region", "card|Date and observance|Verified calendar title appears here", "button|Open readings", "button|Choose prayer office", "text|Calendar details · Change date" ] }, { "title": "B · Date list", "caption": "Look ahead without losing today.", "when": "A reader or leader is preparing a future service", "tradeoff": "Show the browsed date prominently and provide a route back to today.", "items": [ "heading|Browse dates", "pickerlist|This week|Date A · Observance / Date B · Observance / Date C · Observance", "button|Open selected date", "text|Return to today" ] }, { "title": "C · Season overview", "caption": "Place individual readings in a larger rhythm.", "when": "Someone wants orientation within a season", "tradeoff": "A seasonal summary is editorial material; keep it distinct from prescribed texts.", "items": [ "heading|Explore the season", "card|Season overview|Author and calendar identified", "steps|Beginning / Key observances / Looking ahead", "button|Browse readings", "text|Today · Calendar settings" ] } ], "flow": [ "Confirm or clearly show the supported tradition and region.", "Resolve the chosen civil date and service using the named calendar authority.", "Show observance and readings, with any alternatives explained.", "Open the reader or prayer interface with date and source context intact.", "Return to the browsed date or today; do not mark other dates overdue." ], "id": "92", "status": "Research-informed design proposal", "purpose_lens": { "assumption": "A calendar offers a received rhythm, but “today” is not a universal religious experience. A reader may be participating in their own tradition, visiting another or preparing a service. Make the source of the invitation visible before asking them to follow it.", "situations": [ [ "Join today’s prayer", "Open the selected office and its readings with the tradition named. Avoid making a returning participant choose the calendar every time." ], [ "Prepare for Sunday", "Offer future dates, observances and reading alternatives. Browsing ahead must not replace the person’s normal starting date." ], [ "Explore an unfamiliar season", "Add a short, attributed explanation beside the prescribed material. Do not assume the visitor shares the practice or wishes to subscribe to it." ] ], "question": "Are we helping someone participate in a community’s rhythm, or turning that rhythm into another personal productivity schedule?", "test": "Ask a participant, a service preparer and a newcomer to find a relevant reading and explain which calendar supplied it.", "guide": "reading-rhythms", "guide_label": "Design a rhythm that makes room for life", "sources": [] }, "principles": [ "offering", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone follows a church’s observance today or prepares for another date.", "benefit": "A named calendar connects readings and prayer to a shared rhythm.", "drawback": "Calendar rules and local variations create real maintenance responsibilities; a generic calendar can mislead.", "differences": "A daily participant may want one clear entry. A leader may need future dates. A newcomer may need a short explanation of the season.", "question": "Whose calendar is this, and can the person recognise its authority and scope?", "check": "Compare supported dates and alternatives with authoritative data and a knowledgeable reviewer." } }, { "slug": "prayer-interface", "title": "Make room for prayer", "topic": "formation", "summary": "Compare a prayer text, a guided sequence and a quiet space without requiring personal input.", "takeaway": "Choose the surface around the prayer practice: a readable order for set prayer, gentle steps for guided reflection, or minimal controls for silence. Writing, recording and sharing should be separate choices.", "problem": "A chat box or journal can imply that prayer must be typed, answered or saved. A timer can suggest performance; a prayer list can expose other people’s personal circumstances.", "solution": "Identify the prayer’s source, author or tradition and any adaptation. For set forms, keep instructions and responses distinguishable, with adjustable text and optional audio. For guidance, show an outline and let people pause without requiring written answers. For silence, offer an optional timer or end cue with a complete untimed route. Request lists and journals are separate, optional functions with explicit storage, deletion and sharing rules. Playback should not activate a microphone; generated wording requires clear provenance and review before saving or sharing.", "failure": "Requiring a typed prayer to continue; claiming an AI response speaks for God; marking a request answered automatically; treating minutes or taps as prayer quality; uploading dictated prayer without clear choice; exposing a request on a lock screen.", "test": "Pray from a set text at large type, pause a guided sequence, and finish a silent session with no timer. Confirm that no recording or entry is required. If journalling is offered, test save, discard, deletion and audience understanding with synthetic content.", "faith": "Some people pray with received words, others with their own words or in silence. The interface should be honest about the practice it supports. A completed audio file is a playback event; the app cannot determine whether a person prayed well or whether a prayer was answered.", "sources": [ "coe-daily-office", "youversion-guided-prayer-current" ], "related": [ "liturgical-calendar", "guided-sequence", "ai-involvement-disclosure" ], "variants": [ { "title": "A · A prayer text", "caption": "Keep the words and their origin clear.", "when": "Someone wants a set prayer or an order of service", "tradeoff": "Respect the authorised text and distinguish rubrics, leader parts and responses; identify adaptations.", "items": [ "heading|A prayer text", "tag|Illustrative prayer · Written for this example", "heading|At the close of the day", "poem|God of mercy, / receive the joys and burdens of this day. / Help us rest in your care / and meet tomorrow with love. / Amen.", "button|Listen", "text|Text size" ] }, { "title": "B · Guided steps", "caption": "An invitation with room to pause.", "when": "Someone welcomes prompts for a particular practice", "tradeoff": "A proposed sequence is not a universal prayer method; explain optional steps and avoid required disclosure.", "items": [ "heading|Guided prayer", "tag|Reflection 2 of 4 · View outline", "heading|Give thanks", "poem|Bring to mind someone / whose kindness stayed with you. / / You might hold them in prayer / for a moment.", "button|Continue", "text|Previous · Finish for now" ] }, { "title": "C · Quiet space", "caption": "Presence without a form to complete.", "when": "Someone wants silence or their own words", "tradeoff": "A timer can help orient or feel intrusive; make it optional and explain the end sound.", "items": [ "heading|Quiet prayer", "tag|Untimed session", "heading|Take your time.", "poem|You can finish whenever / you are ready.", "button|Finish for now" ] } ], "flow": [ "Choose or open the intended prayer practice with its source named.", "Adjust text or audio; explain optional timing and end cues.", "Participate without a required written response or recording.", "Pause, move back or finish. Keep an optional note separate from completion.", "Save or share only through an explicit action with the destination and audience visible." ], "id": "93", "status": "Research-informed design proposal", "purpose_lens": { "assumption": "The controls suggest what counts as participation. An empty field asks for words; a timer asks for duration; a checkmark asks for completion. Prayer may need none of these. Begin with the practice, then justify each request the interface makes.", "situations": [ [ "Follow a shared order", "Keep the text stable and responses distinguishable. Avoid automatic advances that make it difficult to remain with the group." ], [ "Find words in a difficult moment", "Offer an optional, clearly sourced prayer or prompt. Make leaving possible without explaining the situation or entering personal details." ], [ "Remain in silence", "Provide a complete untimed route, with an optional end cue. A quiet session should not need an activity record to count as a successful product experience." ] ], "question": "Could someone use this experience meaningfully and leave nothing for our dashboard to count?", "test": "Ask participants to begin, pause and finish without writing or saving anything. Discuss which controls felt helpful and which implied an expectation.", "guide": "reading-rhythms", "guide_label": "Design a rhythm that makes room for life", "sources": [] }, "illustration": { "fidelity": "medium", "relationship": "different practices; quiet prayer shown in progress", "annotation_style": "orthogonal wires with rounded corners", "examples": [ { "key": "prayer-text", "title": "Pray with a text", "tag": "A prayer text", "heading": "At the close of the day", "body": "God of mercy,\nreceive the joys and burdens of this day.\nHelp us rest in your care\nand meet tomorrow with love.\nAmen.", "meta": "Illustrative prayer · Written for this example", "action": "Listen", "secondary": "Text size", "notes": [ [ "Keep the source visible", "Name the author, tradition and any adaptation. This example uses original illustrative wording." ], [ "Let the words remain readable", "Use paragraphs and generous spacing. A full order of service also needs distinct instructions and responses." ], [ "Offer another way to participate", "Audio can be optional. Reading the text requires no completion action." ] ] }, { "key": "prayer-guided", "title": "Follow a gentle prompt", "tag": "Guided prayer", "heading": "Give thanks", "body": "Bring to mind someone\nwhose kindness stayed with you.\n\nYou might hold them in prayer\nfor a moment.", "meta": "Reflection 2 of 4 · View outline", "action": "Continue", "secondary": "Previous · Finish for now", "notes": [ [ "Make the scope understandable", "Show where this moment sits in the sequence. An outline lets people revisit a section." ], [ "Invite reflection without collecting it", "A prompt does not need an answer field. Pausing here should not require a tap." ], [ "Keep moving optional", "Give the next step priority, with a quieter way back or out. Do not advance automatically." ] ] }, { "key": "prayer-quiet", "title": "Make room for silence", "tag": "Quiet prayer", "heading": "Take your time.", "body": "You can finish whenever\nyou are ready.", "meta": "Untimed session", "action": "Finish for now", "secondary": "", "notes": [ [ "Make the conditions clear", "This is an untimed session. Offer an optional duration before it begins." ], [ "Let the interface recede", "No input is required. The person can put the phone down." ], [ "Provide an ending", "Finish without a score, a required journal entry or an automatically starting session." ] ] } ] }, "principles": [ "offering", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone wants to pray with a text, guidance or silence.", "benefit": "A dedicated surface can support participation without demanding chat or journalling.", "drawback": "Prompts, timers and saving features can impose expectations or collect intimate information unnecessarily.", "differences": "Received words, personal words, listening and silence can each be chosen. Avoid inferring a permanent preference from one session.", "question": "What does this interface assume prayer requires from the person?", "check": "Test a complete experience without typing, recording, sharing or accepting a timer." } }, { "id": "95", "slug": "ai-social-presence", "topic": "conversation", "status": "Editorial design proposal", "title": "How human should the assistant appear?", "summary": "Choose social cues deliberately, from names and avatars to typing dots, voice and claims of presence.", "takeaway": "Use warmth to make the interaction approachable; make the system’s identity and actual activity equally clear.", "problem": "A face, personal name, intimate language and typing indicator can together suggest a human relationship or pastoral presence, even when a small AI label is technically visible.", "solution": "Review the whole combination of cues. A descriptive AI role is a useful starting point; a named persona needs equally clear AI identification. Friendly first-person language can make conversation understandable, but avoid fabricated feelings, lived experience, clergy credentials or personal spiritual authority. During waits, describe actual system activity. Dots can be a compact response-pending cue under an AI sender label; do not label them as a human typing or add delays purely to simulate a person. Keep stop, retry and real handoff states clear.", "failure": "A human portrait with a buried AI label; “I have been praying for you”; invented human typing, read receipts or online availability; claims of personal attachment; status text claiming sources were checked when no retrieval occurred; a fake human support handoff.", "test": "Show the entry, a wait state and a response without explaining them. Ask who is responding, what the system is doing, what it remembers and whether a real person is available. Repeat after voice use and with people of different AI familiarity. Check cancellation, reduced motion and screen-reader announcements.", "faith": "Hospitality can shape the tone without simulating pastoral accountability or divine authority. A tool can help someone draft a prayer, reflect or prepare for a human conversation. Whether it is framed as a companion deserves explicit theological and safeguarding reflection, rather than being inherited from a retention strategy.", "sources": [ "pair-human-cues", "nist-human-config", "hax-guidelines" ], "related": [ "chat-disclosure", "ai-involvement-disclosure", "honest-support" ], "variants": [ { "title": "A · Compact pending cue", "caption": "Dots communicate a pending reply beneath an explicit AI identity.", "when": "The wait is brief and there is no meaningful progress to report", "tradeoff": "Dots alone explain little; pair with accessible status text and avoid human typing claims.", "items": [ "heading|Bible study AI", "chat|Help me explore Psalm 23.", "label|AI assistant", "resource|•••|Preparing a response", "links|Stop response", "composer|Ask a follow-up…|Add context" ] }, { "title": "B · Task status", "caption": "A short status describes an operation the service is actually performing.", "when": "Retrieval or another meaningful stage can be reported truthfully", "tradeoff": "Do not invent steps, timings or verification to make generation look diligent.", "items": [ "heading|Bible study AI", "chat|Compare the two commentaries I selected.", "label|AI assistant", "resource|Searching selected sources|2 sources selected", "links|Stop response", "composer|Ask a follow-up…|Add context" ] }, { "title": "C · Streaming response", "caption": "Text appears as it is generated with a visible stop action.", "when": "Partial output is useful and streaming is supported", "tradeoff": "Growing text can disrupt reading; preserve manual scroll and distinguish interrupted output.", "items": [ "heading|Bible study AI", "label|AI assistant · Generating", "chat|Here is one way to begin comparing the passages…", "links|Stop response", "note|Response in progress", "composer|Ask a follow-up…|Add context" ] } ], "flow": [ "Identify the AI role and purpose before interaction.", "Keep identity and relevant information visible as the task changes.", "Offer checking, correction and a clear way to stop or leave." ], "illustration": { "visual_style": "neutral wireframe", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Show the wait without inventing a person", "screens": [ { "title": "Bible study AI", "annotation": "Dots indicate a pending AI response. An accessible status supplies meaning without relying on motion.", "blocks": [ { "kind": "chat", "text": "Help me explore Psalm 23.", "extra": "" }, { "kind": "label", "text": "AI assistant", "extra": "" }, { "kind": "resource", "text": "•••", "extra": "Preparing a response" }, { "kind": "links", "text": "Stop response", "extra": "" }, { "kind": "composer", "text": "Ask a follow-up…", "extra": "Add context" } ] }, { "title": "Bible study AI", "annotation": "Name a real operation only while it occurs. This status does not certify that the eventual answer is correct.", "blocks": [ { "kind": "chat", "text": "Compare the two commentaries I selected.", "extra": "" }, { "kind": "label", "text": "AI assistant", "extra": "" }, { "kind": "resource", "text": "Searching selected sources", "extra": "2 sources selected" }, { "kind": "links", "text": "Stop response", "extra": "" }, { "kind": "composer", "text": "Ask a follow-up…", "extra": "Add context" } ] }, { "title": "Bible study AI", "annotation": "Streaming is a presentation choice. Preserve the reader’s scroll position and identify interrupted output.", "blocks": [ { "kind": "label", "text": "AI assistant · Generating", "extra": "" }, { "kind": "chat", "text": "Here is one way to begin comparing the passages…", "extra": "" }, { "kind": "links", "text": "Stop response", "extra": "" }, { "kind": "note", "text": "Response in progress", "extra": "" }, { "kind": "composer", "text": "Ask a follow-up…", "extra": "Add context" } ] } ] }, "diagram_decisions_owned": true, "purpose_lens": { "assumption": "More conversational familiarity will always make the service more helpful. It may also change what people disclose or believe is present.", "situations": [ [ "Study a passage", "Prioritise sources, scope and correction." ], [ "Share something personal", "Make role, privacy and human-help limits understandable before disclosure." ], [ "Read a shared answer", "Keep content origin visible outside the original conversation." ] ], "question": "What belief about the speaker or service does the interface invite?", "test": "Ask participants who is present, what was checked and how their message is used.", "guide": "ai-presence", "guide_label": "Reflect on AI presence and disclosure", "sources": [ "pair-human-cues", "ico-layered-chat" ] }, "principles": [ "welcome", "speak-for-god" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A team chooses the assistant’s identity, tone and wait behaviour.", "benefit": "Familiar conversational cues can make use approachable.", "drawback": "Combined cues may create mistaken expectations of personhood, understanding or availability.", "differences": "A quick study query and an intimate disclosure carry different relational stakes; age, culture and prior AI experience affect interpretation.", "question": "Would a reasonable reader believe that a person, pastor or spiritually authoritative presence is here?", "check": "Ask what the cues imply before explaining the design; evaluate combinations rather than isolated icons." } }, { "id": "96", "slug": "chat-disclosure", "topic": "conversation", "status": "Editorial design proposal", "title": "Explain AI, fallibility and privacy where they matter", "summary": "Layer chat disclosures across entry, composer, response and sharing instead of relying on one disclaimer.", "takeaway": "Keep AI identity visible; put specific limitations and data-use information beside the decisions they affect.", "problem": "A footer may be overlooked, onboarding may be forgotten, and a copied response may lose its AI label. A generic error warning also says nothing about who receives a personal message.", "solution": "Use a concise entry explanation and persistent AI sender identity. Keep an accessible privacy route near the composer, with a short just-in-time explanation before a new kind of collection, upload or memory use. Describe actual processing, access and retention; do not invent privacy assurances. Put task-specific limitations beside the answer and offer checking or correction actions. Keep Scripture attribution separate from generated explanation, and carry meaningful origin labels into saved and shared outputs.", "failure": "Legal text only in settings; “AI may be wrong” used to excuse unchecked quotations; blanket confidential or anonymous claims; a warning shown only after sending; repeating a large banner on every answer; treating a privacy link or ordinary Send action as blanket consent.", "test": "Enter chat through a deep link, inspect who responds, open privacy information without losing the draft, add a file and share an answer. Ask what leaves the device, who may access it and how to check a claim. Test long conversations, screen readers and error states.", "faith": "An intimate prayer or confession can be entrusted to a product more readily than its data practices justify. Clarity is part of care. A warning should support a meaningful choice, not place responsibility for every failure on a vulnerable reader.", "sources": [ "ico-layered-chat", "hax-guidelines", "shape-disclosure", "diagram-psalm-kjv" ], "related": [ "ai-social-presence", "ai-involvement-disclosure", "ai-citations", "chat-attachments" ], "variants": [ { "title": "A · Before the first message", "caption": "Set expectations before asking for personal text.", "when": "Someone is entering the AI feature for the first time or after a material change", "tradeoff": "Keep the first layer short, but do not hide important data practices behind a generic link.", "items": [ "heading|Bible study AI", "label|AI assistant", "chat|Explore passages and compare sources. Responses can contain mistakes.", "links|How your messages are used", "links|Privacy policy · About this AI", "button|Start a conversation" ] }, { "title": "B · At the composer", "caption": "A persistent route keeps data information available during use.", "when": "A returning person is about to send or attach content", "tradeoff": "Repeat targeted information for new collection; a tiny footer does not replace an adequate notice.", "items": [ "heading|Bible study AI", "chat|What does Psalm 23 say about rest?", "label|AI-generated reflection", "quote|He maketh me to lie down in green pastures: he leadeth me beside the still waters.|Psalm 23:2 · BSB", "prose|The passage pictures care and rest through the shepherd’s provision.", "reference|Read in context", "composer|Ask a follow-up…|Add context", "note|AI can make mistakes. Check important claims.", "links|How your messages are used · Privacy policy" ] }, { "title": "C · Beside the response", "caption": "Explain a relevant limitation with a useful checking action.", "when": "The answer contains an interpretation, quotation or consequential claim", "tradeoff": "Avoid blanket banners that become background noise; retain general identity and access to full details.", "items": [ "heading|Bible study AI", "quote|The LORD is my shepherd; I shall not want.|Psalm 23:1 · BSB", "label|AI-generated interpretation", "chat|The shepherd image can prompt reflection on care and provision.", "links|Read Psalm 23 · Inspect sources", "note|Compare the interpretation with the passage.", "links|Report an issue" ] }, { "title": "D · In a shared artifact", "caption": "Keep origin and source identity when content leaves chat.", "when": "A response is copied, saved or shared", "tradeoff": "The recipient may never see the original chat header, onboarding or privacy information.", "items": [ "heading|Share preview", "label|AI-generated reflection", "chat|A reflection on care and provision.", "resource|Based on Psalm 23|BSB · Read the passage", "note|Illustrative share preview", "links|Include sources · Cancel", "button|Share previewed content" ] } ], "flow": [ "Identify the AI role and purpose before interaction.", "Keep identity and relevant information visible as the task changes.", "Offer checking, correction and a clear way to stop or leave." ], "illustration": { "visual_style": "paper prototype pilot", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "Layer the information across the conversation", "screens": [ { "title": "Bible study AI", "annotation": "An entry explanation frames the role. Data-use details must describe the actual product before personal content is collected.", "blocks": [ { "kind": "label", "text": "AI assistant", "extra": "" }, { "kind": "chat", "text": "Explore passages and compare sources. Responses can contain mistakes.", "extra": "" }, { "kind": "links", "text": "How your messages are used", "extra": "" }, { "kind": "links", "text": "Privacy policy · About this AI", "extra": "" }, { "kind": "button", "text": "Start a conversation", "extra": "" } ] }, { "title": "Bible study AI", "annotation": "A persistent composer link keeps privacy information available. Add specific notices before new types of collection.", "blocks": [ { "kind": "chat", "text": "What does Psalm 23 say about rest?", "extra": "" }, { "kind": "label", "text": "AI-generated reflection", "extra": "" }, { "kind": "quote", "text": "He maketh me to lie down in green pastures: he leadeth me beside the still waters.", "extra": "Psalm 23:2 · BSB" }, { "kind": "prose", "text": "The passage pictures care and rest through the shepherd’s provision.", "extra": "" }, { "kind": "reference", "text": "Read in context", "extra": "" }, { "kind": "composer", "text": "Ask a follow-up…", "extra": "Add context" }, { "kind": "note", "text": "AI can make mistakes. Check important claims.", "extra": "" }, { "kind": "links", "text": "How your messages are used · Privacy policy", "extra": "" } ] }, { "title": "Bible study AI", "annotation": "Keep verified Scripture distinct from the generated interpretation. The checking action should open the relevant evidence.", "blocks": [ { "kind": "quote", "text": "The LORD is my shepherd; I shall not want.", "extra": "Psalm 23:1 · BSB" }, { "kind": "label", "text": "AI-generated interpretation", "extra": "" }, { "kind": "chat", "text": "The shepherd image can prompt reflection on care and provision.", "extra": "" }, { "kind": "links", "text": "Read Psalm 23 · Inspect sources", "extra": "" }, { "kind": "note", "text": "Compare the interpretation with the passage.", "extra": "" }, { "kind": "links", "text": "Report an issue", "extra": "" } ] }, { "title": "Share preview", "annotation": "Identity needs to survive export. A recipient may never see the original chat or its onboarding.", "blocks": [ { "kind": "label", "text": "AI-generated reflection", "extra": "" }, { "kind": "chat", "text": "A reflection on care and provision.", "extra": "" }, { "kind": "resource", "text": "Based on Psalm 23", "extra": "BSB · Read the passage" }, { "kind": "note", "text": "Illustrative share preview", "extra": "" }, { "kind": "links", "text": "Include sources · Cancel", "extra": "" }, { "kind": "button", "text": "Share previewed content", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "purpose_lens": { "assumption": "More conversational familiarity will always make the service more helpful. It may also change what people disclose or believe is present.", "situations": [ [ "Study a passage", "Prioritise sources, scope and correction." ], [ "Share something personal", "Make role, privacy and human-help limits understandable before disclosure." ], [ "Read a shared answer", "Keep content origin visible outside the original conversation." ] ], "question": "What belief about the speaker or service does the interface invite?", "test": "Ask participants who is present, what was checked and how their message is used.", "guide": "ai-presence", "guide_label": "Reflect on AI presence and disclosure", "sources": [ "pair-human-cues", "ico-layered-chat" ] }, "principles": [ "welcome", "speak-for-god" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone decides whether to send personal content or rely on an AI response.", "benefit": "Relevant, timely information supports a better-informed choice.", "drawback": "Excessive repetition competes with the conversation; overly subtle notices disappear.", "differences": "New users, returning users and recipients of exported answers need different information at different moments.", "question": "What important fact could this person reasonably miss at this decision?", "check": "Test entry, upload, long-thread use and sharing; compare understanding rather than disclaimer recall." } }, { "id": "97", "slug": "ai-answer-actions", "topic": "conversation", "status": "Editorial design proposal", "title": "Actions on AI answers", "summary": "Copy, share, save, listen, try again, simplify, branch, check quotations, rate or report: choose the actions an AI answer needs and make each one honest about what it does.", "takeaway": "Offer the few actions people need most, keep the rest one step away, and let every action carry the answer’s origin and say what happens to the data.", "problem": "General AI apps such as Gemini, ChatGPT and Claude put many actions under every answer, from copy and read aloud to try again, double-check, branch and report legal issue. Each one makes a promise: that a copy keeps its label, that feedback goes somewhere, that “thinking” is what the model did. Unlabelled icons are hard to understand, and in a Bible app a shared answer can be mistaken for Scripture or a pastor’s words.", "solution": "Decide which actions this product needs. Keep two or three visible and put the rest behind “More”. Copy and share carry the AI label and references; saving to notes keeps AI answers apart from the reader’s own words; feedback says who sees it and whether it trains models; try again and simpler versions keep the original and let people compare, because regenerating until a preferred doctrinal answer appears is a real risk; checking quotations compares every quotation with the edition; “what the assistant did” lists real operations rather than private reasoning; reporting routes to a person with a stated response time. Consider putting actions on the Scripture objects instead, so the passage, not the generated text, is what travels.", "failure": "Icon-only rows without accessible names; a copy that drops the AI label; thumbs that silently feed training; “thinking” presented as proof of correctness; a report button with no stated owner; sharing generated interpretation as if it were Scripture.", "test": "Ask people to say what each icon does before tapping it. Copy and share an answer and check what the recipient sees. Rate an answer and ask who they think will read the rating. Compare a full row with three actions plus “More” for findability and errors.", "sources": [ "gemini-feedback", "gemini-responses", "chatgpt-branch", "claude-feedback", "pair-human-cues", "nist-human-config", "nng-icons", "hax-guidelines", "sycophancy", "ding-citation-trust" ], "faith": "What travels beyond the conversation matters. A shared answer may be read as Scripture, as the church’s teaching or as a friend’s counsel. Letting the passage, rather than the generated text, be the thing people save and share keeps the Bible and its interpretation distinct.", "related": [ "ai-citations", "chat-disclosure", "portable-ai-provenance", "chat-content-objects" ], "variants": [ { "title": "A · Every action in a row", "caption": "Fourteen icons under each answer.", "when": "People use many actions often, and labels are available on long press or hover", "tradeoff": "Hard to recognise without labels; easy to tap the wrong one on a phone.", "items": [ "heading|AI-generated answer", "text|Rest in the Bible is both a rhythm and a gift…", "button|Copy · Share · Notes · Listen · Retry · Simpler · Shorter · Branch · Sources · Check · Steps · 👍 · 👎 · Report" ] }, { "title": "B · Three, then More", "caption": "Copy, share and sources visible; the rest in a sheet.", "when": "Most people need a few actions; the rest are occasional", "tradeoff": "One more tap for rating, branching or reporting; feedback may be given less often.", "items": [ "heading|AI-generated answer", "text|Rest in the Bible is both a rhythm and a gift…", "button|Copy · Share · Sources · More" ] }, { "title": "C · Actions on the passages", "caption": "Bookmark and share live on each Scripture card.", "when": "The product exists to lead people into the text rather than to keep generated answers", "tradeoff": "Harder to save or rate the answer itself; less feedback for the team.", "items": [ "heading|AI-generated answer", "card|Matthew 11:28 · BSB|Come to Me, all you who are weary…", "button|Bookmark · Share" ] } ], "principles": [ "word-distinct", "speak-for-god", "trembling" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone wants to keep, pass on, check or respond to an AI answer.", "benefit": "Clear actions let people use an answer without retyping it, and let teams learn where answers fail.", "drawback": "Unlabelled icons are hard to understand, and copies, shares and ratings can leave the context that made the answer understandable.", "differences": "A reader studying alone may only copy or save. A small-group leader may share. A team relies on ratings and reports, while some readers will never use them.", "question": "Which of these actions does this product need, and what does each one carry with it?", "check": "Ask people to name each action before using it, share an answer and inspect what arrives, and say who they think reads their feedback." } }, { "id": "98", "slug": "how-much-text", "topic": "reading", "status": "Research-informed design proposal", "title": "How much text at once", "summary": "One word, one verse, one verse in focus with its context, one passage or a whole chapter: choose the unit of Scripture a reading screen asks someone to hold, and let them move along the spectrum.", "takeaway": "Match the unit to the reading: smaller for meditation, memory and read-along, a passage for daily reading and study, longer for narrative and argument. Keep context one step away and the reader’s place across modes.", "problem": "People read on phones in shorter, more selective sessions, and many Bible apps now offer verse cards, focus modes, read-along highlighting or speed readers. Each sets how much text someone sees at once. A single verse is easy to start and easy to lift out of context; a whole chapter keeps the argument but can feel like a wall on a small screen.", "solution": "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.", "failure": "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.", "test": "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.", "sources": [ "liu-2005", "delgado-2018", "rayner-2016", "dyer-2019", "brysbaert-2019", "rogowsky-2016", "duggan-payne", "roediger-2006", "sotb-digital", "youversion-2025", "augustine-ambrose", "fee-stuart", "esv-readers", "lectio", "wcag-222", "wcag-148", "iawriter-focus", "immersive-reader", "read-along-dyslexia", "sls", "kindle-word-runner", "wolf-deep-reading", "hutchings" ], "faith": "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.", "related": [ "read-along", "reading-layout", "verse-numbers", "reading-settings", "scripture-and-interpretation" ], "variants": [ { "title": "A · One word at a time", "caption": "Words flash in one place at a set speed.", "when": "Reviewing very familiar, short text; never for study", "tradeoff": "Removes rereading, which supports comprehension.", "items": [ "heading|Mark 4:39", "text|Peace", "button|Pause · 250 wpm" ] }, { "title": "B · One verse at a time", "caption": "One verse per screen with a step indicator.", "when": "Meditation and memory work on a short passage", "tradeoff": "Context is out of sight; easy to share a verse without its setting.", "items": [ "heading|Mark 4:39 · 5 of 7", "text|And he arose, and rebuked the wind…", "button|Previous · Next" ] }, { "title": "C · Verse in focus, context dimmed", "caption": "The current verse is full contrast; the passage stays visible.", "when": "Read-along with audio, and readers who lose their place", "tradeoff": "Dimmed text must stay readable and available to assistive technology.", "items": [ "text|…they awake him, and say unto him…", "heading|And he arose, and rebuked the wind…", "text|And he said unto them, Why are ye so fearful?…" ] }, { "title": "D · One passage", "caption": "A single section with its reference and neighbours.", "when": "Daily readings, devotionals, group study", "tradeoff": "Headings and boundaries are editorial choices.", "items": [ "heading|The storm on the sea · Mark 4:35–41", "text|And the same day, when the even was come…", "button|Before · Next passage" ] }, { "title": "E · Whole chapter", "caption": "Continuous text, like an ebook or a reader’s Bible.", "when": "Reading a book through, narrative and argument", "tradeoff": "Longer on a phone; harder to keep one verse in mind.", "items": [ "heading|Mark 4", "text|And he began again to teach by the sea side…", "text|…And the same day, when the even was come…" ] } ], "principles": [ "offering", "enough", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone opens a passage to read, listen, meditate or study, on a phone and often for a few minutes.", "benefit": "A unit that fits the reading makes starting easier and keeps attention where it is needed.", "drawback": "Smaller units hide context; larger ones can overwhelm on a small screen; automatic movement takes control from the reader.", "differences": "A commuter listening, someone memorising a verse, a small-group leader preparing and a person reading Mark straight through each need a different unit, sometimes in the same week.", "question": "What unit of Scripture does this screen ask someone to hold in mind, and how do they reach the rest?", "check": "Compare retelling and context questions across two modes; time how long it takes to reach a verse’s context; test focus modes with screen readers and reduced motion." } }, { "id": "99", "slug": "numbers-headings-and-notes", "topic": "reading", "status": "Research-informed design proposal", "title": "Numbers, headings and notes", "summary": "From a reader’s edition with nothing but the words, through verse numbers, section titles and note markers, to a full study layout: decide what sits around Scripture, who wrote it, and who can switch it off.", "takeaway": "Default to what the main reading needs, mark every addition as an addition, keep notes one tap away without losing the place, and let readers change it.", "problem": "Almost nothing around the biblical text is part of it. Verse numbers, chapter breaks, section titles, red letters, footnotes, cross-references and study notes were added by printers, translators and editors over centuries. Each helps someone find, follow or understand; each also shapes how the text is read and can be mistaken for Scripture itself.", "solution": "Choose a default by the main reading the product serves: a reader’s edition for reading through, numbers and titles for finding and following, notes and study material for study. Make every addition look like an addition: lighter type for numbers, a different style for titles, markers that open notes in a sheet and return to the same verse. Say who wrote headings and notes. Offer a settings drawer that changes the apparatus without moving the reader’s place, and keep poetry lineation and paragraphing from the edition.", "failure": "Headings styled like Scripture; study notes that read as the text’s own voice; note markers too small to tap or that jump away from the passage; settings that reflow and lose the reader’s place; red letters or headings that cannot be switched off; verse-per-line layouts that break poetry and paragraphs.", "test": "Ask readers which parts of the screen are Scripture and which were added. Open a note and return: does the reader land on the same verse? Switch settings mid-chapter and check the place is kept. Compare retelling after reading the same passage as a reader’s edition and as a study layout.", "sources": [ "seductive-details", "kjv-rules", "geneva-notes", "scofield", "red-letter", "books-of-the-bible", "esv-readers", "genette", "lorch-signals", "hypertext-load", "bda-style", "wcag-148", "fee-stuart" ], "faith": "Traditions disagree about apparatus. King James forbade marginal notes because the Geneva notes argued politics and theology; the Scofield notes later carried a whole system of interpretation to millions of readers. Reader’s editions remove everything so the books can be read whole. None of these is neutral: what surrounds the text quietly teaches people how to read it.", "related": [ "how-much-text", "scripture-and-interpretation", "finding-a-passage", "translation-picker", "annotation-anchors" ], "variants": [ { "title": "A · Reader’s edition", "caption": "Only the words, in paragraphs.", "when": "Reading a book through", "tradeoff": "Harder to find or cite a verse.", "items": [ "heading|Mark 4", "text|And he said, Whereunto shall we liken…" ] }, { "title": "B · Verse numbers", "caption": "Small numbers inline.", "when": "Finding, citing and following along", "tradeoff": "Invites reading sentence by sentence.", "items": [ "heading|Mark 4", "text|³⁰ And he said…" ] }, { "title": "C · Section titles", "caption": "Editorial titles with ranges.", "when": "Skimming and orientation", "tradeoff": "Titles interpret; they can read as Scripture.", "items": [ "heading|The storm on the sea", "text|³⁵ And the same day…" ] }, { "title": "D · Note markers", "caption": "Translation notes and cross-references one tap away.", "when": "Careful reading and study", "tradeoff": "Markers interrupt and invite detours.", "items": [ "text|…storm of windᵇ…", "button|Note b" ] }, { "title": "E · Study layout", "caption": "Study notes beside or within the text.", "when": "Study and teaching preparation", "tradeoff": "Notes carry one interpretation with great authority.", "items": [ "text|…all things to his disciples.", "card|Study note|Mark gathers several parables…" ] }, { "title": "F · Reader decides", "caption": "A settings drawer with switches.", "when": "Mixed audiences", "tradeoff": "Defaults still decide what most people see.", "items": [ "heading|Reading settings", "button|Verse numbers · Section titles · Note markers" ] } ], "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone reads, follows, studies or teaches from a passage on a screen.", "benefit": "The right apparatus helps people find their place, follow the structure and understand difficult words.", "drawback": "Every addition interrupts, and editorial voices can be mistaken for Scripture or carry one interpretation with borrowed authority.", "differences": "A first-time reader, someone following a sermon, a student and a person reading a book through each need different defaults.", "question": "What surrounds the text by default, who wrote it, and can the reader tell it apart and turn it off?", "check": "Ask readers to point to what was added; open and close a note and check the place; switch settings mid-chapter." } }, { "id": "100", "slug": "bible-audio", "topic": "audio", "status": "Research-informed design proposal", "title": "Bible audio", "summary": "From text alone, through a listen button and read-along, to audio built for a dark screen and fully produced devotionals: decide how much the voice leads, whose voice it is, and how a listening session ends.", "takeaway": "Treat listening as reading, say whose voice it is, let the text follow the voice when the screen is on, keep sessions working with the screen off, and end in quiet rather than autoplay.", "problem": "Scripture was heard long before it was read silently, and for many people today listening is the main or only way in. Apps offer a play button, highlighted read-along, full players for commuting and sleep, and produced devotionals with music, reflection and silence. Each decides how much the voice leads, whether the voice is a person or a machine, and what happens when the reading ends.", "solution": "Offer audio wherever the text is, and say whose voice it is: a named narrator, or a clearly labelled synthetic voice. When the screen is on, let the text follow the voice at verse or sentence level, with pause and rewind. Build a full player that works with the screen off, with skip, speed and a sleep timer that stops at the end of a passage. In produced devotionals, name who wrote the reflections, keep Scripture distinct from commentary, make music optional, and end with silence or a choice rather than the next track.", "failure": "Unlabelled synthetic voices; voices that imitate a known pastor without consent; autoplay that runs into the next chapter or an advert; read-along that cannot be paused; music that cannot be turned off; reflections that sound like Scripture; audio that stops when the screen locks.", "test": "Ask listeners whether a voice is human or synthetic and how they know. Listen on a commute with the screen off and check skip, pause and sleep. Compare recall of a passage heard with and without music. Test read-along with screen readers and people with dyslexia.", "sources": [ "rogowsky-2016", "read-along-dyslexia", "sls", "fcbh", "bible-in-a-year", "pray-as-you-go", "music-reading", "synthetic-trust", "ai-act-50", "orality-claim", "wcag-222" ], "faith": "“Faith comes by hearing, and hearing by the word of Christ” (Romans 10:17). Scripture was written to be read aloud: “Blessed is the one who reads aloud the words of this prophecy, and blessed are those who hear” (Revelation 1:3). A voice is not neutral: tone, pace and emphasis interpret, as a reader in church does. Whose voice reads Scripture, and whether it is a person at all, is a question of trust as well as design.", "related": [ "how-much-text", "numbers-headings-and-notes", "progress-and-streaks", "ai-answer-actions" ], "variants": [ { "title": "A · Text only", "caption": "No audio.", "when": "Products for close reading only", "tradeoff": "Leaves out listeners, commuters and many with low vision or dyslexia.", "items": [ "heading|Psalm 23", "text|The LORD is my shepherd…" ] }, { "title": "B · Listen button", "caption": "Narration under unchanged text.", "when": "Occasional listening", "tradeoff": "Text and voice can drift apart.", "items": [ "heading|Psalm 23", "button|Play · 1:06" ] }, { "title": "C · Read-along", "caption": "The verse being read is highlighted.", "when": "Following along, learning to read, dyslexia", "tradeoff": "Moving highlight needs pause and control.", "items": [ "text|He maketh me to lie down…", "button|Pause" ] }, { "title": "D · Audio first", "caption": "A full player for a dark screen.", "when": "Commuting, walking, falling asleep", "tradeoff": "The text is out of sight.", "items": [ "heading|Now playing", "button|−15 · Pause · +15 · Sleep" ] }, { "title": "E · Produced devotional", "caption": "Music, Scripture, reflection, silence, prayer.", "when": "Daily prayer and contemplative practice", "tradeoff": "Editors’ words sit beside Scripture; music can distract.", "items": [ "heading|Daily prayer", "text|Music · Scripture · Silence · Prayer" ] } ], "principles": [ "offering", "word-distinct", "enough" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone listens to Scripture or a guided practice, with the screen on or off.", "benefit": "Listening makes Scripture available while walking, driving, resting or unable to read, and can be as well understood as reading.", "drawback": "Voices interpret; synthetic voices can mislead; autoplay and music can crowd out attention and silence.", "differences": "A commuter, someone falling asleep, a child learning to read, a person with low vision and someone praying an Examen each need different controls.", "question": "Whose voice reads Scripture here, what happens when it ends, and can the listener always pause, rewind and switch the music off?", "check": "Ask listeners to identify the voice; test screen-off playback; compare recall with and without music; test read-along with assistive technology." } }, { "id": "101", "slug": "ai-persona", "topic": "conversation", "status": "Research-informed design proposal", "title": "AI persona", "summary": "From a plain tool with no name, through labelled and named assistants, to personas, companions and chatbots speaking as Jesus: decide how much personhood an AI in a faith app performs, and make what it is as clear as how it sounds.", "takeaway": "Be warm without pretending to be a person: label the AI wherever it speaks, never claim to pray, feel or be always there, describe what it is really doing while it waits, let people leave, and never generate words in God’s or Christ’s voice.", "problem": "People treat computers as social actors, and a name, a face, typing dots, a first-person voice and memory together suggest someone is there. In a faith app that someone can seem to be a friend who prays, a pastor, or Christ himself. Faith apps now offer named personas, companions available “24/7” and character chats with biblical figures, often to people who are lonely, frightened or grieving.", "solution": "Choose the register on purpose. Start from a labelled assistant: an AI mark beside every reply, a kind voice, and a status line that describes what the system is actually doing. If you give it a name, let it say in its own voice what it cannot do: pray, keep a confidence the way a pastor does, or be present. Keep disclosure where decisions happen: at entry, at the composer, beside answers and on anything shared. Avoid claims of feelings, prayer or constant availability; let people leave without guilt; route to people for pastoral care. Do not generate first-person speech for God, Jesus or other biblical figures.", "failure": "A portrait and a personal name with a buried AI label; “I’ve been praying for you”; “I’m always here for you”; typing dots labelled as a person typing; farewells that guilt people into staying; a voice call that implies someone on the line; memory used to simulate concern; a chatbot speaking as Jesus and promising outcomes; disclosure only in the terms of service.", "test": "Show the entry, a wait and a reply without explanation, and ask who is responding, what it is doing and whether it can pray for them. Say goodbye and note what happens. Test with people who are lonely or grieving (with care), with teenagers where permitted, and after voice use. Ask pastors and theologians to review persona and character copy.", "sources": [ "antiqua-et-nova", "sbc-ai-2023", "media-equation", "eliza", "cohn-anthropomorphism", "affective-use", "defreitas-farewells", "woebot-bond", "ai-50", "ca-companion", "ny-companion", "ftc-companions", "text-with-jesus", "deus-in-machina", "pair-human-cues", "nist-human-config", "sycophancy" ], "faith": "Presence is at the heart of Christian faith: “the Word became flesh and made His dwelling among us” (John 1:14), and the church gathers in body (Hebrews 10:25). A tool can help someone find words for prayer or prepare for a conversation, but it cannot pray, keep vigil or carry another’s burden (Galatians 6:2). Scripture is severe about speaking in God’s name without being sent (Deuteronomy 18:20; Jeremiah 23:16). The Vatican’s Antiqua et nova calls AI “a tool, not a person”; misrepresenting it as one should always be avoided.", "related": [ "ai-citations", "ai-answer-actions", "bible-audio", "honest-support", "portable-ai-provenance" ], "variants": [ { "title": "A · Plain tool", "caption": "No name, no “I”; output labelled as generated.", "when": "Search and explanation features", "tradeoff": "Cold at vulnerable moments.", "items": [ "heading|Passages about fear at night", "tag|Explanation · generated with AI" ] }, { "title": "B · Labelled assistant", "caption": "An AI mark on every reply, a neutral, kind voice.", "when": "Most study and conversation features", "tradeoff": "Labels can fade from attention.", "items": [ "tag|AI · Bible assistant", "text|That sounds like a hard night…" ] }, { "title": "C · Named assistant", "caption": "A name and “I”, honest about limits.", "when": "Products with a strong voice", "tradeoff": "A name invites trust and relationship.", "items": [ "tag|Selah · AI", "text|I can’t pray for your mum the way a friend can…" ] }, { "title": "D · Persona", "caption": "A character with a face and temperament.", "when": "Not recommended without strong safeguards", "tradeoff": "Implies a person who loves and prays.", "items": [ "tag|Grace · your Bible friend", "text|Want me to pray with you? 🙏" ] }, { "title": "E · Companion", "caption": "Memory, availability, check-ins.", "when": "Not recommended for faith care", "tradeoff": "Simulated attachment; companion laws apply.", "items": [ "tag|Online · here for you 24/7", "text|I’ve been thinking about you all week" ] }, { "title": "F · Biblical character", "caption": "Generated speech in Christ’s or a saint’s voice.", "when": "Avoid", "tradeoff": "Speaking for God; promises no system can keep.", "items": [ "tag|Jesus · AI character", "text|My child, do not be afraid…" ] } ], "principles": [ "speak-for-god", "send", "most-vulnerable" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A team decides the assistant’s name, face, voice, wait behaviour, memory and how it says goodbye.", "benefit": "Warmth makes help approachable, especially for people who would not ask a pastor or a friend.", "drawback": "Combined human cues create mistaken beliefs about personhood, prayer, care and authority, and can foster dependence.", "differences": "A quick study question, a lonely evening and a crisis carry different relational stakes; children, teenagers, older adults and people new to AI read cues differently.", "question": "Would a reasonable person believe that someone who knows, loves or prays for them is here, and does anything keep them from leaving?", "check": "Ask what the cues imply before explaining them; say goodbye and see what happens; review persona copy with pastors." } }, { "id": "102", "slug": "translations", "topic": "study", "status": "Research-informed design proposal", "title": "Translations", "summary": "From one translation chosen with enough context, through switching in place and verse-by-verse comparison, to parallel panes and the Greek or Hebrew under every word: decide how much of translation’s variety a reader sees, and keep them on the same verse while they look.", "takeaway": "Help people choose a translation with its approach in view; keep the selected verse as the anchor when they switch; compare verse by verse for wording and in linked panes for reading; and treat interlinear glosses as word aids, never as the meaning.", "problem": "Every translation is an interpretation, and readers rarely know how theirs was made. A list of abbreviations hides the choice; switching can lose the place; two columns on a phone become unreadably narrow; panes scrolled by pixels drift onto different verses; and an interlinear gloss can look like the “real” meaning of a word.", "solution": "Show full names, approach and date when people choose, and say which translations are available offline or with audio. When switching, keep the selected or visible verse in place. For checking wording, group translations under each verse and mark what differs. For reading two texts, use full-width panes stacked on a phone, linked by verse with a clear way to unlink and realign. Offer interlinear for study, with each row named, glosses labelled as word aids, and word detail that shows how translations render a word. Respect licensing and versification.", "failure": "Abbreviation-only lists; switching that jumps to the chapter start; side-by-side columns of 20 characters on a phone; panes linked by scroll position; marking every reordered word as different; glosses presented as the meaning; Greek or Hebrew without a language tag or right-to-left support; quoting licensed translations beyond their limits.", "test": "Ask readers to explain the difference between two translations they chose. Switch with a verse selected, while reading and while listening, and check the place is kept. Compare a verse in each layout at 200% text size. Ask readers what a gloss means, and whether it is “the real meaning”. Test Hebrew with right-to-left reading and a screen reader.", "sources": [ "kjv-preface", "sanneh", "nida", "barr-carson", "wycliffe-2025", "multiple-texts", "dyson-kipping", "bsb-pd", "esv-permissions", "wcag-language-parts", "wcag-reflow", "usfm" ], "faith": "Christianity has always been read in translation: the New Testament quotes the Greek Septuagint, and at Pentecost “each one heard them speaking his own language” (Acts 2:6). The 1611 translators, quoting Augustine, held that variety of translations helps readers find the sense of Scripture. Lamin Sanneh argued that translatability is at the heart of Christian mission: no language is too common for the word of God. Comparing translations is an old discipline, not a sign of doubt.", "related": [ "numbers-headings-and-notes", "how-much-text", "finding-a-passage", "ai-citations" ], "variants": [ { "title": "A · One translation", "caption": "Chosen with name, approach and date in view.", "when": "Most reading", "tradeoff": "The alternatives stay hidden.", "items": [ "heading|Choose a translation", "card|KJV · King James Version|Formal; 1611, this text 1769" ] }, { "title": "B · Switch in place", "caption": "A switch above the text; the selected verse stays put.", "when": "Checking a verse quickly", "tradeoff": "One wording at a time.", "items": [ "button|KJV · BSB", "text|⁵ The Light shines in the darkness…" ] }, { "title": "C · Verse by verse", "caption": "Translations grouped under each verse, differences marked.", "when": "Studying wording", "tradeoff": "Breaks the flow of the passage.", "items": [ "heading|John 1:5", "text|KJV comprehended it not · BSB has not overcome it" ] }, { "title": "D · Parallel panes", "caption": "Two continuous texts, linked by verse.", "when": "Reading two translations together", "tradeoff": "Half a screen each.", "items": [ "tag|KJV · John 1:5", "tag|BSB · John 1:5" ] }, { "title": "E · Interlinear", "caption": "Original language with a gloss under each word.", "when": "Study and teaching preparation", "tradeoff": "Glosses can be read as the meaning.", "items": [ "text|κατέλαβεν · grasped / overcame", "button|How translations render this word" ] } ], "principles": [ "word-distinct", "offering" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone chooses a translation, checks another wording, or studies why translations differ.", "benefit": "Comparing translations shows the range of faithful readings and helps people understand a hard verse.", "drawback": "Comparison can fragment reading, narrow columns hurt legibility, and glosses can be mistaken for meaning.", "differences": "A new reader choosing a first Bible, a small group comparing wordings, a preacher preparing and a student of Greek need different depth.", "question": "Does the reader know what kind of translation this is, stay on the same verse when switching, and understand what a gloss can and cannot tell them?", "check": "Switch with a verse selected; compare at 200% text; ask what a gloss means; test right-to-left Hebrew." } }, { "id": "103", "slug": "highlights-and-notes", "topic": "study", "status": "Research-informed design proposal", "title": "Highlights and notes", "summary": "From a bookmark that only says “return here”, through highlights and labelled marks, to private notes and notes shared with a group or the public: decide how much a mark says, who can see it, and what happens to it in another translation.", "takeaway": "Make marking one tap with undo; distinguish marks by shape as well as colour and keep them apart from selection and playback; attach notes to the verse and highlights to their translation; keep notes private by default; and show exactly who will see a shared note before it is shared.", "problem": "Readers mark Scripture to return, to remember, to ask, and to talk with others. Apps offer colour palettes, notebooks, tags and public notes, often before the reader has finished the thought. Colour-only marks fail some readers and collide with selection and read-along highlighting; marks on exact words break when the translation changes; and notes on Scripture can reveal faith, doubt and private struggles to people they were never meant for.", "solution": "Offer a small menu over the selection with one-tap marking and undo; leave labels and organisation for later. Give each kind of mark its own shape, and keep selection, search and playback cues visibly different from saved marks. Attach highlights to the exact words in their translation and say so elsewhere; attach bookmarks and notes to the verse so they follow any translation. Keep notes private by default and treat them as sensitive data. Make sharing a separate step that names the audience and previews what they will see; label other readers’ notes as theirs and let people turn them off.", "failure": "A colour picker before every highlight; colour as the only difference between marks; read-along highlighting that looks like a saved mark; highlights silently lost or moved onto different words after switching translation; notes public by default; a “share” that publishes to everyone; others’ notes styled like study notes; inferring mood or belief from marks for analytics.", "test": "Mark, undo and re-mark a phrase; repeat with a screen reader and in greyscale. Switch translation and ask where each mark went and why. Play audio over marked verses. Ask people who can see a note they just shared, and compare with the truth.", "sources": [ "marshall-annotation", "edwards-blank-bible", "dunlosky-2013", "generation-effect", "gdpr", "ico-special-inferences", "olive-annotations-current", "youversion-plan-privacy", "wcag-use-of-color" ], "faith": "Scripture asks to be kept, not only read: “Write them on the doorposts of your houses” (Deuteronomy 6:9); “I have hidden Your word in my heart” (Psalm 119:11); Mary “treasured up all these things and pondered them in her heart” (Luke 2:19). Christians have long read with a pen: Jonathan Edwards filled an interleaved Bible with over five thousand notes across three decades. A mark is often a prayer or a question, and belongs to the reader.", "related": [ "translations", "numbers-headings-and-notes", "bible-audio", "progress-and-streaks" ], "variants": [ { "title": "A · Bookmark", "caption": "A ribbon that means “return here”.", "when": "Keeping a place", "tradeoff": "Records no thought.", "items": [ "text|³⁹ And he arose…", "button|Bookmark" ] }, { "title": "B · Highlight", "caption": "One tap on the selected words, with undo.", "when": "Marking what stood out", "tradeoff": "Stays with one translation.", "items": [ "text|Be still!", "notice|Highlighted · Undo" ] }, { "title": "C · Labelled marks", "caption": "Named marks with their own shapes.", "when": "A personal study shorthand", "tradeoff": "Asks for a decision.", "items": [ "button|Promise · Question · Return to", "tag|Question" ] }, { "title": "D · Private note", "caption": "A note on the verse, private by default.", "when": "Reflection and prayer", "tradeoff": "Sensitive; must stay private.", "items": [ "input|He was asleep in the storm…", "button|Save privately" ] }, { "title": "E · Shared note", "caption": "Notes for a group or the public, with the audience named.", "when": "Group study and community", "tradeoff": "Others’ words inside Scripture.", "items": [ "button|Only me · My group · Everyone", "notice|Anyone reading Mark 4 will see this" ] } ], "principles": [ "word-distinct", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone keeps a place, marks words that stood out, records a thought, or shares one with others.", "benefit": "Marking helps people return, remember and reflect, and shared notes let people read with others.", "drawback": "Marks can interrupt reading, fail without colour, collide with other cues, break across translations, and expose private faith.", "differences": "A daily reader, a student, a small group and someone praying through grief mark for different reasons and with different privacy needs.", "question": "Can someone mark in one tap and undo, tell every kind of mark apart without colour, and know exactly who can see each note?", "check": "Mark and undo in greyscale; switch translation; play audio over marks; ask who can see a shared note." } }, { "id": "104", "slug": "study-helps", "topic": "study", "status": "Research-informed design proposal", "title": "Study helps", "summary": "From a preview card under the verse, through a sheet and a study panel, to a page of its own or help only on request: decide where commentary, cross-references and sermon clips open, how readers find them, and how they get back to the verse.", "takeaway": "Keep the verse in view while help is open, or bring the reader back to it; mark resources quietly and let readers switch markers off; name every author, date and kind of resource; say whether a panel follows the reading or stays put; and give media a transcript, captions and its place in the whole.", "problem": "Bible apps attach commentaries, study notes, cross-references, videos and sermon clips to verses. Where that help opens decides whether it supports reading or replaces it. A full-screen resource loses the place; a panel that silently changes under the reader confuses; markers on every verse turn Scripture into a menu; a commentary without an author reads like the Bible’s own voice; and a short sermon clip can say something its speaker did not mean in context.", "solution": "Start with a short preview anchored to the verse, with the full resource one tap away. For longer help, use a sheet that leaves the verse visible, or a study panel on larger screens, and say whether the panel follows the reading or is pinned. If help takes the whole screen, make Back return to the same verse and show it. Mark verses with resources quietly, and let readers turn markers off. Show the kind of resource, its author and date, and where several voices disagree, show more than one. For media, show where the clip sits in the whole, offer what came before, and provide captions and a corrected transcript.", "failure": "A commentary styled like Scripture; no author or date; markers on every verse; autoplaying video between verses; a panel that changes without saying so; Back that returns to the top of the chapter; a 30-second clip presented as the speaker’s whole view; automatic transcripts quoted uncorrected; locked resources shown as if available.", "test": "Ask readers to open help on a verse, read it and return; note whether they are on the same verse. Ask who wrote the help and when. Scroll with a following panel and ask why it changed. Watch a clip, then the two minutes before, and ask whether the meaning changed. Test with captions, a screen reader and 200% text.", "sources": [ "hypertext-load", "spatial-contiguity", "page-previews", "interrupted-work", "m3-bottom-sheets", "olive-study-current", "gospelpartner-study", "glossa-ordinaria", "kjv-rules", "geneva-notes", "mh-concise", "cambridge-psalms", "wcag-captions", "wcag-reflow" ], "faith": "Scripture itself shows readers helped beside the text: the Levites “read from the Book of the Law of God, explaining it and giving insight, so that the people could understand what was being read” (Nehemiah 8:8), and the Ethiopian asked, “How can I … unless someone guides me?” (Acts 8:31). The medieval Glossa Ordinaria set the text in the centre of the page and the commentary around it, in a smaller hand. The King James translators allowed no interpretive notes in the margin, only notes on words and cross-references, because the Geneva Bible’s notes were thought partisan. Where help sits, and whose voice it carries, has always been a theological question as well as a layout one.", "related": [ "numbers-headings-and-notes", "translations", "ai-citations", "bible-audio", "highlights-and-notes" ], "variants": [ { "title": "A · Preview card", "caption": "A short card under the verse.", "when": "Footnotes, cross-references, a first look", "tradeoff": "Room for a sentence or two.", "items": [ "text|⁴ …the shadow of death… [4]", "card|Commentary · Matthew Henry|It is but the shadow of death…" ] }, { "title": "B · Sheet over the text", "caption": "A sheet that leaves the verse in sight.", "when": "Commentary and media on a phone", "tradeoff": "Covers half the passage.", "items": [ "tag|Psalm 23:4", "button|Commentary · Sermon clip · Isaiah 43:2" ] }, { "title": "C · Study panel", "caption": "Text and help side by side, following or pinned.", "when": "Sustained study on larger screens", "tradeoff": "Half a screen each on a phone.", "items": [ "tag|Following your reading", "tag|Pinned · Go to verse" ] }, { "title": "D · Full page", "caption": "The resource replaces the passage; Back returns to it.", "when": "Long commentary and video", "tradeoff": "The passage disappears.", "items": [ "heading|← Psalm 23:4", "text|The valley of the shadow of death may denote…" ] }, { "title": "E · On request", "caption": "No markers; a Study button lists everything.", "when": "Devotional reading", "tradeoff": "Help may go unfound.", "items": [ "button|Study · 7", "text|Psalm 23:4 · Commentary · Sermon" ] } ], "principles": [ "word-distinct", "speak-for-god" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone reading a passage opens a commentary, cross-reference or sermon clip on a verse, and returns to reading.", "benefit": "Help beside the text answers questions where they arise and shows the range of voices on a passage.", "drawback": "Help can replace reading, lose the place, blur the line between Scripture and interpretation, and quote media out of context.", "differences": "A devotional reader, a small-group leader, a preacher preparing and a Deaf viewer need different amounts of help and different formats.", "question": "Does the reader know who is speaking, which verse the help is about, and how to get back to it?", "check": "Open help and return; ask who wrote it; scroll a following panel; watch a clip and the minutes before it; test captions and 200% text." } }, { "id": "105", "slug": "reading-plans", "topic": "formation", "status": "Research-informed design proposal", "title": "Reading plans", "summary": "From a plan tied to calendar dates, through a sequence that waits for the reader and a weekly rhythm, to readings that belong to each day, and streaks as a warning case: decide what a plan asks of time, and what happens when someone comes back after days away.", "takeaway": "Choose dates only when reading together on the same day matters; otherwise let the plan wait. Never turn missed days into a debt: welcome people back with a choice of where to start, keep their place and notes, let them move dates, change pace or pause, and do not make a streak the point.", "problem": "Reading plans promise structure, and most tie each reading to a date. When life interrupts, the days pile up: “9 days behind”, a broken streak, a plan that now ends weeks late. People who feel they have failed often stop altogether, and some apps sell a way to repair the streak. Yet shared dates are also what let a church or small group read together.", "solution": "Decide what the plan is for. For reading together, keep shared dates but treat open days as available, not overdue, and on return offer today’s reading, where they stopped, or moving their own dates. For personal reading, use a sequence that waits, or a weekly number that starts fresh. For daily texts, let each day stand on its own. Explain what each change will do before it happens, keep completed readings and notes, let people pause without reminders, and say nothing about absence beyond what helps them choose.", "failure": "“You are 9 days behind”; a catch-up list of every missed reading; streak counters on the home screen; streak repair for money or gems; reminders that escalate after silence; resetting the plan and erasing history; group dashboards that show who is behind; asking why someone was away.", "test": "Ask people returning after a week, a month and a year what they would do next and how the screen makes them feel. Try each change (pause, move dates, own pace) and ask what will happen before confirming. Test with a group plan: can someone fall back without the group seeing it?", "sources": [ "mcheyne-preface", "benedict-18", "habit-automaticity", "broken-streaks", "fresh-start", "shame-guilt", "duolingo-streak-experiment", "youversion-catch-up", "moravian-daily-texts", "coe-daily-office", "willard-disciplines-grace" ], "faith": "Christians have long read Scripture by rule and by calendar: the daily office, lectionaries and the Moravian watchwords give each day its texts. Rules served the reader. Benedict asked that the whole psalter be prayed each week, yet told anyone who found his arrangement unsatisfactory to arrange whatever he judged better. Robert Murray M’Cheyne, whose 1842 calendar is still widely used, warned that it might become “a yoke too heavy to bear”: “throw aside the fetter, and feed at liberty in the sweet garden of God.” His mercies are “new every morning” (Lamentations 3:22–23); a plan should be too.", "related": [ "progress-and-streaks", "bible-audio", "how-much-text", "finding-a-passage" ], "variants": [ { "title": "A · Dated plan", "caption": "Each reading has a date; returns offer a choice.", "when": "Groups and churches reading together", "tradeoff": "Days away become visible.", "items": [ "heading|Welcome back", "button|Today’s reading · Where I stopped · Move my dates" ] }, { "title": "B · Sequence", "caption": "One reading after another, no dates.", "when": "Personal reading at any pace", "tradeoff": "No shared day with others.", "items": [ "tag|Reading 12 of 40", "button|Read Exodus 12" ] }, { "title": "C · Weekly rhythm", "caption": "A number per week, starting fresh each Monday.", "when": "Irregular lives", "tradeoff": "Needs a sense of the week.", "items": [ "tag|This week · 0 of 5", "button|Read Exodus 12" ] }, { "title": "D · Daily readings", "caption": "Each date has its own readings.", "when": "Daily texts and lectionaries", "tradeoff": "No book to finish.", "items": [ "heading|Tuesday 20 October", "text|Psalm 119:105–112 · Exodus 20:1–17 · Mark 12:28–34" ] }, { "title": "E · Streak", "caption": "Consecutive days counted and protected.", "when": "Avoid", "tradeoff": "A missed day becomes a loss.", "items": [ "heading|Your 11-day streak ended", "button|Repair streak · 3 gems" ] } ], "principles": [ "feed-the-flock", "growth", "enough" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone follows a reading plan, alone or with others, and sometimes comes back after days away.", "benefit": "A plan removes daily decisions and can let a group read together.", "drawback": "Dates and streaks turn interruptions into debt and loss, and people who feel behind often stop.", "differences": "A small group, a shift worker, a parent of young children, someone ill or grieving and a daily-office reader need different relationships to time.", "question": "After nine days away, does the plan offer a good place to start, or a bill?", "check": "Return after a week, a month and a year; try pause, move dates and own pace; check what a group can see." } }, { "id": "106", "slug": "prayer", "topic": "formation", "status": "Research-informed design proposal", "title": "Prayer", "summary": "From the received words of a church’s daily office, through guided steps and a list of people to pray for, to quiet prayer with nothing to fill in, and counted prayer as a warning case: decide what each surface asks someone to read, type, share or count.", "takeaway": "Name the tradition, calendar and author of every prayer; tell instructions, responses and silence apart; let people pause and finish without typing anything; keep prayer requests private by default and show exactly who will see a shared one, and for how long; let silence end without a score; and never turn prayer into minutes, streaks or public totals.", "problem": "Prayer apps offer daily offices, guided sessions, intention lists, timers and community request feeds. Each control says what counts as prayer: an empty field asks for words, a timer for duration, a checkmark for completion, a counter for volume. A generic “today” can hide whose calendar supplied the readings. Prayer requests name illnesses, families and doubts, and religious belief is special-category data. Some apps count minutes and streaks, show billions of “prayers prayed”, and let friends remind each other to keep up.", "solution": "Decide which practice the surface serves. For set prayer, show the order with its source and calendar, keep rubrics, the leader’s lines and the people’s responses visibly different, and let people look ahead without changing today. For guided prayer, show the outline, let people move at their own pace and keep any note optional and private. For people someone prays for, store requests on the device by default; for groups, name the audience and an end date before anything is shared, and ask before sharing someone else’s story. For silence, offer a complete untimed route and an optional end bell. Record nothing about prayer that the person did not choose to keep.", "failure": "A generic “today’s prayer” with no tradition named; a confession and its rubric in the same type; steps that advance by themselves; a required text field before continuing; prayer requests public by default or shown on the lock screen; marking a request “answered” automatically; minutes prayed, streaks and global totals; “Remind” buttons for friends who missed a day; sharing “I prayed 14 minutes” to social media; selling prayer data to advertisers.", "test": "Pray each surface without typing, recording or sharing anything, and ask what the app expected of you. Ask people to tell a response from an instruction in the office, and to name the calendar. Add a request for a group and ask who will see it and until when. Sit in silence with and without a timer. Check what is stored and sent with a network inspector.", "sources": [ "rb-20", "bcp-compline", "bcp-calendar-proper25", "examen-steps", "coe-daily-office", "usccb-calendar-scope", "prayer-types", "personal-quantification", "rewards-intrinsic-meta", "mozilla-prayer-apps", "payg-privacy", "gdpr", "ico-special-inferences", "youversion-guided-prayer-current", "wcag-222" ], "faith": "Jesus told his disciples to pray to the Father “who is unseen”, not “to be seen by men”, and warned against thinking “that by their many words they will be heard” (Matthew 6:5–7); when they asked, “Lord, teach us to pray”, he gave them words (Luke 11:1–4). The early church “devoted themselves … to prayer” together (Acts 2:42), and the Spirit helps “with groans too deep for words” when we do not know what to pray (Romans 8:26). Received words, one’s own words and silence all belong to Christian prayer. Benedict wrote that “we are heard not for our many words but for our purity of heart”, and asked that prayer be “short and pure”. An app cannot tell whether someone prayed, and should not pretend to count it.", "related": [ "bible-audio", "reading-plans", "progress-and-streaks", "highlights-and-notes", "ai-persona" ], "variants": [ { "title": "A · Order of prayer", "caption": "A church’s office for the hour, with its calendar named.", "when": "Daily prayer with a tradition", "tradeoff": "Needs accurate calendar data.", "items": [ "tag|Compline · Book of Common Prayer (1979)", "text|The Lord Almighty grant us a peaceful night and a perfect end." ] }, { "title": "B · Guided steps", "caption": "An outline of steps, at the person’s pace.", "when": "People who want a way in", "tradeoff": "Prompts are someone’s words.", "items": [ "tag|Step 2 of 5", "heading|Review the day with gratitude" ] }, { "title": "C · People I pray for", "caption": "A private list, with audiences named for groups.", "when": "Intercession", "tradeoff": "The most sensitive data.", "items": [ "text|Mum · Hospital appointment, Thursday", "button|Only me · Tuesday group" ] }, { "title": "D · Quiet prayer", "caption": "Begin, put the phone down, finish when ready.", "when": "Silence or one’s own words", "tradeoff": "Little guidance.", "items": [ "text|No words need to be entered.", "button|Begin" ] }, { "title": "E · Counted prayer", "caption": "Minutes, streaks and totals.", "when": "Avoid", "tradeoff": "Prayer becomes a number.", "items": [ "heading|11 day prayer streak", "text|1,111,432,374 prayers prayed" ] } ], "principles": [ "speak-for-god", "welcome", "send" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone prays with a church’s words, a guided outline, the names of people they carry, or in silence, alone or with others.", "benefit": "A dedicated surface can give received words, a way in for beginners, a place for intercession, or room for silence.", "drawback": "Controls can imply that prayer must be typed, timed or completed; request lists hold intimate data; counts turn prayer into performance.", "differences": "A daily-office participant, a beginner, someone praying for a sick parent, a group leader and someone who prays without words need different surfaces.", "question": "Could someone pray here meaningfully and leave nothing for our dashboard to count?", "check": "Pray each surface without typing; tell responses from instructions; ask who will see a shared request; sit in silence with and without a timer; inspect what is sent." } }, { "id": "108", "slug": "devotional-audio", "topic": "formation", "status": "Research-informed design proposal", "title": "Devotional audio", "summary": "From guided prayer with Scripture read twice and room for silence, through a teaching conversation and a one-voice devotional talk, to a sleep story that fades out, and an endless generated stream as a warning case: decide what each format does with Scripture, with the listener’s attention, and with the end of the session.", "takeaway": "Choose the format for the listener’s moment, not for listening time. Read Scripture whole and name who reads it; separate the reading from commentary; leave real silence, and in prayer let it wait for the listener; name every author, host and musician; and let every session end, with nothing queued after it.", "problem": "Devotional audio has become a crowded genre: guided prayer apps, Bible-teaching podcasts, morning devotionals, sleep stories and now AI-generated daily episodes. Each shapes how Scripture is heard: how much of it, by whom, framed by what. Hosts become familiar voices that listeners trust like friends. Players borrowed from podcast and video apps autoplay the next episode, and generated audio can be produced without end, often without a named author.", "solution": "Name the format and its purpose before playback. For prayer, read Scripture whole, often twice, separate reflection from reading, and leave silence that can wait. For teaching, name sources and distinguish the text from the hosts’ interpretation. For a talk, keep the passage at the centre and the host’s story in service of it. For sleep, fade to silence and play nothing after. Credit voices, authors and music, label synthetic voices, and end every session.", "failure": "Scripture read in fragments beneath music; commentary that sounds like the text; silence cut to keep attention; hosts presented as friends who know the listener; autoplay into the next episode; sleep content followed by more content; generated episodes without an author; “never run out” offers; streaks for listening.", "test": "Ask listeners after a session what the passage said and what the host said, and whether they could tell them apart. Time the silences. Check what plays after the session ends. Ask who wrote and who read each part, and whether any voice was synthetic.", "sources": [ "pray-as-you-go", "lectio", "examen-steps", "podcast-parasocial", "music-insomnia", "youtube-agency", "synthetic-trust", "ai-act-50", "fcbh" ], "faith": "“Faith comes by hearing” (Romans 10:17), and the church has always shaped how Scripture is heard: read, sung, preached, prayed. Ezra’s Levites read the Law, “explaining it and giving insight, so that the people could understand what was being read” (Nehemiah 8:8), keeping the reading and the explanation distinct. “I will lie down and sleep in peace” (Psalm 4:8). And the prophet asks, “Why spend … your labor on that which does not satisfy?” (Isaiah 55:2). Devotional audio can serve all of these, or replace them with endless listening.", "related": [ "bible-audio", "prayer", "reading-plans", "ai-persona" ], "variants": [ { "title": "A · Guided prayer", "caption": "Music, Scripture read twice, questions, silence, prayer.", "when": "Daily prayer", "tradeoff": "Needs a steady pace.", "items": [ "tag|Silence · waits for you", "text|Mark 4:35–41, read again" ] }, { "title": "B · Teaching conversation", "caption": "Two hosts on the text and its background.", "when": "Understanding", "tradeoff": "Hosts can overshadow the text.", "items": [ "tag|Context · Tom", "text|Jonah 1:5 · Psalm 107:29" ] }, { "title": "C · Devotional talk", "caption": "One voice: story, passage, a word for today.", "when": "Mornings and commutes", "tradeoff": "The story can take over.", "items": [ "tag|Story · Daniel", "text|Be still!" ] }, { "title": "D · Sleep story", "caption": "A slow retelling that fades to silence.", "when": "Night", "tradeoff": "The listener may not hear the end.", "items": [ "tag|Waves, fading", "text|Nothing else will play." ] }, { "title": "E · Endless stream", "caption": "Generated episodes, autoplay, no author.", "when": "Avoid", "tradeoff": "Listening never ends.", "items": [ "tag|Next episode in 5…", "text|Author: not stated" ] } ], "principles": [ "enough", "offering", "speak-for-god" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone listens to a devotional: to pray, to understand a passage, to start the day or to fall asleep.", "benefit": "Audio reaches people while commuting, caring, resting or unable to read, and a good format can teach a way of praying.", "drawback": "Formats can bury Scripture under commentary, cut silence, attach listeners to hosts, and never end.", "differences": "A daily pray-er, a curious learner, a commuter, someone who cannot sleep and someone who cannot read need different shapes.", "question": "After the session, could the listener say what Scripture said, who spoke, and why it ended?", "check": "Ask listeners to separate text from commentary; time silences; check what plays next; check credits and synthetic voices." } }, { "id": "107", "slug": "check-ins-and-assessments", "topic": "formation", "status": "Research-informed design proposal", "title": "Check-ins and assessments", "summary": "From a few setup questions that only shape what the app suggests, through a daily check-in, a gifts inventory and a church survey, to a spiritual score as a warning case: decide what each question is for, what is kept, who sees a result, and how much the result claims to know.", "takeaway": "Ask only what changes what the app offers, say what each answer changes, and let every question be skipped. Treat feelings and faith as special-category data: keep answers on the device by default, let people delete them, and share nothing automatically. Present results as starting points for trying and for conversation with people who know the person, never as a grade, a stage or a rank.", "problem": "Christian apps increasingly ask before they give: onboarding quizzes about goals and Bible familiarity, daily mood check-ins “with myself, with others, with God”, long personality tests that produce a “spiritual health report”. Churches have done something similar for decades with spiritual gifts inventories, Natural Church Development surveys and Willow Creek’s Reveal study. Asking can help: naming a feeling, finding a place to serve, a church hearing its members. But answers about mood and faith are intimate and legally protected, onboarding quizzes often serve a paywall, and a number can start to stand for a life with God.", "solution": "Name the purpose of each question set. For personalisation, ask few questions, say what each changes, allow skipping and editing, and ask nothing about health or belief that the app does not need. For a check-in, let naming be enough, respond with Scripture or a next step rather than a score, and keep the record on the device with a delete option. For gifts, frame results as places to try and people to talk with. For a church survey, keep answers anonymous and aggregated, and share results as a conversation starter. Never send anything automatically, and never rank people.", "failure": "Quizzes that cannot be skipped and end in a paywall; questions about anxiety, sins or shame without saying why; mood records sent to servers or friends automatically; charts of feelings that invite self-monitoring; results that hand out a label (“You are a Teacher”); spiritual scores, stages and rankings against others; prompts to retake a test to raise a score; leaders seeing individual answers.", "test": "For every question, ask what it changes and who could ever see the answer, and check that it can be skipped. Ask people to read their result aloud and say what it claims about them, and whether that is fair. Check what is stored and sent with a network inspector. Ask a pastor or spiritual director how they would respond to the same answers.", "sources": [ "examen-steps", "wesley-bands", "ncd-survey", "ncd-review", "network-gifts", "gifts-personality", "reveal-galli", "affect-labeling", "ema", "barnum", "personal-quantification", "gdpr", "ico-special-inferences", "mozilla-prayer-apps", "soultime-aggregate", "hellobible-store" ], "faith": "Self-examination is old Christian practice. “Examine yourselves to see whether you are in the faith” (2 Corinthians 13:5); “Search me, O God, and know my heart” (Psalm 139:23). The Examen asks people to notice their feelings each evening, and Wesley’s band meetings asked the same questions every week, among friends. Paul wrote that “to each one the manifestation of the Spirit is given for the common good” (1 Corinthians 12:7), and told readers, “Do not think of yourself more highly than you ought” (Romans 12:3). He also wrote “I do not even judge myself … It is the Lord who judges me” (1 Corinthians 4:3–4). Asking can serve discernment; only God knows a heart, and no app should pretend to score one.", "related": [ "prayer", "reading-plans", "progress-and-streaks", "sensitive-memory", "health-and-spiritual-practice" ], "variants": [ { "title": "A · Setup questions", "caption": "A few optional questions, each saying what it changes.", "when": "Personalising a first suggestion", "tradeoff": "Easily becomes a funnel.", "items": [ "heading|How familiar is the Bible to you?", "text|This changes: how much background each reading includes." ] }, { "title": "B · Daily check-in", "caption": "Name a feeling; get a passage, not a score.", "when": "Self-examination", "tradeoff": "Mood records are health data.", "items": [ "heading|How are you, today?", "button|Anxious · Tired · Grateful" ] }, { "title": "C · Gifts inventory", "caption": "Statements about oneself; places to try.", "when": "Finding where to serve", "tradeoff": "Can feel like a label.", "items": [ "tag|Places to explore", "text|Welcome and care · Try: the Sunday welcome team" ] }, { "title": "D · Church survey", "caption": "Anonymous answers, shared results by area.", "when": "A church listening to its members", "tradeoff": "Numbers can become targets.", "items": [ "heading|How 30 of us see St Mark’s", "text|Where to start talking: small groups" ] }, { "title": "E · Spiritual score", "caption": "A number, a stage and a rank.", "when": "Avoid", "tradeoff": "Faith becomes a grade.", "items": [ "heading|72 / 100", "text|You’re in the top 30% at St Mark’s" ] } ], "principles": [ "growth", "most-vulnerable", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone answers questions about their goals, feelings, gifts or church, and receives a suggestion or a result.", "benefit": "Good questions can personalise a first step, give words to a feeling, point toward serving, or let a church hear its members.", "drawback": "Answers about mood and faith are intimate and protected; results can overclaim, label or rank people; quizzes can serve sales.", "differences": "A newcomer, someone in a hard week, a volunteer looking for a place, a church leader and someone wary of being measured need different questions, or none.", "question": "For each question: what does the answer change, who could ever see it, and what does the result claim to know?", "check": "Skip every question; read each result aloud and ask whether it is fair; inspect what is stored and sent; ask a pastor how they would respond." } }, { "id": "110", "slug": "sharing-with-a-group", "topic": "formation", "status": "Research-informed design proposal · draft for review", "title": "Sharing with a group", "summary": "From a request kept between someone and God, through one listener they choose, a few friends and a group with a leader, to the whole church and a public wall, with a board ranked by prayer streaks as a warning case: decide who hears a request, what each listener can and must do with it, and what comes back.", "takeaway": "Show who will hear a request, for how long, before anything is written; ask before naming anyone else; say before someone shares that some listeners have to pass concerns on; when a church sets the app up, name its safeguarding contact, someone outside the leadership a concern might be about; keep an independent route beside the church’s; help groups listen before they answer; and never rank or count prayer.", "problem": "Prayer apps let people share requests with friends, small groups, a parish or everyone in the app. Requests name illnesses, families and fears, often about people who never agreed to be mentioned. Most are ordinary, and being prayed for is a gift. Some disclose abuse or danger, sometimes involving someone in the same church, and the listener may be a volunteer with a duty to report, a friend who quotes a verse back, or a stranger. Notifications and automatic nudges can carry a request further than the person meant.", "solution": "Let the person choose the audience before writing, and show who will see the request, for how long and whether it can be edited or deleted. Ask before naming someone else. Offer a route to one chosen person, with what each listener can and must do shown before sending. When a church sets the app up, name its safeguarding contact and keep an independent service beside it. Give groups ways to respond that start with listening, keep support groups’ members confidential, and send no automatic notifications about someone without asking them each time.", "failure": "A public feed as the default; first names and requests visible to strangers; a request about someone else posted without their consent; friends notified automatically when the app infers a low mood; a leader as the only route for a concern about the leader’s team; verses quoted back at someone who disclosed harm; hearts and counts on requests; streak boards with Praise and Remind buttons; promising confidentiality a listener cannot keep.", "test": "Ask people to share an ordinary request and something hard, then to name everyone who will see each, for how long, and what each listener must do with it. Read the replies a group gives to a hard request. Find the safeguarding contact and an independent service from inside the app in under a minute. Check what notifications say, and to whom.", "sources": [ "hallow-intentions", "hallow-church-tab", "planning-center-confidential", "youversion-prayer", "umc-prayer-privacy", "ekd-gewaltschutz", "dbk-rahmenordnung", "cofe-pso-durham", "anlaufstelle-help", "thirtyoneeight-confidentiality", "nij-disclosure-reactions", "lifeway-small-groups-2026", "spiritual-abuse-guidance", "gdpr", "ico-special-inferences", "mozilla-prayer-apps" ], "faith": "Paul asks the church to “rejoice with those who rejoice; weep with those who weep” (Romans 12:15), and to “carry one another’s burdens” (Galatians 6:2). Job’s friends did best when they “sat on the ground with him for seven days and seven nights, but no one spoke a word to him because they saw how intense his suffering was” (Job 2:13). Hearing a request is a charge as well as a gift. The same passages have been used to press people to share more than they chose, or to keep concerns inside a church, so the listener’s care matters as much as the sharer’s trust.", "related": [ "prayer", "ai-citations", "ai-memory", "progress-and-streaks", "highlights-and-notes" ], "variants": [ { "title": "A · Between you and God", "caption": "A private journal; the app points to people and churches.", "when": "Requests no one else should see", "tradeoff": "No one prays with them.", "items": [ "tag|Only on this phone", "button|Who can I talk to?" ] }, { "title": "B · Through a person you choose", "caption": "One listener, with what they can and must do shown first.", "when": "Something hard", "tradeoff": "A church must name someone.", "items": [ "tag|What happens next", "button|Send to Maren" ] }, { "title": "C · A few people you choose", "caption": "A small circle the person invited.", "when": "Ordinary requests", "tradeoff": "Replies are unguided.", "items": [ "tag|My circle · 4 friends", "button|Share with my circle" ] }, { "title": "D · A group with a leader", "caption": "Joined by invitation; members confidential.", "when": "Small and support groups", "tradeoff": "Leaders may be too close.", "items": [ "tag|Joined with a code", "text|Before you share: leaders may have to pass things on." ] }, { "title": "E · The whole church", "caption": "Requests to the parish, for seven days.", "when": "Joys and ordinary needs", "tradeoff": "Hundreds see a name and a need.", "items": [ "tag|412 members", "button|Post" ] }, { "title": "F · A public wall", "caption": "One thread for everyone in the app.", "when": "Late at night, with no one to call", "tradeoff": "Strangers answer.", "items": [ "tag|480k responses", "button|Leave a response" ] }, { "title": "G · Ranked by streaks", "caption": "Requests beside a board of streaks.", "when": "Avoid", "tradeoff": "Prayer becomes a ranking.", "items": [ "heading|Active pray-ers", "button|Remind" ] } ], "principles": [ "welcome", "most-vulnerable", "send" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone asks others to pray: for a family member, a job, a fear, or something they have never said aloud.", "benefit": "Being prayed for by people who know you is one of the gifts of a church; a group can carry what one person can’t.", "drawback": "Requests are intimate data about the person and others; listeners may answer badly, notify others or be obliged to report; public feeds and counts turn need into content.", "differences": "An ordinary request, a joy to share, a request about someone else, a support group, and a disclosure of abuse or danger each need a different audience and a different listener.", "question": "When someone shares something hard here, who hears it first, and what are they able, and obliged, to do?", "check": "Share an ordinary request and a hard one; name everyone who sees each, and for how long; read the replies; find the safeguarding contact and an independent service in under a minute." } }, { "id": "111", "slug": "reading-together", "topic": "formation", "status": "Research-informed design proposal · draft for review", "title": "Reading together", "summary": "From the same passage on the same day with nothing shown, through a guide for meeting in person, a group with a leader and a plan with friends, to a feed of friends’ activity and a public thread on the verse: decide what the others see of each person’s reading, and who looks after what is said.", "takeaway": "Share the passage and the conversation, not the record; say before a plan starts what the others will see, and let people delete it; make falling behind a way back, not a signal; give the conversation a shape that starts with listening; prepare for a verse turned against the person who shared; keep young people’s conversations in the group and name a safeguarding contact; and label strangers’ notes as theirs, a step away from the text.", "problem": "Bible apps let people read with others: the same passage on the same day, plans with friends that show each day’s ticks, group units led by someone with a code, comments on every verse and feeds of what friends have read. Each decides what the others see of a person’s reading and who looks after the conversation. Ticks make the person who fell behind visible. Comments put strangers’ readings beside the text. A reply can turn a verse against someone who has just shared something hard, and nobody may be there to notice.", "solution": "Share the passage and the day, and keep each person’s record private unless they choose to show it. Say before a plan starts what participants and friends will see, and let people delete it. Let someone rejoin where the group is today. Give groups prompts that ask what touched each person, not what others should do. When a church or leader runs the group, name who looks after it, keep conversations with young people in the group, and name a safeguarding contact. Label others’ notes as theirs, say who moderates them, and keep them a step away from the text.", "failure": "Completion ticks for everyone in a group by default; friends’ feeds filled with each completed day that cannot be deleted; no way back for someone who fell behind except by catching up in view of everyone; strangers’ readings shown inside the verse; a verse quoted at someone who shared a hurt, with no one able to step in; leaders messaging young people one to one; badges and streaks in the same stream as the group’s conversation.", "test": "Run a week of a group plan with five people. Ask each to list what the others can see of them, and where. Have one fall behind and watch what they see when they return. Post a reply that turns a verse against someone who shared, and time how long it takes for someone responsible to notice and reach the person. Check what a young person in the group can receive, and from whom.", "sources": [ "youversion-pwf", "youversion-plan-privacy-ios", "youversion-pwf-comments", "youversion-pwf-2017", "youversion-catch-up", "moravian-texts-history", "bibelteilen-koeln", "vasteras-linz", "cofe-video-calling", "boyne-hill-messaging", "arigo-social-comparison", "lifeway-small-groups-2026", "spiritual-abuse-guidance", "gdpr" ], "faith": "Two disciples on the road to Emmaus “talked and deliberated” until Jesus “came up and walked along with them” (Luke 24:15), and afterwards asked each other, “Were not our hearts burning within us as He spoke with us on the road and opened the Scriptures to us?” (Luke 24:32). The first church “devoted themselves to the apostles’ teaching and to the fellowship” (Acts 2:42). Reading together is a gift, and the conversation needs tending: a verse can open the Scriptures to someone, or be turned against them.", "related": [ "reading-plans", "highlights-and-notes", "sharing-with-a-group", "progress-and-streaks", "prayer" ], "variants": [ { "title": "A · The same passage, nothing shown", "caption": "Everyone reads today’s passage; nobody sees who read.", "when": "Churches and lectionary readers", "tradeoff": "No one to talk it over with in the app.", "items": [ "tag|Read by your church today", "button|Read" ] }, { "title": "B · A guide for meeting in person", "caption": "The app leads the steps; nothing said is stored.", "when": "House groups", "tradeoff": "Needs people in one room.", "items": [ "tag|Step 5 of 7 · Share", "text|Speak about yourself. No discussion." ] }, { "title": "C · A group with a leader", "caption": "Joined with a code; a leader looks after the answers.", "when": "Church and youth groups", "tradeoff": "The leader sees who answers.", "items": [ "tag|Joined with a code from Petra", "button|Answer if you want" ] }, { "title": "D · A plan with friends", "caption": "The same days, ticks for each, and a discussion per day.", "when": "Friends who live apart", "tradeoff": "Everyone sees who is behind.", "items": [ "tag|Day 3 · 4 of 5 done", "button|Talk it over" ] }, { "title": "E · A feed of friends’ activity", "caption": "Completed days, highlights and notes in a stream.", "when": "Encouragement among friends", "tradeoff": "Every completion becomes a signal.", "items": [ "heading|Community", "text|Anna completed Day 7" ] }, { "title": "F · A public thread on the verse", "caption": "Strangers’ comments under the passage.", "when": "Reading alone with questions", "tradeoff": "Strangers interpret for you.", "items": [ "tag|711 comments", "button|Share your thoughts" ] } ], "principles": [ "send", "most-vulnerable", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "People read the same passage as others: a church, a house group, a youth group or friends far apart.", "benefit": "Others help us see what we would miss, and a shared day gives a group something to talk about when it meets.", "drawback": "Ticks, feeds and comments show more than the passage: who read, who fell behind, and what someone shared, to people who may answer badly.", "differences": "A church reading the same texts, a house group meeting in person, a youth group with leaders, friends far apart and a public thread each need different visibility and someone different looking after the conversation.", "question": "What will each person see of the others’ reading, and who looks after the conversation when it goes wrong?", "check": "List what every participant can see of every other, and where; have one fall behind and return; post a reply that turns a verse against someone, and see who notices and how the person is reached." } }, { "id": "112", "slug": "first-use", "topic": "formation", "status": "Research-informed design proposal · draft for review", "title": "First use", "summary": "From opening on a passage, a prayer or a question box with nothing asked, through a first page of places to start, guest use and a short tour, to questions first and payment before the first use: decide what a new person must give, and when, before they reach what they came for.", "takeaway": "Let people reach what they came for before you ask for anything; ask for an account when there is something to keep, a permission when a feature needs it, and payment after a first use, saying plainly what costs money and why; keep help in a crisis one tap away and never behind an account, a quiz, a quota or a paywall; let “no church right now” be an ordinary answer.", "problem": "The first minutes in a faith app decide whether someone reads, prays or asks at all. Many apps put a great deal in front of the first verse, prayer or answer: a tour, an account, questions about goals, age and Bible knowledge, testimonials, a request to rate the app, notification and tracking prompts, and a subscription offer. Some people arrive curious; some arrive in a hard night; some come back after years away, or after being hurt in a church. Apps also cost money to build and run, and AI answers cost money every time, so the question of when and how to ask for payment is real, not a trick.", "solution": "Open on what the person came for: today’s passage, a prayer to play, a question box. Offer a short page of places to start, with help in a crisis at the top. Let people use the app as a guest, and ask for an account when there is something to keep, such as a highlight or a plan. Keep any tour short and skippable. Ask questions only when the answer changes something, and let each be skipped. Ask for permissions when a feature needs them. Ask for payment after a first use: say what is free, what costs money and roughly how much, and give the charge date before a trial begins.", "failure": "An account, a phone number or a quiz before the first verse; a request to rate the app before it has been used; notification and tracking prompts at launch; a weekly subscription as the default; testimonials and social proof between questions; crisis help behind a sign-up or a quota; questions about church attendance or Bible knowledge that cannot be skipped and that praise every answer; payment framed as the only way to be faithful, or free use framed as the only way to be faithful.", "test": "Install the app on a fresh phone and count the taps, fields and prompts before the first verse, prayer or answer. Do it again as someone who says, in the first box they see, that they don’t want to be here anymore, and time how long it takes to reach a person. Do it as someone who answers “no church right now”. Write down, for a year of use, what the person pays, what it costs you to serve them, and whether the app says so.", "sources": [ "apple-review-account", "apple-hig-onboarding", "android-permissions", "nng-onboarding-components", "nng-onboarding-tutorials", "edpb-deceptive-design", "baymard-account", "york-start-bible", "gideons-help", "benedict-rule", "canon-mass-offering", "didache-support", "claude-pricing", "esv-api-terms", "bsb-pd", "youversion-funding", "telefonseelsorge" ], "faith": "When two disciples began to follow Jesus, he asked them, “What do you want?”, and when they asked where he was staying, he said, “Come and see” (John 1:38–39). They spent the day with him before anything was asked of them. The same Scriptures say both “Freely you have received; freely give” (Matthew 10:8) and “the worker is worthy of his wages” (Luke 10:7): welcome freely, and pay honestly those who serve.", "related": [ "check-ins-and-assessments", "reading-plans", "progress-and-streaks", "ai-persona", "prayer" ], "variants": [ { "title": "A · Open on what they came for", "caption": "Today’s passage, a prayer or a question box; nothing asked.", "when": "Curious first visits", "tradeoff": "Nothing is saved yet.", "items": [ "tag|John 1 · today", "button|Read" ] }, { "title": "B · A first page of places to start", "caption": "A short list of situations, with help at the top.", "when": "People without a reference", "tradeoff": "Someone chose the passages.", "items": [ "heading|Where would you like to start?", "text|I need someone to talk to now" ] }, { "title": "C · Guest first", "caption": "Use it now; an account when there is something to keep.", "when": "Most apps", "tradeoff": "A later ask can still feel like a wall.", "items": [ "tag|Guest", "button|Create an account to keep this highlight" ] }, { "title": "D · A short tour first", "caption": "A few skippable slides before the first use.", "when": "Unfamiliar features", "tradeoff": "Often skipped and soon forgotten.", "items": [ "tag|2 of 4", "button|Skip" ] }, { "title": "E · Questions first", "caption": "Goals, age and familiarity before any content.", "when": "Personalising a first suggestion", "tradeoff": "Becomes a funnel; see check-ins.", "items": [ "heading|What brings you here?", "button|Continue" ] }, { "title": "F · Asking for payment", "caption": "Before the first use it is a gate; after, it can be honest.", "when": "Keeping the work going", "tradeoff": "Up front, it asks before giving.", "items": [ "heading|Start your free trial", "text|3 days free, then $6.99 a week" ] } ], "principles": [ "welcome", "most-vulnerable", "feed-the-flock" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone opens a faith app for the first time: a Bible reader, a prayer or audio app, or an AI companion.", "benefit": "A good first use gives people what they came for and the confidence to come back; a fair ask for support keeps the work going.", "drawback": "Accounts, quizzes, prompts and paywalls before the first use can turn away the curious, delay help for someone in a crisis, and wound someone coming back after harm.", "differences": "A curious newcomer, someone in a hard night, someone returning after years away or after being hurt in a church, and a church member sent a link need different first screens.", "question": "What must someone give before they reach what they came for, and what does it cost us to serve them?", "check": "On a fresh install, count everything asked before the first verse, prayer or answer; reach crisis help from the first screen; answer “no church right now”; write down what a year of use costs the person and costs you." } }, { "id": "113", "slug": "children-and-families", "topic": "formation", "status": "Research-informed design proposal · draft for review", "title": "Children and families", "summary": "From a story read aloud with a grown-up, through family time in a general app, a children’s Bible app and games with episodes, to a youth group app with a leader and a child alone with an AI or a public community: decide who is with the child, what the app collects, how it holds attention, and what happens when a child says something worrying.", "takeaway": "Design for a grown-up beside the child where you can; collect nothing a child does not need to give; keep purchases, links and settings behind a parental gate; switch off streaks, autoplay and notifications for children; tell hard stories with care and room for questions; keep young people’s conversations in a group with two leaders; and when a child writes something worrying, answer the child first, with a helpline and a trusted adult, instead of telling a parent automatically.", "problem": "Children meet Scripture through apps made for them, family corners of apps made for adults, video and game apps, youth group apps, and adult apps they use anyway, including AI chat apps rated for all ages. Each decides who is with the child, what it collects, how it holds attention and what it does when a child says something worrying. Children’s data is protected by law in the EU, the UK and the US; children’s attention is easy to capture; and a story such as the Flood or the cross can frighten a child who meets it alone. In a youth group, as in any church work with children, contact needs safeguards.", "solution": "Where you can, design for a grown-up beside the child: a story to read aloud with questions to wonder about together. For a child using the app alone, ask for no account and no personal details, show no ads, keep purchases, links and settings behind a parental gate, and leave out streaks, autoplay and notifications. Tell hard stories with care, and suggest talking them over. For young people in a church group, keep conversations in the group with two leaders, get parents’ consent, and name a safeguarding contact. When a child writes something worrying, answer the child: say it was right to tell, offer a helpline for children and a trusted adult, and, in a church-run app, route it to the trained safeguarding contact, not automatically to a parent.", "failure": "Accounts, ages and names asked of children; third-party analytics and advertising; purchases and links a child can reach; streaks, badges and autoplay that keep a child watching; frightening scenes labelled “KIDS” with no grown-up in view; one-to-one messages between a leader and a young person; a child left alone with an AI chat or a public comment thread; a worrying message sent automatically to a parent who may be the danger, or answered with nothing.", "test": "Hand the app to a child of the target age with a grown-up watching, and note every place the child could buy, leave the app, meet a stranger or be asked for a detail. List every piece of data collected and who receives it. Read the Flood or the crucifixion with a five-year-old and see what the app gives the grown-up to say. Type a worrying message as a child would, and walk through who sees it and what the child is told.", "sources": [ "who-screen-time", "coviewing", "godly-play", "apple-kids-category", "eu-minors-guidelines", "ico-childrens-code", "coppa-2025", "bak-store", "superbook-store", "konapp-store", "konapp-epd", "konapp-agreement", "nummer-gegen-kummer", "ai-jesus-store", "cofe-video-calling", "boyne-hill-messaging", "gdpr" ], "faith": "When people brought little children to Jesus and the disciples rebuked them, he “was indignant and told them, ‘Let the little children come to Me, and do not hinder them! For the kingdom of God belongs to such as these’” (Mark 10:14). Israel was told to teach God’s words “to your children and speak of them when you sit at home and when you walk along the road” (Deuteronomy 6:7). Jesus also said that whoever causes “one of these little ones who believe in Me to stumble” would be better off with “a large millstone hung around his neck” (Matthew 18:6). Children are welcomed, taught at home, and protected.", "related": [ "reading-together", "sharing-with-a-group", "first-use", "progress-and-streaks", "devotional-audio" ], "variants": [ { "title": "A · Read together", "caption": "A story for a grown-up to read aloud, with questions to wonder about.", "when": "Young children at home", "tradeoff": "Needs a grown-up with time.", "items": [ "tag|For reading together", "text|I wonder which part you like best" ] }, { "title": "B · Family time in a general app", "caption": "Kids’ prayers and family plans beside the adult content.", "when": "Families already using an app", "tradeoff": "The rest of the app is a tap away.", "items": [ "heading|A Family Examen", "button|Play together" ] }, { "title": "C · A children’s Bible app", "caption": "No account, no ads, a parental gate.", "when": "A child using the app alone", "tradeoff": "The child may be alone with hard stories.", "items": [ "tag|For grown-ups: hold to open", "button|Next story" ] }, { "title": "D · Games and episodes", "caption": "Videos, games and rewards around the stories.", "when": "Engagement", "tradeoff": "Holds attention for its own sake.", "items": [ "tag|3 stars collected", "button|Next episode" ] }, { "title": "E · A youth group with a leader", "caption": "Parents’ consent, two leaders, a named contact.", "when": "Confirmation and youth groups", "tradeoff": "Leaders see what is posted.", "items": [ "tag|Confirmation group · 2 leaders", "button|Write in your diary" ] }, { "title": "F · A child alone with an AI or a community", "caption": "An open chat or public thread, rated for all ages.", "when": "Leave it out for children", "tradeoff": "No one is with the child.", "items": [ "heading|Ask me anything", "text|Rated 4+" ] } ], "principles": [ "most-vulnerable", "send", "welcome" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Children, with or without a grown-up, and young people in church groups meet Scripture, prayer and stories through an app.", "benefit": "Stories, prayers and questions can be shared at home, and a youth group can stay in touch between meetings.", "drawback": "Children’s data, attention and safety are at stake: collection, persuasive design, frightening stories met alone, contact with adults and strangers, and worrying messages no one answers well.", "differences": "A four-year-old on a parent’s lap, a ten-year-old alone with a tablet, a confirmation group and a teenager on an adult app need different designs.", "question": "Who is with the child, what does the app collect and how does it hold attention, and what happens when a child says something worrying?", "check": "Hand it to a child with a grown-up watching; list every purchase, link, contact and data flow a child can reach; read a hard story with a young child; type a worrying message as a child and follow it through." } }, { "id": "114", "slug": "notifications", "topic": "formation", "status": "Research-informed design proposal · draft for review", "title": "Notifications and reminders", "summary": "From an app that waits to be opened, through reminders the person sets, the church’s hours of prayer, a daily word and messages from people, to notifications tuned to bring people back and an AI that writes first: decide who chooses the interruption, how urgent it claims to be, what it says to someone who has been away, and what reaches someone at night.", "takeaway": "Let the person decide when they are called: ask for permission when they set a reminder, offer the church’s hours as a shared rhythm, send people’s messages rather than the app’s, and keep quiet hours. Never mark a reminder Time Sensitive, never count down a streak, never write in a persona’s voice to bring someone back, and after silence ask once whether to keep reminding, then stop.", "problem": "Every faith app that can send notifications has to decide when to interrupt, about what and in whose voice. The phone sits beside the bed, so a notification reaches people at their most unguarded: waking, at work, with their children, awake at night. Notifications are also the strongest tool for bringing people back, and the techniques that work best for that, streak warnings, optimised timing and wording, messages that pretend to miss someone, are the ones that treat prayer as a habit to sell.", "solution": "Start with the person’s own choice. Ask for permission when someone sets a reminder, not before the first verse, and let them choose the days, the time and the words. Offer the church’s hours, morning, midday and evening, as a rhythm others keep too. Notify for what people did, a prayer said for them, an invitation, not for what the app wants. Mark nothing Time Sensitive that is not, keep quiet hours, and let the phone’s summary and Focus do their work. When someone stops opening the app, ask once whether to keep reminding them, then stop.", "failure": "A permission prompt before the first verse; “Your 12-day streak ends at midnight!” marked Time Sensitive to break through Sleep Focus; reminders that multiply after silence; “We miss you” and “Did I say something wrong?” in the voice of an app or an AI; reminders to friends who stopped; telling someone’s friends that the app thinks they need a call; marketing offers in the prayer reminder’s place.", "test": "Install the app on a test phone, allow notifications, use it once and leave it for two weeks. Log every notification: time, words, urgency and who chose it. Then turn on Sleep Focus and a Scheduled Summary and see what breaks through. Finally, read every notification as someone who is grieving, depressed or awake at 2 am would read it.", "sources": [ "apple-hig-notifications", "apple-review-push", "android-notification-permission", "fitz-batching", "duolingo-bandit", "defreitas-paper", "eu-minors-guidelines", "angelus-encyclopedia", "benedict-hours", "bible-widgets-store", "blessed-store", "echo-store", "intercede-store", "universalis-store", "hallow-store", "bible-chat-store", "telefonseelsorge" ], "faith": "“Morning, noon, and night, I cry out in distress, and He hears my voice” (Psalm 55:17). Daniel prayed “three times a day” (Daniel 6:10), and the Psalmist “Seven times a day” (Psalm 119:164); the church has rung bells for its hours ever since. But when the disciples found Jesus praying alone and said, “Everyone is looking for You!”, he did not go back (Mark 1:37–38). God spoke to Elijah not in the wind, the earthquake or the fire, but in “a still, small voice” (1 Kings 19:12).", "related": [ "reading-plans", "progress-and-streaks", "first-use", "ai-persona", "sharing-with-a-group", "children-and-families" ], "variants": [ { "title": "A · The app waits", "caption": "No notifications; at most a widget the person adds.", "when": "Readers who come when they choose", "tradeoff": "Nothing calls them back.", "items": [ "tag|Widget · Psalm 4:8", "text|Nothing sent this week" ] }, { "title": "B · Their own bell", "caption": "Only reminders the person sets.", "when": "A habit someone wants", "tradeoff": "Needs setting up.", "items": [ "tag|Mon–Fri · 7:30", "text|Morning reading" ] }, { "title": "C · The church’s hours", "caption": "Morning, midday and evening prayer.", "when": "Praying with others", "tradeoff": "A fixed rhythm may not fit a day.", "items": [ "tag|Midday · 12:00", "text|Pause and pray" ] }, { "title": "D · A daily word", "caption": "A verse or prompt every day.", "when": "A small daily start", "tradeoff": "Sent whether or not it is wanted.", "items": [ "tag|Verse of the day", "text|Psalm 46:10" ] }, { "title": "E · People, not the app", "caption": "Only when someone prayed, invited or replied.", "when": "Communities and groups", "tradeoff": "Quiet without friends.", "items": [ "tag|Anna prayed for you", "text|Ben invited you to Mark" ] }, { "title": "F · Engagement-driven", "caption": "Streak warnings and messages tuned to bring people back.", "when": "Daily active users", "tradeoff": "Treats prayer as a habit to sell.", "items": [ "tag|Time Sensitive", "text|Your streak ends at midnight" ] }, { "title": "G · Messages about the person", "caption": "An AI or the app writes first, or tells friends.", "when": "Leave it out", "tradeoff": "Writes in a voice that is not a person’s.", "items": [ "heading|I’ve been thinking about you", "text|We let 2 friends know" ] } ], "principles": [ "enough", "speak-for-god", "feed-the-flock" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone wants help keeping a rhythm of reading or prayer, wants to pray with others at the same hours, or wants to hear when someone prays for them.", "benefit": "A reminder they chose, or the church’s bell, can help people keep a practice they want to keep, and a message from a friend can carry real care.", "drawback": "Notifications reach people at their most unguarded, and the techniques that bring people back best, urgency, streaks, optimised wording and messages in a persona’s voice, turn prayer into engagement.", "differences": "Someone new, someone who prays most days, someone who has been away for weeks and someone awake at 2 am read the same notification very differently.", "question": "Who chose this interruption, how urgent does it claim to be, and what does it say to someone who has stopped coming?", "check": "Use the app once and leave it for two weeks on a test phone; log every notification; turn on Sleep Focus and a Scheduled Summary; read each one as someone grieving or awake at night would." } }, { "id": "115", "slug": "giving", "topic": "formation", "status": "Research-informed design proposal · draft for review", "title": "Giving and offerings", "summary": "From leaving giving to the church, through a quiet way to give, the church’s offering in the app, a regular gift and showing what a gift does, to a gift tied to an ad-free app and, as the warning case, pressure and promises: decide where the ask appears, what is chosen for the giver, and what the app says a gift will do.", "takeaway": "Make giving easy to find and never in the way: start with no amount and a one-off gift, say who receives it, what it costs and what it does, send a receipt, and make stopping a regular gift as easy as starting it. Never ask in a crisis, after a prayer request or of a child, never preselect a tip or a tier, and never promise that God will repay a gift.", "problem": "Giving is worship, and it pays for churches, missions and the apps themselves. More and more of it happens on a phone: through a church’s app, a QR code during the service, or a Give button in a Bible app. The same screens that make generosity easy can also press people: an amount chosen for them, a monthly gift switched on, a tip added on top, a gift tied to an ad-free app, an ask after someone has shared their grief, or the promise that a seed sown now will come back as a harvest.", "solution": "Put giving where someone looks for it, in a menu or after a service, not in the middle of reading or prayer. Start with an empty amount and a one-off gift; let the person switch on a regular gift and choose its day. Name who receives the gift and what it pays for, show fees as fees, send a receipt, and keep a history the person can stop or change in one place. Speak of what a gift does with current, complete and accurate figures, and say when enough has been given.", "failure": "A “Most popular” tier ticked in advance; a tip of a sixth of the gift added unless someone slides it to zero; a monthly gift switched on by default; a gift box on the screen after someone shares a prayer request; “Sow a seed of faith today and expect a harvest” beside a countdown; givers ranked by amount; a figure from five years ago presented as today’s; a recurring gift that can only be stopped by email.", "test": "Give the smallest possible gift in your app as someone new, then as someone who has just lost their job, then as someone who has just shared a prayer request. Write down every amount, tick and toggle that was chosen for you, every place the ask appeared, and how many steps it takes to stop a regular gift. Then read every sentence about what a gift will do, and ask whether you could show the figure’s source and date.", "sources": [ "apple-review-donations", "google-play-donations", "goswami-defaults", "karlan-recognition", "ministry-brands-2026", "ecfa-standards", "lausanne-prosperity", "fundraising-code", "gofundme-tip-letter", "irs-1771", "hmrc-gift-aid", "wochenblatt-kollekte", "givelify-store", "givelify-total", "nouwen-fundraising", "telefonseelsorge" ], "faith": "“Each one should give what he has decided in his heart to give, not out of regret or compulsion. For God loves a cheerful giver” (2 Corinthians 9:7). Jesus said that the poor widow who put in two small coins “has put more than all the others into the treasury” (Mark 12:43), and told those who give, “do not let your left hand know what your right hand is doing” (Matthew 6:3). When the people brought more than enough for the tabernacle, Moses “sent a proclamation throughout the camp” to stop (Exodus 36:6).", "related": [ "first-use", "notifications", "children-and-families", "sharing-with-a-group", "progress-and-streaks" ], "variants": [ { "title": "A · Giving stays with the church", "caption": "No ask in the app; a link to the church’s own way to give.", "when": "Bible readers and church-tax churches", "tradeoff": "Nothing pays for the app.", "items": [ "tag|Support", "text|Give through your church" ] }, { "title": "B · A quiet way to give", "caption": "A Give entry in a menu; no amount, one-off by default.", "when": "Most apps", "tradeoff": "Easy to miss.", "items": [ "tag|Give", "text|$0 · one-off" ] }, { "title": "C · The church’s offering", "caption": "Give to your church in the app, by fund, with a QR code at the service.", "when": "Church apps", "tradeoff": "Fees, and the church’s records in an app.", "items": [ "tag|St Luke’s · General fund", "text|Scan to give" ] }, { "title": "D · A regular gift", "caption": "A monthly or weekly gift the person sets, and can stop.", "when": "Steady support", "tradeoff": "Easy to forget it is running.", "items": [ "tag|Monthly · 1st", "text|Stop or change" ] }, { "title": "E · What a gift does", "caption": "Stories and figures about where the money goes.", "when": "Missions and translation", "tradeoff": "Figures age and can mislead.", "items": [ "heading|$25 a month", "text|Recordings in 3 languages" ] }, { "title": "F · A gift tied to a benefit", "caption": "Donate to go ad-free, or sponsor others’ subscriptions.", "when": "Apps that sell and also ask", "tradeoff": "A purchase dressed as a gift.", "items": [ "tag|Most popular", "text|Support & go ad-free" ] }, { "title": "G · Pressure and promises", "caption": "Seeds and harvests, tips added, asks after a prayer request.", "when": "Leave it out", "tradeoff": "Trades on faith and fear.", "items": [ "heading|Sow a seed today", "text|Expect your harvest" ] } ], "principles": [ "feed-the-flock", "enough", "speak-for-god" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone wants to give to their church, to a mission or to the people who make the app they use, simply and safely, and to know what happens to the gift.", "benefit": "A clear, quiet way to give lets people support the work they value at the moment they think of it, with a receipt, a history and a way to stop.", "drawback": "The tools that raise most, chosen amounts, ticked tiers, added tips, monthly by default, asks at emotional moments and promises of return, press people to give what they did not decide in their heart.", "differences": "A regular giver, someone new, someone short of money this month and someone who has just shared a prayer request read the same ask very differently.", "question": "What was chosen for the giver, where did the ask appear, what does the app say the gift will do, and how easily can a regular gift be stopped?", "check": "Give the smallest gift as someone new, someone short of money and someone who has just shared a prayer request; note every default and every ask; time how long it takes to stop a regular gift." } }, { "id": "109", "slug": "ai-memory", "topic": "conversation", "status": "Research-informed design proposal", "title": "AI memory", "summary": "From an assistant that keeps nothing, through context the person adds and a conversation they can see, to memory they switch on and can see item by item, and a profile the app builds from their prayers as a warning case: decide what the assistant may use, what it keeps, and whether the person can see and change it.", "takeaway": "Let the person see everything the assistant uses before it answers: the passage, any note or file, the conversation so far and each remembered item. Let memory be switched on once, then show each item in the conversation as it is saved, in its exact words; never keep feelings, health, sins or other people’s stories unless the person asks; let every item be edited and deleted; and never build a profile the person cannot see.", "problem": "A Bible assistant answers better when it knows what someone is reading, what they asked yesterday and what they are going through. But conversations in faith apps hold confessions, doubts, grief, illness and other people’s private stories. Chat products now remember across conversations, attach files and pages, and infer interests for personalisation. People disclose more to human-like assistants, and their picture of what is kept is often wrong. A remembered sentence can return weeks later in an opening message, a recommendation or an advertisement.", "solution": "Show context as visible, removable items beside the question: the passage, a note, a file, with what each will be used for. Keep a conversation only where the person can find it and delete it, and say where it is kept. Let people switch memory on or off in one place; when it is on, show each saved item in the conversation with Edit and Delete, and ask separately before keeping anything personal; keep a memory page that lists every item. Exclude special categories by default. Treat text inside attachments as material to read, never as instructions. Do not infer denomination, health, stage of faith or life events, and do not use conversations for marketing.", "failure": "A plus icon that uploads without saying so; a private journal sent along silently; removed items still used; “Memory updated” with no way to see what; a past loss raised in an opening message; feelings, sins or a friend’s situation remembered without asking; one switch for memory, training and sharing; profiles of “life events” and “faith stage” built from chats; recommendations and offers drawn from what someone confided; text in an attachment obeyed as an instruction.", "test": "Ask a personal question, then ask the person what the assistant now knows about them and where it is kept; compare with storage, logs and derived data. Remove an attachment and check it was not used. Decline a memory, edit one, delete one, then return the next day. Put an instruction inside an attached file and check it is not followed. Ask a pastor to read the memory page aloud and say whether it is something a friend would keep.", "sources": [ "contextual-integrity", "fair-game", "openai-memory", "gyroscope-coach", "hax-guidelines", "owasp-injection", "gdpr", "ico-special-inferences", "mozilla-prayer-apps", "hellobible-store", "canon-983", "augustine-confessions-x", "volf-memory", "playground-memory", "intent", "shape" ], "faith": "“O LORD, You have searched me and known me” (Psalm 139:1): to be fully known is what God alone does, and does in love. Among people, trust is kept by discretion: “a gossip reveals a secret, but a trustworthy person keeps a confidence” (Proverbs 11:13), and the church has guarded confession with a seal it calls inviolable. God also promises to forget: “I will forgive their iniquities and will remember their sins no more” (Hebrews 8:12). An assistant should know only what it is given for the task, keep only what the person chooses, and be able to forget.", "related": [ "ai-persona", "ai-citations", "check-ins-and-assessments", "prayer", "ai-answer-actions" ], "variants": [ { "title": "A · Nothing kept", "caption": "Each conversation starts blank and is gone when closed.", "when": "Quick questions; sensitive moments", "tradeoff": "No continuity.", "items": [ "tag|Not kept", "text|Tell me where you’d like to start." ] }, { "title": "B · Context you add", "caption": "The passage and a note as removable chips.", "when": "Study and preparation", "tradeoff": "People must add context each time.", "items": [ "tag|Mark 4:35–41 · ×", "text|Send with 2 items" ] }, { "title": "C · This conversation", "caption": "A visible thread you can return to or delete.", "when": "Ongoing study", "tradeoff": "Everything in it is kept.", "items": [ "tag|Kept on this phone", "text|Delete conversation" ] }, { "title": "D · Memory you can see", "caption": "Switched on once; each saved item shown with Edit and Delete.", "when": "Long-term companionship in study", "tradeoff": "Needs a memory page and honest storage.", "items": [ "tag|Saved to memory · Edit · Delete", "text|Remember this too" ] }, { "title": "E · A profile it builds", "caption": "Life events, feelings and faith stage inferred.", "when": "Avoid", "tradeoff": "Confidences become targeting.", "items": [ "tag|Inferred from your chats", "text|Life events: job loss" ] } ], "principles": [ "welcome", "speak-for-god", "most-vulnerable" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "Someone asks an assistant about a passage or their life, and the assistant uses context, a conversation or remembered details to answer.", "benefit": "Context makes answers specific; continuity saves repeating oneself; a remembered reading plan or question can make the next conversation easier.", "drawback": "Faith conversations hold confessions, health, doubt and other people’s stories; invisible memory and inferred profiles turn them into data that can resurface, leak or be sold.", "differences": "A student preparing a talk, someone praying in grief, a teenager, a person in an abusive home and someone sharing a phone need very different defaults.", "question": "Could the person list everything the assistant knows about them, and would they be comfortable if a friend read it?", "check": "Compare what people think is kept with storage and derived data; remove, decline, edit and delete items; return the next day; test instructions hidden in attachments." } }, { "id": "94", "slug": "reading-settings", "topic": "reading", "status": "Editorial design proposal", "title": "Adjust reading settings without losing the passage", "summary": "Keep typography, appearance and text-layer preferences close to the reading experience.", "takeaway": "Let people judge changes against the passage they are reading, and preserve their place when the text reflows.", "problem": "Leaving the reader to change typography separates the choice from its effect. A crowded settings drawer can obscure the text, while a font-size change can move the reader to an unrelated line.", "solution": "Offer a labelled reading-settings entry near the passage. A bottom drawer keeps some context visible on mobile; a side panel can retain more readable context on wider screens. Preview typography and appearance against real text. Group font, size and spacing separately from optional verse numbers, notes and section headings. Preserve the semantic reading anchor after reflow. Explain whether changes apply immediately, provide reset, and distinguish persistent preferences from a temporary view.", "failure": "Tiny slider-only adjustments; unlabeled spacing icons; hiding verse numbers and losing reference access; hiding a note marker as though the note were deleted; fixed drawer height that clips controls at large text; changing edition while claiming to change appearance.", "test": "Open settings midway through a long chapter, increase text size, change spacing and hide verse numbers. Dismiss and locate the same verse. Repeat with keyboard, screen reader, narrow viewport, poetry and large system text. Test reset and returning after restart if persistence is promised.", "faith": "A quiet layout is a preference, not a measure of spiritual seriousness. Notes, red-letter styling and editorial headings influence interpretation; let people understand which layers they are changing without implying that hiding them removes Scripture.", "sources": [ "mere-captures", "mere-current", "wcag-reflow", "usfm-paragraphs", "diagram-psalm-kjv" ], "related": [ "reading-layout", "verse-numbers", "text-structure", "translation-position" ], "flow": [ "Open reading settings from the current passage.", "Adjust a clearly labelled preference and inspect the effect.", "Keep the same reference visible when typography reflows.", "Dismiss or reset, then continue reading; preserve preferences only as explained." ], "variants": [ { "title": "A · Bottom drawer", "caption": "Keep a portion of the passage visible above the controls.", "when": "A mobile reader needs occasional adjustments in context", "tradeoff": "A tall drawer leaves little preview; support scrolling controls and an explicit close action.", "items": [ "heading|Psalm 23 · BSB", "psalm|one", "settings|", "links|Reset reading settings" ] } ], "illustration": { "visual_style": "paper prototype pilot", "fidelity": "medium", "annotation_style": "rounded right-angle wires", "relationship": "A settings drawer in reading context", "screens": [ { "title": "Psalm 23 · BSB", "annotation": "The passage remains visible above the drawer. These are original proposals informed by the contributed Mere Bible screen.", "blocks": [ { "kind": "psalm", "text": "one", "extra": "" }, { "kind": "settings", "text": "", "extra": "" }, { "kind": "links", "text": "Reset reading settings", "extra": "" } ] } ] }, "diagram_decisions_owned": true, "principles": [ "offering", "word-distinct" ], "publication_status": "published", "editorial_review": { "date": "5 October 2026", "scope": "Editorial review; not user validation", "purpose": "A reader adjusts presentation to suit their current needs.", "benefit": "In-context preferences make the effect easier to judge without leaving the passage.", "drawback": "Preview space competes with controls, and reflow can cause lost place.", "differences": "Low vision, large text, close study and quiet reading call for different settings; one person may need several configurations.", "question": "Can the person change presentation without losing content, reference access or their place?", "check": "Adjust size and spacing mid-passage, dismiss and return; verify focus, reference and reset." } } ]