Building Shalom: how we designed a Bible app for consistent daily discipleship

Overview

Over roughly six weeks, from July to August 2026, Shalom went from an initial product concept to a live, offline-first daily discipleship product. It now holds 100 authored study days across five learning paths, a nine-step daily experience, habit mechanics, personal notes and prayers, sharing, Bible character journeys, and community-based Discipleship Circles.

The result is not simply another Bible-reading app. Shalom is a daily Bible companion designed to help you read, understand, remember and apply Scripture in five to eight minutes a day.

The home screen

A wise dove who never nags, ranks, or shames.

Good morning, Zamai — a new word to carry today.

Knowing God · Day 12

Your rhythm

current rhythm: 3lifetime: 42 days

Begin today’s reading

Your path

Knowing God

11 of 21 days

Home

The problem

The problem is not access to biblical content. People already have Bible apps, sermons, devotionals, podcasts, YouTube channels and thousands of reading plans. The deeper problem is turning access into consistent spiritual practice.

Early research and product discovery kept returning to five challenges:

• Inconsistent Bible reading.
• Difficulty understanding Scripture.
• Difficulty remembering biblical stories and characters.
• Trouble connecting Scripture with everyday life.
• No clear structure for spiritual growth.

At the same time, many existing solutions created another problem: too much content. You could open an app, find hundreds of plans, translations, devotionals and sermons, and still wonder:

What should I actually do today?

That framed a different opportunity. Instead of building another content library, Shalom became a daily discipleship system combining habit, learning, memory and application. The core product promise followed:

Grow spiritually in just 5–8 minutes a day through guided Bible reading, simple explanations and daily application.

That time constraint became one of the most important design decisions in the entire product. Shalom works for someone opening the app before work, during a commute, or late at night.

The emotional problem matters too

Habit products often rely on anxiety: red warnings, broken streaks, countdown timers, loss aversion, rankings, notifications telling you that you are falling behind. Those mechanics can work for language learning or fitness. Inside a spiritual product, we believed they had to change.

Someone returning to Scripture after missing several days should not be greeted by a screen telling them they failed. That led to one of Shalom’s defining principles:

Encourage consistency without turning spiritual discipline into guilt.

The in-house brand guide formalises it. Shalom is wise, gentle, consistent, uplifting and trustworthy — and it must never become a guilt machine, a hype bot, or a childish cartoon character.

Our product thesis

Reduce the effort required to begin, give every session a clear ending, and make returning feel emotionally safe. Instead of asking you to decide what to study, Shalom makes the next step obvious.

The original daily loop was short:

Open → Scripture → Explanation → Insight → Quiz → Action → Progress

As we designed and tested the experience, that loop grew. The session now runs nine stages, and what began as a Bible-reading flow became a compact learning cycle: read, understand, remember, reflect, pray, act.

The solution

Shalom’s daily loop, and the mascot that carries it, in one line: a wise dove who never nags, ranks, or shames.

Brand before build

Before any product decisions were made, we wrote the mascot’s brand personality guide: an archetype (the Sage — power through wisdom, not authority), five personality pillars, and, critically, an explicit banned-word list. Pairing a “say this / not this” table with that list meant later copy decisions had a test to fail, not just a vibe to match.

One guided session instead of an infinite content feed

The most important interface decision was restraint. Shalom does not open onto a library. Home answers one question — what should I do today? — and each session is short, progressive and finite. That gives you something content products often fail to provide: a clear definition of done.

“Know God” instead of just “know more”

Comprehension alone is not the outcome. Every session carries one clear insight about God — his patience, faithfulness, justice, grace. That changes the mental model from “I completed another reading” to “I learnt something about God today.” Shalom is not optimised for content consumed. It is optimised for understanding gained and carried into the day.

A mascot that functions as interaction design

The mascot is the product’s emotional interface rather than decorative branding — closer to a trusted pastor, a patient teacher and a kind friend than a cartoon sidekick. It holds six defined states, and the product responds through them. During learning Shalom is calm; during prayer it becomes compassionate; at milestones gold appears; after an absence the experience welcomes rather than reprimands.

Six states, one character

Greeting

Open posture, wings lowered. The state onboarding opens on.

Focused

A slow head tilt — the posture of listening closely.

Celebrating

One settle, no bounce. 640ms, the longest motion allowed.

Glowing

A full golden aura, reserved for rhythm milestones.

Compassionate

One wing extended, and no motion at all — stillness is the point.

Resting

