Matthew Johnson

Zory: Turning Bestselling Romance Novels into Interactive Experiences

I designed and scaled an interactive fiction platform from concept to 14,000+ downloads. Partnering with Matt Hall—creator of Apple Design Award-winning Crossy Road—and Clara Reeves, CEO of Hipster Whale, I established design systems, user research processes, and product strategy that achieved 32-minute average sessions and $13.28 Android ARPPU in a highly competitive market.

Role

Co-founder · Founding Designer

Team

Partnered with Matt Hall (creator, Crossy Road) and Clara Reeves (CEO, Hipster Whale)

Impact

14k+ downloads · 32min avg session · ⭐ 4.8 rating

Scope

Consumer app, author tools, content platform

Duration

2020 – 2025 (5 years)

Tech Stack & Design Tools

Flutter
Firebase
Figma
Google Workspace
Google Apps Script
Rive

Why This Project

Bridging Two Worlds: Traditional Publishing Meets Interactive Media

Traditional ebook platforms offered quality literature but no interactivity, while interactive fiction apps relied on user-generated content that rarely met publishing standards. We saw an opportunity: readers wanted agency in their stories without sacrificing quality.

Our initial research revealed compelling user needs. When we surveyed romance reading communities, 91% expressed interest in interactive versions of professional, novel-length books. This overwhelming response signaled an underserved market where digital natives craved more agency in their reading experiences—a fundamental shift in how modern audiences expect to engage with stories.

Mapping the Opportunity Space

Venn diagram showing gap between traditional reading apps and interactive fiction platforms

A clear market gap between passive reading and visual-heavy gaming experiences

Key Design Challenges

1. Creating Seamless Interactivity

How could we add choices without breaking reading flow? Modal dialogs and game UI would disrupt immersion. We needed interactions as natural as turning a page.

2. Empowering Non-Technical Authors

Bestselling authors wanted to write—not learn to code. Existing tools like Twine either require programming knowledge or the use of rigid templates. We needed a writing system that was familiar and easy for authors while still enabling complex branching narratives.

3. Balancing Monetization with User Expectations

Mobile readers expected free content while professional authors expected premium pricing. We stayed agnostic about the ideal model but started with in-app currency—keys and diamonds—a system familiar from existing interactive apps. This let us monetize premium choices naturally while planning to test other approaches as we grew.

Understanding Our Users

We identified two distinct user groups whose needs had to be simultaneously addressed:

Readers

Digital natives who grew up with both books and games. They expected agency in their entertainment but were frustrated by the juvenile content in existing interactive apps.

Authors

Professional writers facing declining income, many sitting on cut scenes and alternate chapters with no good way to monetize them.

To bring the project to market, we'd need to design an ecosystem to serve both authors and readers. Every interface decision would ripple through content creation, user experience, and business sustainability.

Core Design Question

Could we create an interactive reading experience sophisticated enough for adult audiences while keeping the authoring process simple enough for non-technical writers?

Research & Discovery

We initially considered building a general interactive fiction app, but market research revealed a more focused opportunity. Romance readers spent more time and money on content than other genres, with 82% female audience and 53% aged 18-34. When we surveyed 388 users across romance and interactive fiction communities, we discovered compelling crossover demand: 67% of romance readers wanted interactive stories, while 79% of interactive fiction users wanted text-based interactive stories.

Romance Readers
Female audience82%
Ages 18-3453%
Discover genre ages 11-1870%

Industry data from RWA

Interactive Fiction Users
Female audience78%
Ages 10-2180%
Want mature content67%*

*Reddit polling data

Romance Reader Community

Survey: Interest in interactive romance narratives

67% Interested
33% Not interested

n=140 respondents

Interactive Fiction Community

Survey: Interest in text-based interactive narratives vs. visual interfaces

79% Wanted text-based
21% Preferred visual UI

n=248 respondents

Competitive Landscape

Mapping existing platforms revealed clear gaps in the market:

