An evolving discovery register

Discover further design questions.

App examples reveal choices that deserve comparison, documentation and evaluation. Observations below are starting points for research, with their evidence type stated.

These observations inform design questions. They are not usability findings or newly validated patterns. Historical behaviour and documented behaviour need fresh testing before they guide a current implementation.

Publisher documentation

A resource guide follows; a parallel resource stays open

Olive Tree distinguishes a passage-following resource index from sustained reading of a selected resource.

Decision to investigate: Should changing the main passage refresh suggestions, preserve the secondary document, or offer both modes?

Inspect the app evidence

Publisher documentation

Exploration can temporarily break synchronisation

A secondary scroll can unlink panes without disabling the possibility of linking them again.

Decision to investigate: Can the reader recognise who controls the shared anchor and recover from accidental divergence?

Inspect the app evidence

Historical publisher documentation

Density is a reading preference

A saved-item collection can prioritise scanning or richer verse previews, with a remembered choice.

Decision to investigate: Which metadata must survive in compact mode, and should large text override the preferred density?

Inspect the app evidence

Directly observed web interaction

Comparison state can be addressable

The YouVersion comparison URL includes the secondary edition; each pane retains its own selector.

Decision to investigate: Should a shared reference preserve comparison state, and how should unavailable editions be resolved?

Inspect the app evidence

Directly observed prototype interface

Personalisation choices can carry spiritual authority cues

Companion-style labels frame an AI-assisted practice before generation.

Decision to investigate: Does the selected style change tone, content or perceived authority? How can those boundaries be made understandable?

Inspect the app evidence

Directly observed Android prototype interaction

The visible passage, selection and study context can differ

Returning to the VSB reader preserves a selected verse and collapsed study reference alongside a different viewport reference.

Decision to investigate: Which anchor should control translation switching, parallel reading, audio following and a return-to-selection action?

Inspect the app evidence

Directly observed signed-out web interaction

Engagement choices mix intent and experience

Lumen’s onboarding offers curiosity, starting or returning, growth and study; skipping reaches a complete home screen.

Decision to investigate: Can a session-specific intent be selected without storing a permanent faith identity or making depth a hierarchy?

Inspect the app evidence

Directly observed signed-out web interaction

Phrase-grouped reading differs from verse-row comparison

Lumen changes a phrase-grouped chapter into paired verse rows when Compare is activated.

Decision to investigate: How do line grouping, shared verse heights and edition identity affect reading continuity and comparison?

Inspect the app evidence

From observation to reusable guidance

  1. Capture the entry, action, resulting state and recovery on named devices and releases.
  2. Compare other implementations and identify the common task.
  3. Separate interface observation, provider claims and measured user outcomes.
  4. Describe alternatives and tradeoffs, then evaluate comprehension and control with relevant readers.
  5. Revise a pattern or add a new family when the decision is sufficiently distinct.