Scaling Bookwood to Support Hundreds of Interactive Stories

Bookwood is an interactive fiction platform from GamerCat Studio, designed to host a growing library of choice-driven stories across Steam, iOS and Android. Unlike a conventional game with a largely fixed set of content, Bookwood needs to support new books being added continuously over time. Ocean View Games was brought into the project to help establish the technical foundations needed to make that possible. The challenge: a straightforward approach would be to package every story, image and other piece of content directly inside the application. That works when a project is small. It becomes much less practical when the goal is to support hundreds of books. As the library grows, application builds become larger, updates become heavier, and publishing a new story can require rebuilding and redistributing content that has not changed. We needed an architecture where Bookwood's application and its library of stories could evolve independently. Separating the application from the content: we designed Bookwood's content system around Unity Addressables and Unity Cloud Content Delivery. Instead of treating every book as part of the core application, story content and its associated assets can be packaged separately and loaded when required. This gives GamerCat Studio much more flexibility as the library grows. New books can be introduced without bundling the entire catalogue into every application build, while existing content can be updated without unnecessarily redistributing unrelated assets. It also keeps the core application focused on the systems responsible for presenting and running the stories rather than carrying every piece of published content itself. Designing for scale from the beginning: the important part of the work was not simply integrating Addressables. We needed to decide how Bookwood's content should be structured, packaged, identified and loaded so that the system remained manageable as the number of stories increased. That meant designing around the future shape of the product rather than only the content available during development. The architecture had to accommodate a growing catalogue while remaining understandable for the development team maintaining it. Building the content pipeline: we established the foundations for a workflow where books can be prepared as independently deliverable pieces of content. The system uses Unity Addressables to organise and reference assets, with Unity Cloud Content Delivery providing remote distribution. This allows the application to retrieve the content it needs while keeping the underlying delivery process separate from the main game build. The result is a content pipeline designed around Bookwood being a long-term platform rather than a single-release title.