Journly Case Study

Wellness | 2025 | Product Designer, Developer

Overview

Most journaling apps are designed around consistency. They encourage users to build habits through streaks, reminders, and progress tracking, but those mechanics can feel out of place in a product that's meant to support emotional reflection.

Journly started from a different assumption. Instead of encouraging people to journal every day, it focuses on making the experience feel safe enough to return to whenever it's needed. The product combines private journals, guided reflection, mood tracking, and AI-assisted writing into an experience designed specifically for women.

I designed and built Journly end to end, leading product strategy, UX, visual design, React Native development, backend architecture, and App Store optimization. Owning both design and implementation meant product decisions, technical constraints, and user feedback were part of the same process rather than separate stages of development.

Problem

I identified a disconnect between current journaling tools and user psychology. While the wellness market is worth $4.5B, most products use sterile, neutral designs that fail to build an emotional connection with their primary demographic.

Market Insights:

• The "Guilt Gap": Competitive audits showed users felt "punished" by apps when they missed a day, leading to app abandonment.

• The Aesthetic Shift: Pinterest data showed a 280% increase in "Dopamine Decor," a move toward saturated, joyful colors that stimulate calmness and joy.

• The Bet: Women will choose a space that feels like a "safe harbor" over a tool that feels like a "task manager."

Constraints

One of the earliest questions I asked was whether the engagement patterns common in wellness apps actually matched the way people journal.

Many products in the category rely on streaks, reminders, and notifications to encourage consistency. Missing a day becomes something the product asks you to recover from. For a habit tracker that approach makes sense. For a journaling app, especially one intended for emotional reflection, it can introduce unnecessary pressure during the moments people are least likely to need it.

That led to a different set of product decisions. Streaks and reminders became optional rather than expected, allowing users to return on their own terms. The experience doesn't change if someone is away for a week, and there are no penalties for stopping and starting again.

The visual language followed the same thinking. Much of the category leans toward muted colours and neutral interfaces. Journly deliberately takes a different direction with softer colours, richer illustration, and a more expressive aesthetic. The intention wasn't simply to make the app look different. It was to create an environment that immediately felt personal to the audience it was designed for.

Role and collaboration

[object Object]

System view

The first version of the product organised entries into folders.

From a technical perspective the model worked well, but the language users used to describe it didn't. During testing and after launch, people repeatedly asked if they could create more journals. They rarely mentioned folders.

That difference turned out to matter. People weren't thinking about organisation in the way the product was presenting it. They were thinking about keeping separate notebooks for different parts of their lives.

I redesigned the experience around that mental model. Folders became journals, the navigation was simplified, and page-turning became the default reading experience, with scrolling available as an option. The change affected more than the interface. It also changed the way information was organised throughout the product because the underlying structure now reflected how people naturally described and used it.

Key decisions

As the product matured, AI became part of the experience in a few carefully chosen places.

Rather than introducing a conversational assistant throughout the app, I focused on areas where it could reduce friction without changing the nature of journaling.

Mood tracking became more conversational by allowing users to move from a broad emotion into more specific feelings before beginning an entry. Those responses were then used to generate a starting point for writing, helping users move past the blank page without replacing their own voice.

Voice capture followed a similar approach. Native speech recognition often required significant editing, so I introduced Whisper-based transcription to improve reliability while keeping audio recording available whenever transcription wasn't appropriate.

AI also helped connect entries over time. Instead of treating each journal entry as an isolated moment, the product could reference previous reflections and generate weekly summaries that highlighted recurring themes and emotional patterns.

Each of those decisions had the same objective: reducing the effort required to begin writing while keeping the act of reflection firmly in the user's hands.

Impact

Journly has reached users in more than 40 countries through organic App Store discovery, without paid acquisition. Iterating on onboarding increased completion to 54.2%, while continued improvements to the product and App Store presence contributed to a 155% increase in first-time downloads. More importantly, the project changed the way I think about designing products for emotional experiences. The strongest ideas in Journly came from paying attention to how people naturally behaved rather than asking them to adapt to the product. Replacing folders with journals, supporting multiple entries throughout the day, making reminders optional, and introducing AI only where it reduced friction all came from the same process: observing behaviour, questioning assumptions, and adjusting the product accordingly. Those are the principles I continue to carry into every product I work on.
40+ Countries reached in the first week through organic App Store discovery, with no paid acquisition or launch campaign
54.2% Onboarding completion after post-launch drop-off analysis and targeted iteration on friction points
74% Increase in downloads within two months from App Store optimization improvements after launch
155 % Growth in first-time downloads after launch through organic App Store discovery, with no paid campaign
62.5 % Growth in returning users updating the app as the user base matured
100 + New users each month through organic App Store discovery, with no paid acquisition, built on onboarding and ASO iteration

Reflection

Working on Journly as both the designer and engineer changed the way I approached product decisions.

Questions around offline support, synchronisation, AI, onboarding, and animation all affected both the user experience and the architecture. Thinking about those constraints early made it easier to simplify ideas before investing time in building them.

It also made iteration much faster. Feedback from users could move directly into the product without long design or development cycles. Some ideas became central to the experience as people adopted them. Others were removed once it became clear they introduced complexity without providing enough value.

Working this way reinforced something that has influenced my approach to product design ever since. Product quality isn't only shaped by the ideas that are added. It's also shaped by the decisions to simplify, postpone, or remove work when it no longer improves the experience.