Paper review · Bible apps and persuasion

Design and the digital Bible

Persuasive technology and religious reading

The closest published precedent to our work: how YouVersion and Glo Bible were designed to shape reading.

Tim Hutchings, “Design and the digital Bible: persuasive technology and religious reading”. Journal of Contemporary Religion 32, no. 2 (2017): 205–219. doi:10.1080/13537903.2017.1298903. Publisher’s page.

Read in full from the published PDF, 10 November 2026. Quotes give the page.

In one paragraph

Tim Hutchings is a sociologist of digital religion. In this short paper he studies two Bible apps, YouVersion and Glo Bible, through the products themselves, interviews with their leaders in 2013 and their public blogs. Early writers expected digital Bibles to make the text fluid and free. Hutchings finds the opposite: carefully structured persuasive technology that leads users into particular reading practices, frequent, personal and shared, and into the evangelical understanding of reading behind them. His conclusion is the paper’s sharpest line: this kind of design exerts influence without claiming authority.

Three takeaways

  1. Plans, reminders and badges are persuasion.

    He finds all seven tools of the standard persuasive-technology scheme at work across the two apps: a plan reduces reading to short daily tasks and tunnels the reader through them; reminders suggest; badges condition; stored reading data is surveillance. The designer chooses the path.

  2. The guilt is older than streaks.

    Users he interviewed split the way our own do and don’t lists predict. One calls the daily reminder “great accountability”, others an annoyance. A third says it helps precisely because it makes you “feel bad if you don’t!”. The same mechanism works through mild guilt.

  3. Influence without claiming authority.

    The app shapes how millions read while their attention stays on the Bible. Who made it, and why, stays in the background; Hutchings notes how rarely YouVersion’s ownership by Life.Church is mentioned.

This use of design exerts influence without claiming authority.

Tim Hutchings, page 217

What it means for design

Proposals for our patterns, drawn from the book. They are not yet part of the published pattern pages.

Reading plans
Name what a plan does: it chooses a path and trains a practice. That can serve formation or engagement; the pattern’s options help you see which.
Progress and streaks and Notifications and reminders
A reminder that sounds like a person can carry the shame without any streak on screen. Let the person set the wording and timing, and treat a missed day as nothing to repay.
Whose theology
Say who made the product and from which tradition. A Bible app is a religious actor whatever its press page says.
AI memory
Unease about a product’s memory of someone’s spiritual life is older than AI. In 2013 YouVersion’s own leaders voiced concern about the limits of reading-data analysis. AI intensifies an unresolved question.
Sharing with a group
An early YouVersion feature offered to contact a mentor the reader had named when agreed reading targets were missed. It attracted little activity and was quickly sidelined. Accountability machinery alone did not create use; design for people who already know each other.
Engagement claims
A much-quoted claim that benefits appear only when people read more than four times a week rests on self-reported data with causation unexplored, as Hutchings notes. Don’t claim that frequency produces spiritual outcomes.

getting reminders to keep to the reading plan is like having another person telling you to do it, so you feel bad if you don’t!

Tim Hutchings, an app user, from Hutchings’s 2015 study, quoted on page 214

Where we differ

Hutchings describes; he does not prescribe. He offers no account of what formation should be, no theological alternative and no design guidance. That gap is where our patterns try to help.

We would not treat structure itself as the problem. The church has always shaped how people read: lectionaries, the daily offices, the readings of the church year. The question is whether the structure is visible and can be questioned, adopted or set aside. Ian Bogost, whom Hutchings draws on, contrasts persuasion that changes behaviour without engaging the person in why with a model the person can interact with and then support, question or resist. Hutchings reads the Bible apps as both. Our spectrum grids aim at the second.

And frequency is not faithfulness. The designer’s ideal path is not the person’s calling; a rhythm kept with grace can include rest, return and seasons of silence.

Who should read it

  • Anyone building reading plans, reminders or progress features in a Bible app.
  • Ministry leaders whose organisation runs an app, and researchers looking for the academic background.
  • It is fifteen pages; read it in one sitting.

Design and the digital Bible at Journal of Contemporary Religion (Taylor & Francis). No affiliate link.

guide them along what we consider to be the ideal path

Tim Hutchings, Nelson Saba, founder of Glo Bible’s maker Immersion Digital, interviewed, page 212

Evidence and limits

  • Designers’ interviews and marketing. Hutchings warns that management interviews emphasise achievements consistent with company policy. Designers’ intentions are well documented; effects on readers are not.
  • Few user voices. Claims about what the apps do to readers are structural arguments with a few quoted users, not measured effects.
  • A 2013–2015 snapshot. Streaks and AI features postdate the study. Quote it for the design philosophy, not today’s features.
  • Two evangelical products. No Catholic, Orthodox, mainline or European app.
  • Behind a paywall. Check access before pointing others to it.

Cited studies we have not checked yet

What the book reports, as it reports it. We don’t cite these as findings until we have read the original.

Study, as citedWhat the book reportsStatus
Cole and Ovwigho, 2012 (Center for Bible Engagement)Reported benefits appear only when people read more than four times a week; self-reported, causation unexplored.Not yet checked
Hutchings, 2015cHis earlier study, the source of one user quote on reminders.Not yet checked
Eyal, 2013A magazine piece framing a Bible app as habit engineering.Not yet checked