Half-closed eyes, a slow breath.

Building Shalom’s visual world

The visuals were never treated as decoration layered on afterwards. The mascot and the Bible-figure portraits were both built through the same brief-then-iterate process the product itself was built with, led by Tamai Banje.

Designing Shalom, the mascot

Before a single sketch was drawn, the illustrator worked from a written brief rather than a mood board: a dove, flat modern illustration, Sage archetype, pure white body with sky-blue wings and gold accents — plus an explicit list of what to avoid. No baby-ish proportions, no squeaky cartoon cues, nothing that reads as a children’s character.

The closing line of that brief set the bar deliberately high:

Shalom will be seen by the same person every day, sometimes at their most vulnerable or hopeful — so the character has to be worthy of that trust.

How the character was arrived at

1. Round 1Sent back

   A round, bulb-shaped body read as a cute cartoon chick rather than a wise guide.

2. Round 2Kept

   The body was elongated and straightened for posture and dignity, and the halo-and-olive-branch motif arrived. It became permanent from this point on.

3. Round 3Kept

   A gold scarf tied back to the halo and gave the silhouette something that still reads at app-icon size.

4. Round 4Locked

   Wings became draped panels rather than spread feathers — closer to a robe than a bird — and the character lost its legs, hovering instead.

The character that shipped

Six states, one character

Once the base character was approved, it was extended into the six fixed emotional states, each specified down to a single distinguishing cue: an extended wing for compassionate, a full golden aura for glowing, half-closed eyes for resting. That keeps the states legible at a glance and prevents them from multiplying beyond the six the brand allows. Final assets were delivered as editable SVGs.

A character illustration system

Shalom could not feel like a coherent product if the mascot lived in one visual world and the Bible characters lived in another. As the Character Spotlight became a more important part of the daily experience, we needed a recognisable illustration system for people such as Abraham, Moses, David, Esther, Paul, Solomon, Peter, Ruth, Mary and Jesus.

We used the existing brand personality and mascot states as the art-direction foundation, and set the constraint for every character illustration from there. Rather than historically dense or highly realistic biblical paintings, we aimed for illustrations that were human and recognisable, warm, simple enough to work on a mobile screen, mature rather than childish, lightly detailed rather than noisy, consistent in proportion and line treatment, and supported by gold only as an accent.

Consistency did not mean making every character look the same. Each illustration was built around a small number of visual cues connected to that person’s story, so Moses, David, Esther and Paul still feel like different people at a glance while their silhouettes, facial treatment and colour discipline belong to one system. New characters were compared against the existing library rather than judged in isolation, which is what kept the style from drifting as the set grew.

The illustrations were designed for a product role rather than as standalone artwork. They stay readable at mobile sizes, sit inside the whitespace of the spotlight screen, and support the lesson rather than dominate it — which is why the final assets are isolated figures on transparent backgrounds, with no rectangular image edge competing with the interface.

One visual system, different stories

Character Spotlight

Esther

A young Jewish woman who became queen of Persia at the moment her people needed someone inside the palace.

Courage is often just obedience with the outcome still unknown.

Character Spotlight

The illustrations ultimately serve a purpose beyond polish. One of the original user problems was difficulty remembering biblical people and stories. Giving each important character a consistent visual identity creates another retrieval cue: instead of meeting a name only as text, you begin to associate that person with a face, a story and a lesson. That turns illustration into part of the learning system.

Designing habit without shame

Habit formation was one of the hardest product-design problems. We studied successful habit products and borrowed the mechanics that made sense, while rejecting those that conflicted with Shalom’s purpose. Shalom uses progress, daily rhythm, milestones, reminders, completion feedback, personalised journeys and visible weekly activity. It deliberately avoids coins, leaderboards, competition, countdown anxiety, red failure states and childish rewards.

Renaming the streak to “rhythm”

The single most important product decision made after launch planning was a rename. “Streak” is the standard word for this mechanic, and it carries the standard psychology. Traditional streak mechanics often leverage loss aversion: once a number has been built, avoiding its loss becomes another reason to return. For a spiritual product, we judged that this could create the wrong emotional relationship with discipline.

The fix was not cosmetic. It required splitting one number into two — a resettable current rhythm that is never announced as a loss, and lifetime totals that can only ever grow. The completion screen shows both, separated by a hairline, because one can reset and the other cannot.

A 36-hour grace window was introduced alongside it, so finishing a reading shortly after midnight is not punished because a database date changed.