Platform TypeStrengthsGaps
Traditional Apps
(Radish, Galatea)
Professional content, established authorsNo interactivity, passive consumption only
Interactive Games
(Episode, Choices)
Engaging mechanics, strong monetizationAvatar-based UI, speech bubbles break immersion, shallow narrative depth
Our OpportunityFull-length narratives, professional authorsText-based choices preserve reading immersion

Key Research Insights

  • Quality Over Quantity: Users wanted "real books by real authors"—not user-generated content
  • Text-First Experience: Readers preferred full narratives over speech bubbles and avatars
  • Meaningful Choices: Decisions should impact relationships and outcomes, not just cosmetics
  • Author Economics: Declining income meant authors needed new monetization for cut content

Validating the Concept

To validate that interactive text could feel as engaging as games, I built a working prototype in Webflow using animations logic. The demo proved choices could feel satisfying rather than mechanical, attracting both bestselling authors and my eventual co-founder Matt Hall.

Zory demo - Interactive story reading interface
Zory demo - Webflow navigator showing complex branching structure

Early Proof of Concept (2020) · Built with Webflow's animations logic · View demo ↗

My Role

Founding Designer

I partnered with Matt Hall (creator of Crossy Road) to build Zory from the ground up, designing the complete mobile experience from the five-tab navigation architecture to the choice animation mechanics. I created screens, interactions, and user flows while Matt built the Flutter app.

Despite working across time zones (Australia/US), we maintained a tight feedback loop—I'd deliver high-fidelity designs in Figma, he'd implement them in Flutter, and we'd iterate based on technical constraints, Matt's own suggestions, and user feedback. My designs evolved based on Matt's needs and technical considerations, and vice versa.

Building Zory required thinking beyond traditional design boundaries. As a small team, I wore multiple hats—balancing product design with content operations, business strategy with creative direction, and user testing with community building. This systems thinking approach meant every design decision had to consider technical architecture, content scalability, and business viability simultaneously.

Product Design circleContent Ops circleTech Architecture circleBusiness Strategy circleTesting & Community circleCreative Direction circleZory Systems Thinking

Matt and I worked together to create an authoring system that let bestselling authors write interactive stories directly in Google Docs. I'd design the interface, he'd build, and we'd iterate based on what we learned.

I gained incredibly valuable skills while working with Matt, like designing for edge cases and accessibility at scale. Matt's experience scaling Crossy Road to 300M+ users informed our technical decisions from day one. Every design choice—from our monetization system to our content architecture—was stress-tested against his knowledge of what breaks at scale. This partnership taught me to design with implementation in mind, always considering performance, data structures, and platform constraints.

The Founding Team

Zory founding team including creators of Crossy Road

Industry veterans with experience shipping to hundreds of millions of users

Learning from Industry Veterans

Our team combined mobile gaming expertise with traditional publishing knowledge. I worked directly with RITA-nominated authors to understand their creative process, then translated those needs into product features. Clara Reeves (CEO of Hipster Whale) advised on platform strategy, while our editorial director brought 35 years of publishing experience to content decisions.

This range of perspectives shaped how I communicated design decisions—technical specs for Matt, creative possibilities for authors, and business implications for advisors. The result was a product that served both our author and reader communities effectively.

Key Design Decisions

1. Choice Architecture: Designing Seamless Interactive Moments

Interactive fiction typically treats choices as interruptions—modal dialogs that break narrative flow. At Zory, we explored whether choices could feel like natural extensions of the reading experience itself.

We decided choices would always appear at the bottom of the reader page, creating predictable placement. When content demanded more room, choices would flow to the next page but maintain that bottom position.

We worked with writers to ensure decision points had emotional context through narrative priming—inner monologues revealing conflicting desires, dialogue building tension without telegraphing options. When choices appeared, readers had context for their decision rather than facing arbitrary options.

Choices appeared via staggered animations triggered by scroll/swipe position rather than waiting statically on the page. The pop-in animation added a moment of delight that signaled an interactive moment without disrupting reading flow.

