TellWing - A Case Study

Overview

TellWing turns a child's name into a personalized activity book. A parent, grandparent, or teacher enters a name, an age, and a few themes; the platform generates a complete book a story where that child is the hero, plus mazes, coloring pages, word searches, tracing sheets, and a dozen other activity types - that can be played online on any device and downloaded as a print-at-home PDF.

Underneath a deliberately simple surface, TellWing brings together several things that are each a project on their own: a content-generation engine, a document editor, an interactive play experience kids actually use, a print pipeline, and a small marketplace of reusable templates. The interesting work was making all of it cohere into one thing that feels effortless to a parent.

This write-up covers the problem the product solves, the scope decisions that shaped it, and the solution - its features, its design, and the engineering ideas that hold it together.

The problem

Generic kids' activity books are everywhere and forgettable. A child flips through a few pages and moves on, because nothing in the book is about them. Meanwhile, the adults who buy these books - parents choosing a rainy-day activity, grandparents shopping for a birthday, teachers preparing for a class - are looking for something that feels personal and worth keeping, and settling for something that isn't.

The core insight behind TellWing is a single emotional beat: a child seeing their own name on a book made for them. That moment - "a whole book starring you" - is the entire value proposition. Everything the product does exists to make that moment reliable, affordable, and instant to deliver.

Two structural truths follow from taking that beat seriously:

The buyer is not the user. The person paying is an adult in a gifting or teaching moment; the person delighted is a child. That splits the product into two experiences that share the same underlying book but almost nothing in their interface - a calm, trustworthy creation flow for adults, and a playful, frictionless play mode for kids.

The product is a keepsake, not a worksheet. A personalized book is something a family keeps, which changes everything from how it's positioned to how much care each page deserves.

Scope

Scope discipline shaped the build as much as the feature list. Deciding what not to do was as important as deciding what to build.

A digital product, delivered instantly. Customers play online and download a print-at-home PDF. This kept the product simple, made delivery immediate, and let the whole thing ship quickly rather than get bogged down in logistics.

A purpose-built editor, not a general design tool. The editor is powerful, but it is built specifically for personalized books - a fixed page model and a curated catalog of activities. Those constraints are exactly what keep it approachable for a busy parent instead of overwhelming.

