Freeways

Most simulation games hand you a god’s-eye view and a menu of pre-built parts. Snap a highway here. Drop an interchange there. Freeways does something quieter and far more subversive: it hands you a pen and walks away.

This is the work of Captain Games, the one-man studio of Justin Smith — a developer with a cult résumé. He’s the mind behind Desert Golfing, the endless, meditative putting game, and Enviro-Bear 2010, the gleefully absurd “drive a car while being a bear” experiment that became a shorthand for indie weirdness. Smith doesn’t make games that look like anyone else’s. He makes games that feel like a single stubborn idea pushed to its logical extreme. Freeways is exactly that.

The premise is small. You’re a traffic engineer. In front of you sits a set of dead-end highways — stubs pointing inward, cars waiting to pour out of them. Your job is to connect them. Not with pre-fab cloverleafs, but by drawing the roads yourself, freehand, with a click-and-drag tool that behaves more like MS Paint than SimCity. Then you press play, the cars flood in, and physics renders its verdict.

Market-wise, Freeways lives in the same neighborhood as Mini Metro and Freeform — minimalist systems-puzzlers that hide real depth under austere presentation. But it’s more hands-on than either. Where Mini Metro asks you to place stations and let the game route trains, Freeways makes the geometry of your own hand the entire challenge. With toll booths, a CommuterCam for tracing individual journeys, a long run of levels, and a scoring system built around speed, concrete, and the ever-looming threat of gridlock, it offers a lot of game for something that looks like it was rendered on an Atari 2600. This is a small game with an enormous skill ceiling.

• Freehand Road Drawing: The core hook. You build interchanges by literally drawing them — click-and-drag ribbons of asphalt that become overpasses, roundabouts, and bridges. No templates, no snapping. Your steadiness and your spatial reasoning are the tools.
• Live Traffic Simulation: Finish drawing and the grid comes alive. Cars, trucks, and other vehicles pour out of every highway stub in a continuous stream, exposing every flawed merge and doomed left turn in real time.
• Three-Axis Scoring: You’re graded on traffic flow speed, concrete efficiency (use less road, score higher), and the binary horror of the ‘Jammed!’ state — total gridlock that voids the run.
• Levels with Escalating Complexity: Progression introduces toll booths, tighter budgets, and geometrically nastier highway arrangements that turn a casual doodle into an engineering thesis.
• CommuterCam & Undo: A camera that follows a single car through your chaos — invaluable for diagnosing bottlenecks — plus an undo function that keeps iteration from becoming punishment.

The Gameplay Loop

The loop here is tight, and it’s worth understanding why. You look at a level. You form a mental model — “these two highways need an overpass, that pair can share a roundabout.” You draw. You simulate. You watch it fail. You revise.

That last part is the whole game. Freeways is a game about being wrong, gracefully. Your first interchange almost never works. A merge you were sure of turns into a standstill. A roundabout you drew a hair too tight forces cars to crawl. The simulation is a merciless, honest critic — it doesn’t tell you what’s broken, it shows you, in the form of a hundred stalled sedans. Then it’s back to the pen.

What lifts this above busywork is that the failure is legible. You can see the exact knot where everything seized. The CommuterCam is the secret MVP of the design — dropping into a single car’s perspective and following it through a doomed left-turn merge teaches you more about your own mistakes than any tutorial could. This is diagnostic play, and it’s satisfying in the way debugging code is satisfying: the problem is real, the cause is knowable, and the fix is in your hands.

The Difficulty Curve

The scoring is where Freeways reveals its teeth. Simply not jamming is the beginner’s goal, and it’s achievable. But the game quietly reframes the challenge once you clear a level: now do it with less concrete. Now do it faster. The three metrics pull against each other constantly. The fastest interchange is rarely the cheapest; the most concrete-efficient one often chokes under load. Optimizing all three at once is where the game transforms from a casual doodle into a strategic obsession — the kind of thing you close, then reopen twenty minutes later because you thought of a better roundabout.

This tension is the engine of replayability. A “solved” level is never really solved. There’s always a leaner, faster answer, and the leaderboard-brain knows it.

Where the Friction Bites

Let’s be honest about the rough edges, because they’re real. Drawing tight curves is finicky. When a level demands a compact loop in a cramped space, the freehand tool fights the player — draw, undo, redraw, mutter. It’s the price of the freeform philosophy, but it’s a price paid often, and on the fiddlier levels it crosses from “challenging” into “irritating.”

And the gridlocks, glorious as they are, can curdle into frustration. When a massive interchange jams, untangling which of your forty road segments caused the cascade is not always the elegant puzzle the game wants it to be. Sometimes it’s just a slog of trial and error. The undo button softens this, but it doesn’t cure it. This is a game that respects your patience right up until the moment it tests it.

The aesthetic is a statement, not a limitation. Freeways looks like it fell out of 1982 — flat colors, chunky pixels, an interface that could pass for a schematic diagram or a particularly stylish spreadsheet. Smith commits fully to this anti-fidelity approach, and here it’s doing real work. Stripping away visual noise means the only thing on screen that matters is the traffic. Every jam reads instantly. Every free-flowing curve is a clean line of motion. The low-fi look isn’t charming despite its simplicity; it’s functional because of it.

The technical demands are modest by design, and that’s a feature. A 2D game of this scope is light on hardware, and the engine is built to keep the simulation readable even when the grid is packed with vehicles — which matters, because a stuttering sim would undermine the whole diagnostic premise. It’s clean, it’s fast, and it never gets in its own way.

The platform split matters more here than in most games, because the core interaction is drawing.

On Android, the touchscreen is arguably the native fit. Dragging a road with a finger is intuitive, direct, and tactile — this is a design with mobile DNA in its bones. The catch is precision: on a small screen, those already-finicky tight curves get finickier, and a fat fingertip obscures the very line being placed.

On Steam, the mouse gives you surgical control. Fine curves are easier to place, the larger monitor gives interchanges room to breathe, and iteration moves quicker. The trade is a sliver of the tactile immediacy that touch delivers. Neither version is compromised — but for precision on the hard levels, the desktop edition has the edge. For losing an afternoon in bed, the phone wins.

Freeways is a puzzle game that makes the solution feel like it came from you — not from a menu, not from a template, but from your own hand and your own stubborn refinement. That authorship is its strength. Justin Smith took one simple verb — draw — and built a game with a skill ceiling well beyond what its look suggests.

It isn’t flawless. The freehand tool’s finickiness is a real friction point, and the game occasionally mistakes tedium for difficulty. Those are the scars of ambition, not laziness — a designer chasing a pure idea and mostly catching it. For anyone who’s ever sat in traffic and thought “I could design this better,” Freeways calls your bluff — and being proven wrong is half the fun.