Premium Choice In Action

The button appeared raised and sank into the page when pressed. Haptic feedback reinforced the interaction. Upon selection, the chosen text animated from the button into its position as the next line of narrative, while unchosen options faded away.

From Concept to Production

Early Vision (Keynote, 2020)

Original concept animated in Keynote before having access to prototyping tools

Refined Prototype (Rive)

Prototyped in Rive to explore timing and personality

Shipped Experience (Flutter)

Final implementation with refined animations

Before I had access to prototyping tools or a technical co-founder, I used Keynote to animate my vision for how choices could feel delightful and integrated. This early concept—complete with pulsing 'tap to continue' and currency indicators—became the foundation for everything we built.

The integrated choice text was styled slightly lighter than surrounding narrative and was centered—a subtle acknowledgment of reader agency without disrupting flow. A staggered reveal animation unveiled the continuation, creating a sense of the story responding to reader input.

Premium choices used the same interaction system with added sparkle animations created in Rive. This maintained consistency while adding visual value to paid options.

Premium Choice Animation

Qualitative feedback consistently highlighted the seamless integration of choices. Beta testers described feeling "inside" the narrative and reported that choices felt like "part of the story" rather than interruptions.

Key Takeaway

Good design dissolves into the experience. Our choices animated directly into the narrative text because that's what they were—the next line of the story. The interface became the story itself.

2. Editor's Notes: Scaffolding Reader Understanding

After soft-launching, we discovered readers faced a cognitive gap between making choices and experiencing their consequences. A choice in chapter 8 might fundamentally alter the story, but its impact wouldn't become apparent until chapter 15. This disconnect caused confusion and contributed to reader drop-off.

Our solution was Editor's Notes—contextual messages that appeared before and after key choices. These served multiple purposes: onboarding new readers into how interactivity worked, celebrating monetized choices with positive reinforcement, and most importantly, letting readers know their choices would have significant consequences down the line.

Editor's Note 1 - Interactive story choice interface
Editor's Note 2 - Sci-fi TV show preferences
Editor's Note 3 - Relationship choices with Paige
Editor's Note 4 - Story consequences

We implemented this feature delicately. We needed to provide just enough information to maintain reader confidence without spoiling future plot points. Notes like "This choice will significantly impact your relationship with this character" gave readers the assurance that their decisions mattered, even when the immediate narrative seemed to continue unchanged.

Beta testers in our Discord reported that Editor's Notes improved their understanding of the interactive format and increased confidence in their choices. Several readers noted that knowing their choices would have later consequences maintained engagement through transitional chapters.

Key Takeaway

Never leave users wondering if their action matters. When users take action, acknowledge it immediately, even if the results come later.

3. Zory Writer: Creating a Design Language for Interactive Authoring

Enabling non-technical authors to create interactive narratives required bridging two different mental models. Existing tools were built by programmers using terms like nodes, branches, and conditional logic. Romance authors thought in scenes, metaphors, and emotional beats.

Early Concept: Color-Coding for Branching Narratives
Early concept diagram showing color-coded options and vines for interactive storytelling

My initial concept for making branching narratives visual and intuitive in traditional word processors

Initial explorations focused on how authors naturally think about story variations. Before collaborating with co-founder Matt Hall, I developed concepts using simple highlights and parenthetical tags that could work in any word processor. This became the foundation for our authoring system.

The key insight was reframing the vocabulary. Traditional interactive fiction used "branches"—implying permanent divergence. We introduced Vines: story paths that could weave apart and come back together. This metaphor shift changed how authors approached their stories. Rather than exponentially complex branch diagrams, they were weaving controlled variations.

The complete framework included 13 simple concepts, four key ones being:

Key Concepts from the Zory Design Language

Vines

Story paths that weave apart and come back together. Unlike traditional branches that diverge forever, vines allow for controlled variation that returns to the main narrative.

Leaves

Content that appears later as a result of earlier choices. Like leaves sprouting from a vine, these passages reveal the consequences of reader decisions chapters later.

