InSpiritInTruth
Faith personalisation. A devotional written for what you are actually carrying today, engineered so an app that quotes scripture can never quietly misquote it.
A devotional app for imperfect journeys — the overwhelmed, the curious, the unchurched, the devoted. The format has looked the same for generations: one text for everyone. ISIT keeps the rhythm and adds the part it never had.
A format that never changed
The devotional is one of the oldest content formats there is: a passage, a reflection, a prayer, the same page for everyone. That sameness is its comfort and its limit. Someone carrying something specific today has never been met where they are.
ISIT keeps what is worth keeping — a weekly devotional written by a person, the whole Bible, no algorithm, no ads — and adds the missing piece. Share what you are going through and it writes one for exactly that, rooted first in Scripture.
Personalisation with a safety net
Generated spiritual guidance is higher-stakes than most AI writing. It has to carry authority without hallucinated certainty. So the generators run on the model that ranks first for restraint and coherence — here, restraint is the feature and creative risk is the failure mode. A cheaper, edgier model was tested on the real prompt and turned down twice.
And nothing generated reaches a reader unverified. Every tailored devotional passes through a fact-check that searches the live web to verify its claims before publication — a pass that deliberately costs several times more than the writing itself.
Where the AI effort goes
The share of machine effort behind one tailored devotional. Most AI products spend everything on generation; ISIT spends most of it making sure the generation told the truth.
| Stage | Share of effort | What changed |
|---|---|---|
| Writing | ~22% | The devotional itself, drafted from what you shared. |
| Verifying | ~77% | Live web-search fact-checking of every claim, before a reader ever sees it. |
| Reflecting | ~1% | The closing reflection pass. |
That ratio is a choice. Verification is the one cost this product will not cut to protect a margin, so the subscription is tuned around keeping it.
Care for the text
An app that quotes scripture carries a special obligation: the words on screen must be exactly what they claim to be. Three of the rules that came out of the build:
- Label + text
- Move together, alwaysA verse's translation label is only ever updated when its text was actually re-fetched in that translation. The bug this rule killed: a failed fetch publishing NKJV wording tagged “NET” — a lie a reader can never detect.
- Device date
- Not the server's, not UTCThe daily verse broke three times by rolling over on UTC midnight instead of the reader's own — showing tomorrow's verse at 1am. Now a hard rule with the reproduction documented.
- No italics
- In scripture passagesRetired across the app: emphasis the original text does not carry is editorialising. The passage is presented as written.
Design follows the same discipline — the devotional hero is bottom-anchored and ratio-sized, the type system is two families rather than three, and generated devotionals draw from a closed, server-enforced set of themes rather than whatever a model invents.
The screens
What I'd do differently
Define “today” on day one. The daily verse rolled over on UTC midnight instead of the reader's clock, and that assumption shipped three times before it became a written rule. Decide whose midnight you honour before the first query.
Measure the cost of honesty before pricing it. The fact-check pass dominates the machine cost of a tailored devotional — several times the writing itself — and that was discovered after the price was set. Instrument first, price second.