Roots: play-by-mail and the tick

The persistent browser game inherits its most important idea from play-by-mail (PBM) strategy games of the 1970s and 80s. In a PBM game you mailed your orders to a moderator, the moderator processed every player's orders together, and results came back by post. The design consequence was profound: all players acted on the same information, at the same deadline, and the world advanced in discrete turns that nobody could speed up.

When the web arrived, that structure moved online almost unchanged. Hattrick, the Swedish football management game launched in 1997, ran its matches on fixed weekly schedules for teams around the world. Utopia (1998) ticked its kingdoms every hour. What mattered was that the tick was shared. Your decisions were made in the context of everyone else's, and the outcome was settled once, fairly, for all.

Designer Raph Koster's argument in A Theory of Fun is that games are fundamentally about pattern learning, and that the fun ends when the pattern is fully learned. The shared tick was the browser genre's answer: the pattern includes other people, and other people keep changing it.

The golden age: economies on a single server

The mid-2000s were the high point. OGame (2002) and Travian (2004) put hundreds of thousands of players into shared universes. Airline management sims such as AirlineSim ran persistent worlds where players competed for the same routes and passengers under real-ish economics. Football and cycling managers, space empires, nation builders: the format proved that you could run a genuinely shared economy with a database, a cron job and a few PHP files.

The business sims in particular found something the desktop tycoon genre never had. In a single-player game, the market is a script. In AirlineSim, if you flooded a route with capacity, the fare war that followed was against a real rival who would remember it. Prices, demand and reputation were emergent properties of a population of players, not lookup tables.

What the golden age got right: community as content

The mechanical insight of the shared tick was matched by a social one. Because every player experienced the same week, the forum was part of the game. Players argued about tactics, published guides, formed federations and rivalries, and, crucially, made the results meaningful to each other. A league table nobody discusses is a spreadsheet; a league table that a forum has been fighting over for three seasons is a sport.

The economics were modest and sustainable. Most of these games ran on subscriptions or small optional fees, with a large free tier. Server costs were low because the world advanced in ticks rather than in real time; a game could serve a hundred thousand players from hardware that a modern web app would find quaint. The result was a genre that could survive on a niche audience for a very long time, which is why several golden-age titles are still running today.

The collapse: Flash, phones and the energy bar

Three things happened between roughly 2010 and 2016.

The smartphone moved the audience. The ten-minutes-a-day player who used to open a browser tab now opened an app. Browser games were slow to follow, and those that did lost their identity on the way.

Free-to-play changed the economics of waiting. The browser genre had always used time as its currency. The mobile industry discovered that time could be sold: energy bars, build timers, "finish now" buttons. The shared tick, which treated every player's time equally, was replaced by the personal timer, which treated time as a thing to be monetized. The design goal shifted from "make the next tick interesting" to "make waiting for the next tick annoying enough to pay to skip."

Flash died. A large share of the browser-game audience had been trained by Flash portals. When browsers deprecated the plug-in and Adobe ended support in 2020, thousands of games simply stopped existing, and the sites that hosted them collapsed. The persistent-server games that never used Flash survived, but the ecosystem around them thinned out.

By the late 2010s the "browser game" had become shorthand for a shallow ad-funded time-waster. The serious management community had scattered to Steam.

The survivors, and what they tell us

Not every golden-age title died. Hattrick is still running, more than a quarter of a century after launch, with a core of players who have managed the same club for most of that time. Several of the space and nation-building games persist on reduced but stable populations. AirlineSim continues to run persistent worlds. What the survivors have in common is instructive: they never adopted the mobile monetization model, they kept the shared tick, and they let their communities carry the game through years when nobody was marketing it.

They also show the cost of standing still. Interfaces built for 2005 look and feel like 2005, and a new player arriving today is asked to accept a great deal of friction on the promise that the depth underneath is worth it. Most do not stay long enough to find out. The survivors preserved the design; they did not modernize the delivery. That gap, deep systems behind a modern interface, is precisely the one the returning genre can fill.

The rebirth: what the modern web can do

The tools that make the genre viable again arrived quietly.

• TypeScript and modern frameworks let a small team ship a desktop-class interface, with drag-and-drop scheduling and real-time state, that would have needed a native client fifteen years ago.
• Serverless functions and document databases mean the "cron job and a database" architecture that ran the golden age can now scale elastically and settle thousands of players in minutes.
• Edge deployment puts the client next to the player anywhere in the world without a data center.
• Open data lets a game key its economy to real-world signals, such as box office figures, instead of inventing everything.

Combine these and the genre's original strength comes back: a shared world, a shared tick, an economy that other people are pushing on. Only now it looks like a modern application rather than a table of links.

Design lessons the returning genre should keep

• One deadline for everyone. The shared tick is the whole point. Do not let it be bought.
• Asynchronous by default. Players should be able to do their week's work in one sitting, at any hour, and never be punished for not logging in at a particular time.
• Bounded worlds. The golden-age games ran multiple servers or leagues so that any player was competing against a legible group of rivals rather than an anonymous mass.
• Legible results. A results screen the community can argue about is worth more than any amount of polish.
• Low ceilings on runaway leaders. Persistent economies drift toward oligarchy; the durable games built in catch-up mechanisms, seasonal resets or diminishing returns to keep newcomers competitive.

Each of these is a constraint the mobile era treated as a limitation and the browser era treated as a feature. The returning genre's job is to remember which side of that argument produced games people played for a decade.

Why the weekly tick beats the energy timer

The core design argument for the returning genre is about respect for the player's time. A weekly settlement says: make your decisions when it suits you, submit before the deadline, and see how they fared against everyone else's. There is no advantage to logging in every hour. There is nothing to buy that skips the wait, because the wait is the same for everyone and it is the thing that makes the results meaningful.

An energy timer says the opposite: your attention is the product, and we will interrupt it as often as you tolerate. The two models produce different players. The timer produces churn. The tick produces a community that has been arguing about the same league table for years.

The browser tycoon game did not deserve its reputation. It was the format that let ordinary people compete in a real economy without buying a console. That format is back, and the management genre is better for it.