Summary

Add the ability for users to select and copy scripture text rendered by the mobile Rock:BibleReader control — either through native text selection (press-and-hold → select → Copy) or a built-in per-passage/per-verse “Copy” action.

Problem

The BibleReader is display-only. Because it renders verse text as native .NET MAUI Labels (which are not selectable by default), users cannot copy any scripture from within the app. People regularly want to:

• Copy a verse into a text/message, social post, or notes app
• Paste a passage into a small-group discussion or sermon-prep doc
• Share the exact wording (not just a deep link)

Today, the only sharing affordance is the header Share button, which shares a reference + deep link (“Read John 1 with me in the Vox Church app!”) — not the text itself. There is no supported way to expose the scripture text from a content block, since the licensed NLT/ESV/MSG text comes through the Spark Data API and is not surfaced to Lava or as a binding. That means this genuinely cannot be solved at the church/config level — it needs a control/shell enhancement.

Proposed Solution (any one of these would solve it)

1. Native text selection — enable OS-level text selection on the verse Labels inside the BibleReader (e.g. Android SetTextIsSelectable(true), iOS long-press selection). Ideally gated by a control property so it’s opt-in:

   <Rock:BibleReader ... IsTextSelectable="true" />

2. Built-in “Copy” action — a per-verse or per-passage copy affordance (long-press a verse, or a copy icon) that places the verse text + reference on the clipboard, respecting the active translation’s copyright/attribution string.
3. Expose the reading text — surface the rendered passage text as a bindable/Lava-accessible value (e.g. BibleBrowser.Reading.Text) so implementers can wire it to the existing CopyToClipboard command themselves.

Option 1 is the most natural UX; option 3 is the most flexible for builders.

Acceptance Criteria

• A user can copy scripture text from the BibleReader on both iOS and Android.
• Copyright/attribution requirements for the active translation (ESV/NLT/MSG via Spark Data API) are preserved on copy.
• Behavior is opt-in or otherwise doesn’t regress existing reading UX (scroll, tap-to-open picker, audio).

Technical Notes / References

• MAUI Label is not selectable by default; selection typically requires a platform handler mapping (Android SetTextIsSelectable, Windows IsTextSelectionEnabled). This is why it can’t be enabled from a Lava/XAML content block and needs a shell/control change.
  • MAUI Label docs: https://learn.microsoft.com/en-us/dotnet/maui/user-interface/controls/label
  • Known MAUI wrapping bug when enabling selection to be aware of: https://github.com/dotnet/maui/issues/29033
• Rock Mobile already ships a CopyToClipboard utility command, so option 2/3 could reuse existing plumbing: https://community.rockrms.com/developer/mobile-docs/essentials/commands/utility-commands
• Current BibleReader docs (no selection capability today): https://community.rockrms.com/developer/mobile-docs/essentials/controls/content-controls/bible-reader

Alternatives Considered (and why they don’t work at the config level)

• WebView with HTML scripture: gets native selection, but loses audio, translation switching, verse formatting, and native navigation — and still has no licensed text source to render.
• Read-only Editor: inconsistent/limited read-only selection support across platforms; reads as an input field.
• Fetching text from a third-party Bible API: violates NLT/ESV licensing, which is precisely why Rock routes text through the Spark Data API.

Impact

Low-risk, opt-in enhancement to a widely used control. Directly improves scripture engagement and sharing, which aligns with the reader’s purpose.