Skipping Stones

Single choices that create ripple effects throughout the entire story. One decision can spawn multiple leaves across chapters, books, or even series.

Choice Framing

Options that shape reader perspective without immediate content changes. These choices influence how readers interpret subsequent events, adding psychological depth.

These four concepts represent a sample of the comprehensive design language I developed, which included 13 distinct terms that helped authors think about interactive storytelling in new ways.

Each term was carefully chosen to resonate with writers' existing mental models. While Matt Hall brilliantly engineered the ZRY markup engine that powered everything, I focused on making it feel natural in Google Docs—the tool authors already used daily.

From Author's Manuscript to Reader's Experience
Comparison showing how simple markup in manuscripts creates rich interactive experiences for readers

The system's elegance: authors write naturally with minimal markup, while readers experience rich, branching narratives—all within immersive text, not speech bubbles

Author in Docs

Author in Docs

Authors write naturally in Google Docs using familiar tools. Color-coded tables and simple formatting conventions replace complex syntax. The add-on provides one-click buttons to insert choice blocks, validate structure, and preview chapters instantly—no code knowledge required.

Convert with ZRY

Convert with ZRY

The system automatically validates every choice ID and target, builds the complete branch graph, and packages everything into a .zry file. Authors receive clear error messages if something needs attention. What previously required technical expertise now happens with a single export command.

Run in the App

Run in the App

Stories come alive instantly in the Zory app with full interactivity, monetized choices, and professional presentation. All without touching a single line of code.

The Google Docs add-on interface maintained simplicity. Despite our system being simpler than traditional tools, any friction could interrupt creative flow. The add-on provided one-click insertion of pre-formatted choice blocks with placeholder text, allowing authors to focus on storytelling rather than syntax.

Zory Writer Google Docs Add-on Interface
Zory Writer Google Docs add-on showing formatted choice table and side panel tools

The add-on provided one-click insertion of formatted choice tables and intuitive controls for authors

Authors who had never created interactive content were publishing stories within hours.

By the time we sunset, dozens of professional authors and in-house writers had successfully used the system. The comprehensive documentation became the foundation for author onboarding, and the conceptual framework influenced how the entire team discussed interactive storytelling.

Key Takeaway

The best tools speak the user's language, not the technology's. By meeting authors where they already worked—Google Docs—and using easily-digestible metaphors, we removed the biggest barrier to adoption.

Results & Impact

While Zory ultimately sunset due to content velocity challenges, we validated our core assumptions during our 18-month run. The metrics below represent lifetime performance across 14,000+ downloads.

32m 48s

Average session time

This exceeded Wattpad's 28-minute average by 14%. But users were consuming content faster than we could produce it.

3.6

Sessions per Week

Gaming-like retention with reading depth

4.16%

iOS Conversion Rate

30% above category average of 3.2%

37%

WAU/MAU Retention

Meeting the 30-50% successful app benchmark

61%

Direct Traffic

Strong word-of-mouth growth

$13.28

Android ARPPU

With optimization potential

We achieved something unique in interactive fiction: gaming retention (3.6 sessions/week) with reading depth (32-minute sessions).

User Behavior Patterns

The 61% direct traffic rate indicated strong word-of-mouth growth. Our 4.16% App Store conversion rate exceeded the iOS entertainment category average by 30%.

This combination—frequent returns with deep engagement—validated our approach to interactive fiction.

User Feedback

Rachel, Apr 2024

"Easy to navigate and binge. Love the app interface. Not distracting. Different from competitors because there is depth and major twists without text boxes."

Reb. G, Apr 2024

"so bubbly and fun to use. You can really tell they put a lot of passion and care into making it. (I really love reading on the dark mode at night.)"

7.62@@, Apr 2024

"great features to make it easy to read on your device (multiple background colors) and the ability to choose scroll reading or page flipping. You can tell the app is put together with care and creates a fun way to take in a new story."

Platform Impact

