Crossovers Spike Traffic, Not Habits — Why Zuda Failed and DC GO! Might Too

DC GO! is launching five interconnected webcomics through a month-long crossover called "Runaway to Ruin," betting that character crossovers and shared narratives can drive engagement on a struggling platform.

This is the exact move DC made when it created Zuda Comics in 2007 — serialized exclusives and interconnected story events meant to build a daily reading habit in young audiences. Zuda ran for eight years with the same architecture DC GO! The platform now uses originals written for it, character crossovers designed to pull readers between series. A launch cadence meant to create return momentum.

The platform collapsed in 2015 not because the stories were bad. Because a crossover event creates a temporary traffic spike and nothing more. Readers came for the story junction, read through it. Stopped returning — they never developed the habit of opening Zuda the way they opened Twitter or YouTube.

The mechanism DC relied on was sound in theory but missed something structural about how young audiences form attention patterns. The difference between a crossover and a habit is the same difference as between a watering can and a well. One event, even a clever one that links five stories together, is still an event with an end date. Scrolling TikTok has no end date. The algorithm generates friction-free novelty every six seconds without requiring the user to remember to return. Zuda required return, required the reader to visit independently, to remember the schedule, to develop loyalty to a specific URL.

sits inside an app that might solve this problem. It can push notifications, surface new episodes in the feed the way Webtoon does, create algorithmic serendipity rather than relying on memory. But none of that happens automatically once you build the feature. Watch whether the app sends you back to these comics next week, or whether it lets you forget they exist. That distinction determines everything that follows.