Library
The shared workspace for Read, Search, Saved, Plans, Prayer, and Study Tools.
BibleBeacon · Product design + AI-assisted development
How I designed and directed an offline-friendly Scripture product and used AI assistance to accelerate bounded implementation, testing, troubleshooting, and documentation.
Product Strategy · UX/UI · Information Architecture · AI-Assisted Development · Local-First Design · Release Governance
Reading, listening, discovery, study tools, games, and private device-local progress in one product system.
The opportunity
BibleBeacon began as a lightweight Scripture challenge. The design opportunity was to support quick play, reading, search, listening, discovery, saving, planning, prayer, study, and return loops while keeping entry simple and the product visually coherent.
The selected direction uses one cinematic visual system, six stable primary destinations, and a shared Library for related personal study work. Core text and study indexes are bundled, personal material stays on the current device, and no account is required in release 0.16.0.
My role
I defined and directed the product. AI helped accelerate selected work inside explicit requirements, privacy boundaries, source rules, acceptance criteria, and review gates.
Experience strategy
Start from a clear home screen with low-friction routes into play, study, listening, or discovery.
Move from a short activity into deeper reading or study without creating an account.
Read, Search, Saved, Plans, Prayer, and Study Tools share one related workspace.
Resume positions, saves, progress, missions, quests, and review scheduling support return visits.
Personal progress and study material remain in versioned device-local storage.
Approved text and study data retain source, revision, license, attribution, and checksum records.
Experience the product
This interactive panel loads BibleBeacon directly from its production domain. Try the navigation, open the Library, explore a game, or launch the product in a separate tab for the full browser experience.
Live content is served by biblebeacon.sardev.io and may reflect changes made after this case study was prepared.
Feature walkthrough
The shared workspace for Read, Search, Saved, Plans, Prayer, and Study Tools.
Four bundled translations, chapter navigation, resume state, and responsive comparison.
Words, phrases, topics, and direct references resolve against the bundled corpus.
Bookmarks, highlights, and notes stay in one searchable device-local collection.
Three short reading paths with local completion, resume, streaks, and optional reminders.
Private prayer and reflection records with structured states and local lifecycle controls.
Approved local indexes for people, places, relationships, Strong's metadata, and topics.
Book and chapter navigation for 260 supplied New Testament recordings with resume and low-data mode.
Curated Scripture cards organized into Stories, Teachings, People, and Wisdom.
A four-choice missing-word experience grounded in pinned local WEB text.
Ten local word-connect levels with hints, rewards, daily play, progress, and sequential unlocks.
A device-local view of sessions, streaks, review, mastery, missions, quests, and recent activity.
Evidence boundary: the page documents product capabilities and observed release behavior. It does not claim user adoption, retention, conversion, revenue, customer satisfaction, or business ROI.
System design
Release 0.16.0 uses TypeScript and Vite, bundled content, versioned local browser storage, a static Node 20-compatible service, and a separately managed audio directory. It does not activate accounts, remote databases, payments, analytics, or a runtime Bible API.
AI-assisted development
I set the problem, requirements, constraints, user behavior, privacy boundary, and release scope.
AI helped compare options, research approaches, draft plans, and surface implementation alternatives.
AI supported scoped coding, data adapters, migrations, tests, and documentation against the current baseline.
I evaluated outputs against the intended experience, sources, rights, privacy, architecture, and operating constraints.
Weak concepts, unsafe assumptions, regressions, and brittle approaches were rejected or revised.
Accepted work advanced only after source inspection, tests, builds, browser checks, and explicit status assignment.
QA / QC
Current repository tests cover product behavior and data integrity.
Typechecking, linting, and the production build passed for the verified 0.16.0 record.
Desktop and requested mobile browser checks covered core flows and horizontal overflow.
Release metadata, the service worker, and direct game routes returned HTTP 200 in the verified release record.
These checks verify implementation and release behavior. They are not a formal usability study, audited accessibility certification, penetration test, or proof of product adoption.
Important correction
An early deployment replaced the web root while the large, separately managed audio path was excluded from the smaller web archive. The application remained available, but expected audio URLs returned 404.
The failure was an architecture and release-boundary issue, not a player-interface defect: web assets and the roughly 549 MB, 260-file audio library had different deployment lifecycles.
Later releases preserved the audio directory, separated web packaging from media synchronization, retained fallbacks, documented rollback, and verified all expected audio URLs plus representative range delivery.
Product evolution
Rebrand, challenge, XP, levels, and achievements.
Timeline, missions, Beacon Log, review, paths, and quests.
Installable PWA, offline shell, and connection status.
Sharing, Discover, chapter audio, and the full listening library.
Reader, Search, Saved, Plans, Prayer, study, and comparison.
Offline study data, imports, manifests, and source review.
Ten local levels, daily play, rewards, and progress.
Final missing-word interaction, history behavior, and refinement.
Verified outcomes
Lessons learned
Incremental releases reduced regression risk. Local-first data reduced runtime dependencies. Explicit source manifests made provenance reviewable. Separating web and media deployments protected the audio library. Shared Library information architecture prevented feature fragmentation.
Next improvements include formal design-decision logging, structured usability testing, and lazy-loading or code-splitting for larger payloads.Visit the live product
Explore the working product, review the full design and AI-assisted development report, or return to the portfolio collection.