💡
What happened after launch? This article covers how Waymark evolved after launch: product analytics, interface improvements, journaling upgrades, Bible Search, localization, App Store positioning, and growth lessons.
A few years ago, I started going back to church on my own. Outside of Sunday services, I struggled to read the Bible consistently. The language felt dense, the context was hard to access, and I often could not see how Scripture connected to the life I was actually living.
I tried other faith apps. Daily verses. Short devotionals. Reading plans. Some helped briefly, but most felt disconnected from real life, locked meaningful guidance behind paywalls, or assumed I already knew what I was looking for.
The friction was not that Scripture was unavailable. It was that understanding it felt intimidating, fragmented, and difficult to apply.
Waymark started from that gap: people do not always need more faith content. They need a calmer way to understand, apply, and reflect on Scripture in real life.
💡
Related build note I wrote more about the personal friction that started Waymark, from struggling to apply Scripture in daily life to shaping the first product direction.
Role
Founder, Product Designer, Developer
Timeline
Industry
Lifestyle
Platform
iOS (Android coming soon)
Faith-based apps have spent years optimizing for content volume: more verses, more devotionals, more plans, more streaks. The assumption is that more access leads to better engagement.
But the deeper problem is not access. Most people who want to engage with Scripture are not short on content. They are short on understanding.
They struggle with:
interpreting passages without cultural or historical context
applying Scripture to real situations
knowing where to start
feeling emotionally hesitant around faith
staying consistent without feeling pressured
accessing meaningful guidance without hitting a paywall
The core issue is not content availability. It is accessibility of meaning.
That became the foundation of Waymark. The product question shifted from:
How do we deliver more Scripture?
to:
How do we make spiritual guidance feel clear, approachable, and sustainable for daily life?
Instead of building another content platform, I reframed Waymark around guidance.
Decision: Build a guidance-first experience instead of a large content library.
Why: Users were not struggling because they lacked content. They were struggling because they felt overwhelmed, unsure where to begin, and disconnected from how Scripture applied to their actual lives.
Product effect: Waymark became intentionally focused: one passage, one real-life situation, one moment of reflection.
This meant saying no to features faith apps often rely on: large libraries, social feeds, competitive streaks, and gamified progress. Those patterns may increase activity, but they can also create pressure around something that should feel personal, reflective, and safe.
Every core product decision was tested against the same question:
Does this reduce friction, or add it?
Design Philosophy
The design of Waymark begins with a simple emotional question:
What does it feel like to open a Bible and not know where to start?
That feeling shaped the product’s pacing, structure, language, and interface. Waymark is designed to receive users in a state of curiosity, hesitation, or longing, without making the experience feel like a test.
The visual language is calm, warm, and unhurried. There are no aggressive progress mechanics, and no gatekeeping language. The UI gives the content room to breathe because the experience itself needs room to breathe.
The product model is linear and deliberate:
Scripture → explanation → context → real-life application → reflection → prayer
This sequence matters. Waymark increases comprehension before asking for interaction. Users are not pushed to reflect before they understand what they read. Each step builds enough clarity for the next one to feel natural.
Key Product Decisions
Some of the most important decisions in Waymark were about what not to build.
These constraints shaped the information architecture, lesson structure, interaction model, and visual system.
Content Quality System
One of the most important parts of Waymark is also one of the least visible: the content quality system.
Generating content about Scripture carries real responsibility. An inaccurate interpretation, tone-deaf application, or theologically skewed framing could do more harm than no content at all.
Before lessons are published, they are evaluated across six dimensions:
Scripture accuracy
Historical and cultural context
Theological alignment
Tone quality
Application relevance
Emotional and spiritual impact
This became a product quality gate. Waymark ships slower because every lesson has to meet a trust standard before reaching users.
That tradeoff is intentional. For this product, trust is not a nice-to-have. It is the product.
Building The Product End To End
Waymark was built entirely by one person, end to end: product direction, UX and UI design, copywriting, app development, backend setup, analytics instrumentation, and launch preparation.
Experience & Content Design
Structured a linear guidance flow from Scripture to reflection, reducing cognitive load and creating a clear daily rhythm.
Designed calm, predictable interactions with subtle motion, morph transitions, and Lottie feedback to guide attention without overwhelming the experience.
Built a minimal, consistent UI optimized for long-form reading, emotional comfort, and daily use.
Defined a modular lesson format: explanation, context, application, reflection, and prayer, turning Scripture into guided, practical insight.
Product & Implementation
Built the mobile app with a fast iteration cycle and a foundation that can support iOS and Android.
Handled authentication, database, and backend logic without heavy infrastructure overhead.
Added native iOS widgets for daily lessons, reflections, and verses, extending the experience beyond the app.
Added event tracking to understand lesson completion, reflection behavior, and product usage patterns.
Added push notifications with controlled delivery logic for gentle, non-intrusive re-engagement.
The website was designed and built separately in Next.js and deployed on Vercel. I treated it as the first step of the product journey, not a marketing afterthought.
Waymark launched quietly: no paid acquisition, no marketing campaign, and no major launch push beyond submitting the app to the App Store.
In the first release cycle, covering V1 and an early bug-fix update, Waymark recorded:
138 first-time downloads
1,080 App Store impressions
20% App Store product page conversion
7 redownloads from users who had previously deleted the app
The 20% App Store conversion rate was the clearest early signal. The product did not win because of distribution. There was no distribution. It won because the positioning was strong enough for the right people to recognize themselves in it.
The redownloads also mattered. For a V1 with known rough edges, they suggested that the core experience was worth returning to, even before the product was fully polished.
💡
Related build note After launch, I started looking more closely at how early signals, positioning, and product data could guide the next version of Waymark.
The V1 data pointed to two problems worth solving before expanding the product further.
First, the App Store product page was not doing the product justice. The original screenshots described the product from the outside in: “Understand the Bible daily,” “Lessons based on your needs,” and “Faith, made practical.” They explained capability, but they did not fully speak to the emotional state that brings someone to Waymark.
So I rebuilt the App Store positioning around real-life moments. Instead of leading with features, the new page opens mid-situation:
When you feel anxious about the future.
Each frame now speaks to a moment the user might actually be living through: needing clarity, wanting a private space to respond, saving what resonates, or watching their walk take shape.
The second issue was product learning. V1 had limited visibility into what users were doing after download. Push notifications did not exist yet, and without event tracking, I could not clearly see where users completed lessons, dropped off, reflected, or returned.
V2 addressed those gaps by adding:
redesigned home and today screens
rebuilt lesson experience
new journal
saved highlights
book-level progress tracking
home screen widgets
dark mode
offline support
PostHog event tracking
OneSignal push notifications
updated App Store positioning
The goal of V2 was not just to add features. It was to strengthen the core product loop: help users return, reflect more easily, and give the product better signals for future decisions.
Current Challenges
Building Waymark as a solo founder means every hard problem lands on the same desk. Two challenges matter most right now.
Getting the lessons right
What This Changed About My Thinking
Building Waymark changed how I think about restraint as a product value.
In many products, the instinct is to add: more features, more content, more paths, more engagement loops. Waymark pushed against that instinct.
The single daily lesson, the removal of streak mechanics, the private journal, and the absence of a social layer all felt like risks. In practice, they are what make the product feel safe.
I also learned how powerful lived experience can be when it is translated into product clarity. Because I had been the user, the priorities stayed sharper. The challenge was not inventing a problem. It was designing with enough restraint to serve it well.
Waymark is proof that not every product needs to optimize for intensity or frequency. A guidance-first product can build trust by reducing friction, both cognitive and emotional.
Future Direction
Waymark’s foundation is intentionally modular. The lesson structure, reflection system, and interaction model can grow into new experiences without changing the product’s core purpose.
Every next step is shaped by the same question that started the product:
How can this help someone understand Scripture and bring it into the life they are already living?