Inspiration

We love Overcooked because it turns a simple job into total chaos the moment you split it across a group of friends. We wanted that feeling in a driving game. Everyone has a phone in their pocket, so we figured: what if every phone was one part of the same car?

What it does

Up to four players scan a QR code on the laptop, and each phone becomes part of one taxi. One person steers with a wheel on their screen. One handles the gas and brake. One has the map, sees the route to the next passenger, and can call out turns or drop a marker on the main screen. One opens the doors, and passengers won't get in or out until they do.

You pick people up and drop them off. Each drop-off earns money and adds time to the clock, and hitting pedestrians, bikes or other cars costs you both. You start with 90 seconds. With two or three players, the roles get combined so everyone still has a job, and you can also play solo with a keyboard.

How we built it

The city is a hand-drawn-style isometric diorama, built on April Zhu's Pocket City engine (MIT licence). It draws the streets, buildings, seasons and traffic from OpenStreetMap data, and renders frames in Web Workers on a 2D canvas.

On top of that we wrote the game in plain JavaScript: taxi physics, fares, collisions, the HUD and the minimap. For multiplayer we wrote a small Node server with no dependencies and a hand-rolled WebSocket implementation. The laptop runs all the game logic, and phones only send their inputs (wheel angle, pedal pressure, button taps). The laptop sends back a stream of the game state 10 times a second.

We also wrote our own QR code encoder, so the whole game works offline as a single HTML file. For the navigator, the laptop finds a route through the road grid and sends it to the map phone.

Challenges we ran into

Campus Wi-Fi blocked phones from talking to laptops. We had to play over a phone's personal hotspot. Getting four people to control one car without it feeling broken. Gas and brake are analog. The wheel springs back when you let go. If a phone disconnects mid-shift, its controls let go so the taxi doesn't take off on its own. Keeping the original driving feel. When we rebuilt the controls to take phone input, we tested that keyboard driving gives exactly the same numbers as before. Phones being phones. Mobile Safari kept zooming in on taps, and it won't let a webpage hide its toolbar.

Accomplishments that we're proud of

It actually works as a party game: scan a code and you're in, with no app and no sign-up. The city looks great, and it's built from real streets. No outside libraries: the server, the WebSocket code and the QR encoder are all our own.

What we learned

Splitting one task across several people is an easy way to make a game fun and chaotic. With multiplayer, one device has to own the game state. Making the laptop the authority made everything simpler. Test on real phones early. Desktop browsers hide a lot of mobile problems.

What's next for tbd

More cities. Smoother driving and a lower, Mario Kart–style chase camera. More game modes.

Built With

Share this project:

Updates

Submission history