Personal Project · UX Design + Research

ChayToon

Research-first mobile app design for webcomic readers and creators — built on 10 user interviews, zero assumptions, and a full IA before a single screen was designed.

scroll

Summary

The Problem

Webcomic readers couldn't discover new content through in-app tools — they relied on Reddit and social media. Creators posted into a void with no meaningful analytics on who was actually reading their work.

The Solution

Designed a dual-mode app serving both readers and creators — contextual discovery for readers who want to find the right comic without scrolling, and transparent analytics for creators who need to know their audience is real.

Role

  • Lead UX Designer
  • UX Researcher

Timeline

2023
  • 10 user interviews
  • Research to wireframes
  • Full IA + prototype

Tools

  • Figma & FigJam
  • Notion

Contributions

UX Researcher

  • 10 semi-structured interviews across readers and creators
  • Built affinity maps and synthesized dual-user insights
  • Competitive analysis of Shonen Jump, Webtoon, WebComics
  • Translated findings into actionable design decisions

UX Designer

  • Designed IA for two distinct user types on one platform
  • Mode-switching model for reader/creator experiences
  • Full wireframe-to-prototype pipeline
  • Dual personas guiding every design decision

Challenge

ChayToon had to serve two fundamentally different user types — readers and creators — on the same platform. Their needs don't just differ; they sometimes conflict. Designing one experience without undermining the other required starting from zero assumptions and letting research define every boundary.

Key Insights

I ran 10 semi-structured interviews with both webcomic readers and independent creators — two very different user types with conflicting but equally valid needs on the same platform.

Affinity Map — Reader & Creator Themes Interview Script

Reader insight: Discovery is broken. Readers find new comics through Reddit and word-of-mouth — not through the apps they read on.

Creator insight: Analytics are opaque. Creators post into a void with no meaningful data on reader engagement or chapter completion.

Interview Script 2
Discovery broken Analytics opaque Two-sided platform Off-platform discovery Engagement invisible

Design Strategy

Competitive Analysis

Deep analysis of Shonen Jump, Webtoon, and WebComics across reading experience, discovery, creator tools, monetization, and community features — mapping gaps and opportunities.

Competitive Analysis Competitive Analysis 2

Personas

Two distinct personas representing the dual nature of the platform — a reader who wants frictionless discovery and a creator who needs visibility and transparent analytics.

Reader Persona

Nour, 23

Casual Reader · Binge-reads on Commute

"I want to find something new without scrolling for 20 minutes. Just show me what I'll actually like."

Creator Persona

Yusuf, 27

Indie Creator · Self-Publishing Online

"I need to know if anyone's actually reading — right now I post and it disappears into the void."

Information Architecture

Building an IA that serves both readers and creators — shared infrastructure, distinct experiences. A mode-switching model lets each user type access what they need without cluttering each other's paths.

Full App Sitemap — Reader & Creator Modes

Solution

Wireframes

Lo-fi and mid-fi wireframes for both reader and creator flows — testing layout concepts and interaction patterns before committing to high-fidelity design.

Reading View Wireframe Creator Dashboard Wireframe Creator Dashboard Wireframe 2
Reading View Wireframe 2 Creator Dashboard 3 Creator Dashboard 4

Impact

10

User interviews completed

2

User types, one platform

3

Platforms analysed

Reflection

ChayToon taught me that the hardest design problems aren't about making one thing better — they're about serving two different people without letting either experience collapse under the weight of the other. The mode-switching model only emerged because the interviews made it undeniable that a single unified flow would fail both users.

← A+Link

Case Study 03 / 03

Back to Work →