Answers, feedback, progress and completion are available in the interactive demo.
Faith App — Orthodox learning, Scripture and a patristic library
We designed and built an iPhone-oriented technical build in Flutter: short lessons, a knowledge map, an offline Bible, difficult-passage notes and local progress. The project is preparing for publication and external theological review.
A technical app build before publication
The Synodal Bible, bundled content and progress work without a network; downloaded books are verified by SHA-256.
Substantive lessons cannot be considered publication-ready without a qualified reviewer.
How we assemble a substantial lesson
These are not illustrative KPIs. They are two real blocks from the current working build. We connect every screen to a named source, constrain reading load and protect important boundaries with targeted tests.
Exercise formats
The observed composition of 3,857 exercises in the read-only snapshot from 14 Aug 2026.
Two lessons under magnification
verified 14 Aug 2026Father of faith: gift and living response
- screens
- 6
- words
- 326
- sources
- 6
- regressions
- 14
Covenant, sign and promised son
- screens
- 7
- words
- 375
- sources
- 7
- regressions
- 13
The content pipeline and its boundary
The generator matches the app's active JSON, sources and illustrations are registered, and the quiz contract remains intact.
External content review, a physical device, a signed Archive and TestFlight remain required before public release.
The questions and explanations come from working blocks T-A-005 and T-A-002. This demo is not connected to an installed app; the theological content still awaits external review.
From a first question to durable progress
A difficult subject becomes a short repeatable loop: gain context, answer, understand the feedback and continue without losing progress.
Choose a path and a short lesson
The learner starts with a guided sequence instead of an unstructured library.
Build the missing context
Theory arrives in slides, while unfamiliar terms open as linked glossary cards.
Answer and understand the mistake
Options are shuffled between questions and feedback teaches meaning, not button position.
Keep progress on the device
Completed lessons, reading position and saved material stay local without requiring an account.
Continue the course
Progress opens the next part of the learning path.
Explain, do not punish
The learner receives context and can continue the loop.
Expert review
Every substantial lesson requires external review before release.
The topic has a high barrier to entry: the sources are either texts from two centuries ago that you have to decode first, or reference sites built like a library rather than a course. Someone ready to take a step googles their first question, gets three screens with twenty unfamiliar words, and closes the tab. A format that leads you from zero step by step doesn't exist in mobile form.
Flutter for iOS with a local-first architecture and no required account, ads or user analytics. Bundled lessons, the Synodal Bible and progress work without a network. Additional Bible translations and the book catalogue use the network; downloaded book files are verified by SHA-256. Local notifications are implemented technically, while permissions and behaviour on a current physical iPhone still need verification.
The quick gate from 14 August confirmed code analysis and hundreds of tests, but the current working slice changed after the latest full iOS gate and is not yet backed by a green CI run. We therefore keep four statuses separate: implemented, technically checked, device QA required and specialist review required.
Structural tests confirm data integrity; they do not replace theological expertise or behaviour checks on a physical device.
The right option was systematically the longest: the author padded it with an explanation and left the wrong ones terse, so a sharp reader could guess by shape without knowing the topic. The second, found on the device: the correct answer stood first in every question, because options rendered strictly by index.
Fixed in two layers. In the code, we shuffle the options, but not in the render method: it's called on every state update, and the buttons would jump under your finger. We had to find every transition between questions and shuffle there, and at the same time move five correctness checks from list position to the answer object itself. In the content, we set a rule: options of equal length and grammatical form, the correct position spread evenly, wrong options are real beginner misconceptions, not straw men. Verified by a script at content build time.
Why both layers: shuffling makes the order in the source harmless for the app, but drafts are read by real people: author, reviewer, editor. A document where the correct answer is always first breeds blindness in everyone who proofreads it.
- Course branches with a glossary and figures in inflected forms.
- Lessons built from theory slides and quizzes; answer order is shuffled so the correct one isn't tied to a position.
- Substantial lessons are not ready to publish without external expert review.
- All 77 books of the Synodal Bible are bundled for offline reading; KJV, WEB and the book catalogue use the network.
- Progress and downloaded material stay on-device; the current project has no required account, advertising or user analytics.