a friendly autopsy of the 4th annual · zero jargon without a translation
No screen ever talked to another screen. Your phone never texted Molly’s iPad. Instead, every screen did two simple things, over and over, all night:
1. Write: when you tapped a button, your screen asked a (ours runs on Vercel) to jot something in the notebook. “Sam wants a beef crunchwrap, no tomatoes.”
2. Read: every couple of seconds, every screen asked the same server, “anything new in the notebook?” and redrew itself to match. That habit has a name: .
Keep that picture in your head and the whole night makes sense. Ready? First, meet the five screens.
Stop 2 · the tour
Five kinds of screens ran the party, and every one of them is a different window into the same notebook. Each shows only what its person needs. Tap each one open.
You scanned a QR code, typed a name, built your wrap, and got a live spot in line. No app store, no account, no password. Your phone remembered you with a little anonymous sticker in the browser (localStorage), which is why coming back later still showed your order.
Clever detail: while you waited it showed “3 wraps ahead of you,” and when yours was delivered, your phone threw its own private confetti.
Built around one rule: the chef gets one button per crunchwrap. The next two orders appeared side by side automatically, every ingredient spelled out in big pills. When one was done she tapped Wrapped. Next! and the queue advanced itself.
She also had emergency powers: pause all ordering, skip an order, mark an ingredient as run out (which instantly greyed it out on every phone in the room), and hand a wrap over directly, bypassing Cody entirely.
When Molly finished a wrap it showed up on Cody’s screen as ready to run. His one glorious button: RUN IT! Tapping it as he left the kitchen is what started the party-wide countdown, timed to his walk into the living room.
After the countdown, the notebook marked the wrap delivered by itself a few seconds later. Nobody owed the app a third tap.
The live line, a giant clock, a QR code big enough to scan from the couch, and the scrolling ticker whose jokes secretly changed as the night went on: new lines joined the rotation past 15, 20, 30, 40, and 50 wraps served. When Molly took a break, the whole board turned into a round of applause for her.
Every order, redrawn as a handwritten post-it on a digital front door, a tribute to the paper door from the first three years. Your stars and reviews got inked onto your note. It’s saved forever, along with every number from the night.
Stop 3 · the machinery
You’ve met the stations. Now watch them work together: the notebook in the middle, the screens around it, drawn as it all stood on party night. Tap through the eight moments of one real order and watch what each screen shows as the notebook changes.
Stop 4 · the goosebumps part
Remember the countdown? Every phone in the room, and the TV, all yelling 3… 2… 1… in perfect agreement. Here’s the problem with that: every phone hears the news at a slightly different moment. Wifi is sloppy. If each phone just started its own 10-second timer when it heard, the room would drift apart.
The fix is a shared finish line: the notebook writes down the exact moment on the clock when the wrap comes out. Each phone does its own little math against that shared moment. Late phones just join the count already in progress, at the correct number.
Try it. Phone B always hears the news 1.5 seconds late. Ring the bell in both modes:
Stop 5 · the disasters that didn’t happen
A party is a hostile environment: greasy thumbs, dying batteries, forty phones on one wifi. The design assumed chaos. Tap the fears:
The fear: the kitchen loses the whole queue.
The reality: the queue lives in the notebook, and the iPad was only a window into it. Plug in any phone or laptop, open the kitchen page, and everything is exactly where it was, mid-wrap included.
The fear: orders collide and one vanishes.
The reality: the notebook has a take-a-number machine that physically cannot hand out the same number twice, and every order gets its own page. We tested it by firing 20 orders in the same instant. All 20 survived, numbered 1 through 20.
The fear: the second tap wraps the NEXT order, which is still raw.
The reality: after every tap the button goes to sleep for one second and shows a checkmark. Dangerous buttons (like skipping an order) demand a second, deliberate tap before they do anything.
The fear: people keep ordering something that doesn’t exist.
The reality: Molly taps it on her 86 list, and within two seconds every phone in the room shows it crossed out and unclickable. Anyone mid-order gets bumped to the next best choice. Tap it again when restocked and it comes back.
The fear: (he did. About forty times.) Old screens run old buttons.
The reality: every screen checks a version stamp with each poll. New version? The page refreshes itself. That’s how the ticker jokes, the two-burner kitchen, and the Spindrift alert all appeared mid-party without anyone touching a thing.
Stop 6 · the decisions
Every piece of this is boring technology, picked on purpose.
Fancy apps push updates to your phone instantly. This one asks “anything new?” every 2 seconds. At party scale a two-second-old answer might as well be live, and bad wifi costs almost nothing: the very next ask picks up whatever the last one missed.
There is exactly one place the party’s state lives. Nothing to sync, nothing to argue. Any screen can die, reload, or join late, then read the truth straight back.
Molly’s screen was designed for a person holding a spatula: one button per wrap, text readable from a step away, nothing precious near the edges. The busier the person, the fewer the buttons.
A party app that asks you to create a password has already failed. A name and an anonymous browser sticker were enough to hold your place in line all night.
Ten seconds is long enough for the room to turn toward the kitchen and short enough that nobody goes back to their conversation. The whole feature exists to make people cheer.
The physical post-it door was the beloved thing. The app’s job was to rebuild it with the night’s real data so it can’t be lost.
Stop 7 · the parts list
The notebook, the screens, the countdown: all of it runs on a handful of real, named services, none of them exotic. Here’s the cast, and what each one actually did that night.
The construction kit
A free, widely used toolkit for building websites. One codebase describes all five screens, and Next.js turns it into fast web pages. The whole party app is a single Next.js site with six addresses.
The host
The service the site lives on. When Cody hits deploy, Vercel builds the site and publishes it to the internet in about a minute. That’s the machinery behind the mid-party updates: publish, and every screen at the party refreshes itself onto the new version.
The notebook itself
The shared notebook is really a tiny cloud database called Redis, run by a company called Upstash. Its specialty is answering tiny questions in a few milliseconds, which is exactly what forty screens asking “anything new?” every two seconds requires. It held the orders, the take-a-number counter, the 86 list, the pause switch, and every countdown finish line.
The front door
A printed sheet by the chips. Pointing a phone camera at it typed the site’s address so nobody had to. A 30-second explanation at the door was the entire onboarding.
The app store you skipped
Nothing was installed. Safari and Chrome ran everything, and a small anonymous sticker in your browser remembered which order was yours. It’s also why the same app worked on iPads, TVs, and every phone brand at once.
The build crew
Cody built this with Claude, an AI assistant, in about a day, and kept building during the party itself. The two-burner kitchen screen, the 86 list, and the Spindrift alert each went from “can we…” to live-on-every-screen in minutes.
Stop 8 · what do I do right now
You now understand the whole machine: one notebook, many windows, one shared finish line. Here’s your next move, pick whichever fits:
Live MAS