Why It Ended Up on Absolutely Everything

Tiny state, no assets, and rules you can implement in an afternoon — the most portable game design ever written.

It is a reasonable claim that this genre has been implemented on more distinct pieces of hardware than any other game idea. Graphing calculators, oscilloscopes, office building facades, terminal emulators, watches, e-readers, car dashboards.

The reason is structural.

The state is tiny

A complete game is: a grid of ten by twenty cells, a current piece with a position and rotation, a preview queue, a score, and a level. That fits in a few hundred bytes. There is no world to load, no physics, no pathfinding, no persistence.

Compare almost any other well-known game. A platformer needs level data, sprite sheets, collision geometry, animation state. This needs an array.

There are no assets

No textures, no models, no audio files, no fonts. The pieces are rectangles. If your target can fill a rectangle, it can display the game — and if it cannot, a version made of text characters works, which is what the original was.

That removes the single biggest obstacle to porting anything: the asset pipeline.

The rules are short

The core loop is: spawn a piece, apply gravity, accept input, detect collision, lock, clear complete rows, repeat. A competent programmer can implement a playable version in an afternoon. The modern refinements — kick tables, bag randomisers, lock delay — add detail, not complexity.

This makes it the standard exercise for anyone learning a new platform. It is big enough to be a real program and small enough to finish, which is why it appears on every unusual device somebody has ever wanted to prove could run something.

No input requirements

Four directions and a rotate. That maps onto a keyboard, a d-pad, a phone screen, two buttons, or a rotary dial if you are determined. Nothing about the design assumes a particular controller, which is why touch versions work at all — a genre requiring precise aiming does not survive the transition to a touchscreen, and this one barely notices.

The consequence

Ubiquity compounds. Because it ran everywhere, everybody encountered it; because everybody encountered it, every new platform wanted one. Sixty years of computing hardware share almost no software in common. This is close to the exception.

Read next

• Why the 1984 Design Barely Needed ChangingForty years of iteration refined the edges and left the centre alone, because the centre was already right.
• Who Invented Tetris?Alexey Pajitnov wrote the original in 1984 at a Soviet research institute, on a computer that could not draw graphics.
• Where the Name "Tetris" Comes FromA Greek numeral prefix welded to the name of a racquet sport, because the author liked both.
• The First Version Ran on a Computer That Could Not DrawThe Elektronika 60 had no graphics mode, so the original pieces were built out of punctuation marks.
• Six Mistakes Almost Every New Player MakesThe specific habits that end early runs, and what to do instead.
• The Attack Table: What Each Clear SendsEvery clear type converted into rows of garbage, plus the bonuses that stack on top.