Dozens of professional authors created interactive stories using our system. The Google Docs workflow enabled writers with no technical background to publish branching narratives within days.

Premium choices converted at 2.6%, with potential for optimization. The $13.28 Android ARPPU demonstrated monetization worked across platforms.

We created interactive fiction that engaged like games while respecting narrative depth. But content production became our critical bottleneck—users consumed stories faster than our curated approach could supply them.

Key Takeaway

The metrics validated our design—everything worked as intended. But great UX couldn't overcome content velocity. We'd built a platform that readers loved, but couldn't fill it fast enough to sustain a business.

Reflection

Zory set out to make interactive storytelling accessible to professional authors. As a bootstrapped team with one primary engineer, we built a platform that let bestselling authors create branching narratives without code. While content velocity challenges led to our sunset, we learned valuable lessons about product design, platform dynamics, and the realities of bootstrapping.

What the Data Revealed

Users spent an average of 32 minutes and 48 seconds per session—higher than typical reading apps like Wattpad (28 minutes) and approaching video streaming engagement. The 61% direct traffic and 3.6 sessions per user indicated strong product-market fit among our user base. Android users spent $13.28 on average versus $7.01 for iOS users, inverting typical platform monetization patterns.

These metrics validated our core assumptions about reader appetite for quality interactive fiction. However, with only a small pool of paying users across all platforms and no ad revenue implementation, our free-to-play model wasn’t sustainable, despite strong engagement.

Systems That Worked

The Zory Writer system successfully onboarded professional authors who'd never created interactive content. By building within Google Docs and creating an intuitive conceptual framework (Vines, Leaves, Skipping Stones), we made is accessible. Authors were publishing complex narratives within hours of starting.

Our choice architecture—seamlessly integrated into the reading flow rather than modal interruptions—maintained narrative immersion. The five-tab navigation respected reader mental models, avoiding game-like conventions that might alienate our target audience. Our key-based monetization with free chapters effectively hooked readers before asking for payment.

The Content Velocity Problem

With 12,000+ users and only 18 authors, we faced a fundamental supply-demand mismatch. Our free-to-play model, with keys regenerating every 8 hours (if below quantity thresholds), encouraged binge reading that our premium author base couldn't satisfy. Unlike platforms with user-generated content or AI-assisted creation, our focus on professional quality stories limited production speed.

This constraint became clear as session times declined from 32 minutes to 15 minutes—users had simply exhausted our content library. With limited resources, we faced a dilemma: building content management tools and creator incentive systems would accelerate production, but shifting to a user-generated content model would betray our core promise. We had positioned ourselves as a publisher of premium fiction, not another platform for amateur writers. The very quality standard that attracted our users also limited our ability to scale.

Closing Thoughts

Building Zory taught me that great design requires sustainable systems. We built tools that worked beautifully—authors created stories easily, readers stayed engaged for 32-minute sessions. But we couldn't produce content fast enough to feed the platform.

The mismatch was fundamental: free-to-play economics need massive content libraries, but quality fiction takes time to write. We'd optimized for the wrong constraint.

Design decisions must account for operational reality. The best user experience is one you can actually sustain. Sometimes that means building less, but building what you can deliver consistently.

Additional Screens

From brand identity to shipped features across consumer and creator experiences

Zory Design System

Zory Design System

Complete design system overview showing all app screens and states

Brand Identity

Brand Identity

Comprehensive visual identity including logo, colors, and typography

Onboarding Flow

Onboarding Flow

Age verification and user onboarding experience

Primary User Flow

Primary User Flow

First-time reader experience: from book details through initial setup to first choice

5-Tab Navigation

5-Tab Navigation

Core app screens: Home, Shelf, New, Store, and Account

Reader Experience

Reader Experience

Customizable reading interface with theme and font options

Zory Writer Tool

Zory Writer Tool

Creator platform for building interactive branching narratives

Key Interactions & States

Key Interactions & States

Empty states, modals, and system feedback patterns