A focus on reliability over breadth. The product is judged on three things, in order: the create-and-download experience never breaks; the exported PDF is correct every time (it is the customer's one tangible artifact); and the play experience produces a moment worth sharing. Getting those three right mattered more than adding features.

The solution: features

The feature set spans creation, customization, play, and output.

Book creation

A short wizard collects the child's name, age range, language, and difficulty, then assembles a book from the activity catalog. Books are structured as an ordered sequence of pages, each carrying one activity plus optional decorations.

The activity catalog

TellWing includes roughly fifteen activity types, each generated to suit the child's age:

A key property is that activities generate deterministically - the same book regenerates identically, so a parent's edits (a custom word list, a difficulty change) stay stable instead of reshuffling into something unrecognizable each time.

Customization

The editor lets a parent shape every page: reorder and swap activities, edit titles and instructions, drag free-floating text boxes, upload and resize images and SVGs, place decorative stickers, choose a page border and color theme, and add custom coloring pages. Changes autosave as you work, and the whole book can be previewed live before any commitment.

Play mode

Kids play the book online. Interactive activities have dedicated players: word searches you tap, mazes you trace, and a Color & Draw experience with a draggable, animated color picker (preset swatches and custom colors), brush sizes, an eraser, undo/redo, a fullscreen option, and free-draw painting over optional line art - all rendered inside the real page border so it looks like a book page, not a bare canvas. Progress is saved so a child can pick up where they left off.

Output

A print-at-home PDF is generated from the same page layout the screen uses, with thoughtful options for home printers: an ink-saver mode that strips heavy background art (dramatically reducing ink use and leaving clean paper to write on), a grayscale mode for black-and-white printers, and control over page margins.

The solution: design and engineering

Beyond the feature list, a handful of design ideas are what make the product cohere. These are the parts worth understanding.

One book, rendered many ways

The single most valuable structural idea is that a page's content is one piece of data rendered in several contexts: as an interactive element on the editor canvas, as a printed page in the PDF, and as a playable activity in play mode. Because all three come from the same underlying content, what you arrange in the editor is exactly what prints and exactly what a child plays. There is no separate "export layout" to keep in sync, which eliminates a whole category of "the download doesn't match the screen" problems.

An extensible activity system

Every activity is built to a shared interface - a small contract that says how it's generated and how it's displayed. This is what lets the catalog grow: adding a new activity is a matter of writing one more generator that conforms to the contract, rather than touching the whole system. It also means every activity benefits from the same customization, preview, print, and play machinery for free.

Deterministic generation from a seed is the quiet hero here: it's what makes a regenerated book reproduce the same puzzles, so that a parent editing one detail doesn't scramble everything else.

A friendly, purpose-built editor

The editor renders the book page and lets a parent layer changes on top - text, images, stickers - all positioned in the same coordinate space as the final page. Full-page activities like coloring and drawing are treated specially: their surrounding chrome is removed so the art fills the page edge-to-edge, exactly as it will print.

The design goal throughout was to make customization feel like play rather than work. A parent should be able to make a book feel theirs in a few taps, without a manual.

A play experience kids return to

Play mode is a separate, joyful world from the editor. The standout is the Color & Draw activity - a free-draw coloring page where a child paints anywhere with a color picker, over optional line art, with brushes, an eraser, and undo/redo, all inside a proper bordered page. Getting that to feel like a real coloring book (rather than a plain white box) took care: the drawing surface sits inside the book's actual page frame, and everything a child places or paints shares one coordinate space so it looks and prints correctly.

Personalized stories and clever tracing

Two subsystems add a touch of magic. An AI writer generates a short, kid-safe story starring the child, which becomes a set of story pages. And the connect-the-dots activity can turn an image into a numbered dot-to-dot outline using image processing - with manual editing tools alongside it, because the automatic tracing is a helpful starting point rather than a perfect one. Designing for "the tool assists, the human finishes" produced a better experience than pretending the automation was flawless.

A print pipeline that respects home printers

Because the product is print-at-home, the PDF pipeline is built around the realities of a home printer rather than a commercial press. The same layout that renders on screen renders to the PDF, so there's never a mismatch, and the ink-saver and grayscale options exist specifically to make printing at home cheaper and cleaner. Small decisions - like letting the decorative page border reach the paper edge by default - add up to output that feels premium rather than like a worksheet printout.

A cohesive design system

The visual language is a small, opinionated design system: a friendly sky-blue and warm golden palette, rounded shapes, soft paper-like shadows, and a rounded, approachable type stack. The same tokens drive the product, the printed book, and the marketing site, so everything feels like one brand - a children's publishing studio rather than a piece of software. A nice technical detail is that pages scale cleanly to any size (thumbnail, editor, full-screen play) from a single layout, so a book looks right everywhere without special-casing.

What the build taught us

A few lessons generalize well beyond this project:

One data shape, many renderers, is a superpower. Representing a page once and rendering it into the editor, the print file, and the play view from shared coordinates removed entire classes of bugs, because there is no separate export to drift out of sync.

The clean mental model usually arrives after building the confusing version. Several features only became simple once we'd built a more tangled first version and could see where the seams belonged. The clearest example: line art for a coloring page belongs to the activity, while decorative images belong to the page - an obvious distinction in hindsight that only became obvious after conflating the two.

Build things so they degrade gracefully. Designing each optional capability to switch off cleanly when it isn't configured meant the product always ran and features could be turned on one at a time - which made development and staged rollout painless.

Reliability is a feature, and it's the one that matters most. For a product whose one tangible deliverable is a file the customer prints, "it works correctly every single time" is worth more than any amount of breadth.

Roadmap

In rough priority order:

1. A play completion and reward moment - a satisfying "you finished the whole book!" payoff, which is also what makes a child want to show it off.

2. Story-driven puzzles - using the child's own generated story to seed the word search, scramble, and other word puzzles, so the whole book feels authored rather than assembled.

3. A browsable template gallery and AI-generated cover art.

4. More activities - color-by-number, nonograms, memory games, spot-the-difference.

5. Multilingual editions - for a personalization product, a new language opens a whole new audience for modest incremental effort.

6. Editor polish - undo/redo across the whole book, custom page-number placement, and streamlined ways to add new activity types.

Closing

The product succeeds or fails on a single moment: a child seeing their name on a book made for them. Every decision, in the end, serves making that moment reliable, affordable, and fast to deliver. That's the quiet discipline of building for a real user - the cleverness stays invisible, and the delight is the point.