How we built it

Phase 1: define the transformation

Building Shalom started by defining what success should look like for someone after roughly 90 days. Before: inconsistent, confused, passive, frustrated by their own lack of discipline. After: reading consistently, understanding major biblical stories, recognising important characters, knowing more about God’s character, and increasingly applying Scripture to everyday decisions. That became the filter for every feature decision — a feature had to support the transformation rather than make the app larger.

Phase 2: design the smallest meaningful loop

Instead of starting with social features, AI chat or an enormous study library, we focused on the recurring behaviour Shalom needed to win: can someone open this product every day and meaningfully finish something? The loop was treated as the engine of retention from the beginning.

Phase 3: build for imperfect connectivity

Because the product needed to stay useful across real mobile conditions, Shalom uses a local-first architecture. Your actions write immediately to Zustand and IndexedDB, and sync to Supabase in the background.

Authentication is anonymous-first, so you can start without an account-creation form. Only after you have experienced the product does Shalom ask you to attach an email and preserve your progress — which keeps friction away from the most fragile part of the funnel, the first session.

Phase 4: test what could silently break trust

For a spiritual product, correctness matters differently. A typo on a generic onboarding screen is inconvenient; incorrect Scripture or misleading theological framing can damage trust in the entire product. So testing covers more than UI behaviour, and all 90 original passages were proofed word-for-word against the official WEB text. You can read the full content process on the methodology page.

How Shalom evolved

The most meaningful changes happened after the core experience already worked. We kept reviewing it by asking one question: what happens after someone understands today’s lesson? That exposed three gaps. Understanding did not automatically produce remembrance. Remembrance did not automatically produce prayer. And reflection disappeared if there was nowhere to keep it.

Three additions closed them:

• Carry This With You — a single verse reinforced at the end of the reading, so you leave with something memorable.
• Pray This — an authored prayer grounded in what the day taught, complete enough to pray aloud with no typing.
• My Journey — saved verses, prayers and personal notes, kept in one place instead of disappearing into history.

The loop became richer without abandoning the five-to-eight-minute philosophy.

Discipleship Circles

The next problem was social: how can churches and small groups use Shalom without turning discipleship into surveillance?

Leaders can create circles, invite members, assign lessons, batch-schedule content and celebrate collective milestones. But the privacy model is deliberately restrictive. An administrator cannot inspect an individual’s spiritual activity; individual progress is visible only when that member opts in, and there are no rankings. Circle milestones — a group’s hundredth or five hundredth completed session — celebrate the community without creating winners and losers.

That promise is enforced in database policy rather than in the interface, which is the difference between a product that intends to protect you and one that is built so it cannot do otherwise. What Shalom stores, and why, is set out in the privacy policy.

Discipleship Circles, end to end

Grace Chapel, Tuesday Group

24 members walking together

Join this circle

Your progress stays yours unless you choose to share it.

Invite

Grace Chapel

This week, together

96

sessions completed by 24 members

Circle milestone

This circle has passed 100 sessions together.

Sharing

Share my progress with the leaderOff

Circle home

Today, from your leader

The Father Who Ran

Luke 15:11–24

Begin this lesson

Finishing this keeps your rhythm — and leaves your own path exactly where it was.

Earlier this week

Mon · A Sower Went Out

Assigned lesson

Growth and sharing

Growth was another area where we resisted simply copying another product. We studied the shareability of verse-image experiences and redesigned Shalom’s sharing around the day’s most meaningful takeaway: the insight about God, the Bible reference, a calm 9:16 composition, generous negative space, restrained branding and a parchment treatment.

The card is rendered locally in the browser, so sharing still works offline. It also shares the completed day’s insight rather than accidentally pulling tomorrow’s unread lesson after progress has advanced. Growth becomes a continuation of the learning experience rather than a generic “invite friends” button.

What we shipped

What comes next

Shalom taught us that building an engaging product does not have to mean making it louder. Sometimes the harder challenge is building something people want to return to without exploiting the reasons they are afraid not to.

The result is a product where the technology deliberately gets out of the way.

One day at a time

One reading.

One truth.

One verse.

One prayer.

One action.

One day at a time.

As the product definition evolved, one principle stayed unchanged. Shalom is not a Bible app, a sermon library or a quote generator. It is a daily discipleship system combining habit, learning, memory and application — and the brand standard still captures what we have been trying to build from the beginning: peace begins with understanding. You can read more about the people and intent behind it on the about page.

Frequently asked questions