Mobile App
Versology
A mobile study environment that treats scripture as layered knowledge: text, terms, culture, and history in one searchable archive.
Versology turns Bible study from an endless tab-switching exercise into a single place where “what does this passage mean?” can be followed all the way to context—without losing the thread.
Tech stack
Architecture
Shape. Web reader + Capacitor iOS shell; Supabase + OpenAI only on server routes (keys never client).
- Next.js 15 — Marketing vs study areas; RSC prefetch; client islands for search and scripture nav.
- React 19 — Search and cross-refs stay responsive; TipTap isolated from heavy list virtualization.
- TypeScript — Archive types (passages, terms, people) and API contracts aligned with Supabase data.
- Tailwind v4 — Reading layouts, dark tokens; v4 + PostCSS without a parallel CSS architecture.
- Radix UI — Accessible dialogs, comboboxes, focus/ARIA for desk and mobile study.
- shadcn-style UI — CVA variants + tailwind-merge for consistent buttons/cards and safe class merges.
- Framer Motion — Panel choreography and cross-fades; scoped to client subtrees only.
- TipTap — Notes/snippets editor with constrained schema; JSON serialization for storage.
- Capacitor 7 — iOS keyboard + safe-area so reading chrome does not jump on focus.
- Supabase — Auth, Postgres archive tree, optional realtime for cross-device progress.
- OpenAI — Server `/api/chat` streams tokens (SSE); prompts never exposed in the client bundle.
What Versology does
- →Provides a central archive of biblical concepts, people, places, and themes—organized for lookup during reading or teaching prep.
- →Surfaces historical and cultural context (period, setting, genre expectations) so interpretation is grounded in more than modern intuition.
- →Connects cross-references and related ideas so study accumulates: today's question strengthens yesterday's map of the text.
- →Prioritizes clarity of navigation on mobile—where serious readers increasingly read, highlight, and search.
Typical study stack
Bible app + browser tabs + notes → fragmented context, lost citations
With Versology
One structured archive → look up → read context → follow threads
The core problem
Serious Bible study is knowledge work. Knowledge work breaks when sources are scattered and unstable.
Readers bounce between translations, commentaries, search results, and forums. Each hop risks low-quality summaries, outdated cultural assumptions, or outright misinformation. Even thoughtful learners struggle to maintain a coherent notebook across apps that were not designed to link concepts.
Devotional and reading-plan apps solve a different job: rhythm and encouragement. They often stop short when the user asks a deeper historical or linguistic question—precisely where a reference archive earns its keep.
The pain shows up as:
- Time lost to search instead of synthesis
- Shallow confidence—copy-pasting takes without understanding provenance
- Abandoned study habits when friction exceeds reward
Design insight
Understanding scripture is cumulative. Concepts reappear across books; places gain meaning as narratives unfold; theological terms carry technical weight. A product that only shows one verse at a time fights how human memory works.
Versology treats the Bible as a network to explore, not a flat feed: each entry should invite the next question—who else, where else, what else happened here—with surfaces that stay readable on a phone.
Differentiation
The market splits roughly into reading experiences (daily verse, audio, plans) and heavy desktop software for specialists. Versology targets the middle: motivated non-specialists who want depth without seminary tooling.
It is reference- and exploration-first, not streak-first: the success metric is whether the user leaves with a clearer grasp of the text’s world—not only whether they tapped “done” today.
Contrast
Devotional apps: Keep you opening daily; thin on structured reference when questions arise.
Versology: Optimizes for inquiry—terms, timelines, and threads that support real comprehension.
The study loop
- Encounter a question. Reading surfaces an unfamiliar name, place, or idea.
- Look up in-archive. The user jumps to an entry that defines the concept and situates it historically.
- Read context, not only definition entries. Culture, genre, and setting frame what the original audience would have heard.
- Follow links. Related passages and themes build a personal map of scripture instead of isolated facts.
- Return to the text informed. The loop closes when the reader re-reads with sharper eyes—not when a checklist increments.
Why “Versology”
The name signals the product’s ambition: verse as the anchor, -ology as systematic study—not a motivational quote generator. It communicates depth without pretending to replace community, preaching, or scholarly guilds.
What Versology optimizes for
Comprehension and navigability—not maximizing shallow session count. The wedge is trust that the archive is organized for study, not for engagement hacks.
Clarity — Can a motivated reader find the right entry in seconds, not minutes of search?
Depth with guardrails — Does context reflect mainstream historical scholarship and avoid sensational claims?
Cumulative learning — Does the IA reward return visits with richer connections?
Strategic framing
Faith-tech often competes on content licensing or personality brands. A durable moat in this category can be information architecture: the graph of concepts, the quality of summaries, and the discipline of linking—i.e., the product is the library and the map.
Versology points at a long-term position: become the default pocket reference for readers who have outgrown atomized daily content but are not yet power users of academic tools.
Product stance
Theological nuance demands humility in UI copy and sourcing. A shipping product would need editorial standards, attribution for paraphrases, denominationally transparent coverage where interpretations diverge, and accessibility for long reading sessions.
Technically, Versology was scoped as a two-month full-stack sprint: prove the core navigation and content model on-device, with performance and offline behavior as next-layer concerns.
Product demo
Prototype walkthrough: archive navigation, article views, and transitions as implemented for the build.