Qwen 4 Preview Builds a 63,000-Word Interactive Flipbook
Resumo
Pixel shares a DEV Community case study exploring how Qwen 4 Preview handled a complex, multi-stage creative coding project. The result includes a 63,258-word, 40-chapter mystery, 42 SVG illustrations, and a 652-page browser flipbook, with automated checks reporting no runtime errors or text overflow.
DEV Community
One Brief, 63,000 Words, 42 Illustrations, and a Working Flipbook: A Qwen4 Case Study
One brief. 40 chapters. 42 illustrations. A working browser-based flipbook. What happens when you give a newly released flagship model a project that can't be completed in one shot? When a new flagship model appears, the usual first tests are familiar: ask it a hard reasoning question, throw a coding benchmark at it, or have it build a small app. I wanted to try something less tidy. I gave Qwen 4 Preview a project with several kinds of work tangled together: write a complete children's mystery, create a consistent illustration system for it, and turn the result into an interactive book that actually works in a browser. The output was: A 63,258-word novel across 40 chapters. 42 SVG illustrations built around a reusable library of nine characters. A single-file, 652-page HTML flipbook. A headless browser run that reported zero runtime errors and zero text overflow. The run took about 1 hour and 42 minutes and involved 242 assistant turns. I ran the model through Jouzu, a coding-agent harness. The source repository contains the prompts and generated artefacts. You can open the finished flipbook here. This isn't a benchmark, and I'm not claiming that one run settles anything about the model. It is a practical look at how Qwen 4 Preview handled a long-running task where the requirements had to survive across multiple stages. Why this particular test? The project is called Pip Parker and the Bureau of Lost Things. Pip is a boy who labels everything. When his brother's stuffed dinosaur goes missing, the trail leads to a bureaucratic animal office that files the town's lost things. There's a mystery to solve, a set of clues to pay off, and a midpoint reframe: the apparent thief isn't stealing things; he's saving them. A children's mystery makes a useful stress test because continuity failures are easy to spot. A character can't suddenly know something they haven't learned. An object can't be in two places at once. A clue introduced early has to matter later. And the ending has to resolve what the opening set in motion. Then I added two more layers. The book needed illustrations, but not 42 unrelated images. It needed a consistent visual language: nine reusable characters, an eight-colour palette, and SVG artwork that reused the same character definitions. Finally, it needed to become a real reading experience. Not a PDF export or a long HTML page, but a flipbook with page turns, navigation, bookmarks and controls. That combination made the task interesting. The agent had to move between narrative generation, structured visual assets and application development without treating them as three unrelated jobs. The brief: constraints first I deliberately made the brief specific. I didn't want the model to decide halfway through that 20 chapters were enough, change the cast, or quietly simplify the illustration requirements. The novel specification called for: 40 chapters, each between 1,400 and 1,700 words. A target of roughly 60,000 words. A fixed cast and timeline. Five explicit plant-and-payoff pairs. A continuity ledger tracking day-by-day events and object ownership. A fixed final sentence. Kid-safe content rules: no death or gore, and a lonely rather than evil antagonist. The plant-and-payoff requirements were especially useful. A detail introduced in one chapter had to become meaningful several chapters later. The model couldn't just make each chapter locally plausible; it had to preserve information for future use. The illustration brief was equally constrained: A nine-character SVG library. A locked eight-colour palette. One cover illustration and one illustration for each of the 40 chapters. The same SVG definitions reused across the plates. The point of specifying these constraints wasn't to make the prompt impressive. It was to make success and failure observable. It took one magic prompt The prompts are preserved verbatim in PROMPT.md. 1. Write the book and create the art system. The initial brief produced the novel, the i...

Powered by Readybot.io