Cody Wymore
Blog
The party board, calm and mid-evening: CRUNCH APP SUPREME in outline type, a three-deep order line, sixteen wraps served, a scan-to-order QR code, and the clock reading 6:05 PM

Crunch App Supreme

Our household's fourth annual crunchwrap party got its own software this year: QR ordering, a one-button kitchen screen for the chef, and a synced countdown on every phone. 54 wraps, a 19-order rush, and 49 deploys on the day of the party. Ten of them shipped mid-party, most requested by people holding food.

Cody Wymore
Cody Wymore
VP, Client Solutions · Innovid
August 17, 2026
Jump to a section
  1. The Most Specific Software
  2. Editing the App
  3. The Numbers
  4. The Fifth Annual

It’s 6:30 p.m. on Saturday night, and 19 crunchwrap orders hit our kitchen in the span of 30 minutes.

Two of them arrived 2.9 seconds apart.

The cook (my wife, Molly, working two pans) never broke stride because the request line lived on an iPad, propped up on the counter. The iPad only ever showed her the next ticket, and the iPad only ever asked her to press one button per wrap.

I should back up.

Every summer, Molly and I throw the Crunchwrap Supreme party. She hand-builds a custom crunchwrap for every guest who wants one, which is most everyone (some of them go for seconds). This was the fourth annual.

For the first three, the ordering system was paper. You ordered off a central menu. You scribbled what you wanted on a post-it note, and you handed it off to the kitchen. By the end of the night, the front door was shingled with orders, doodles, and reviews. The door often got its own photograph. Molly loved that door.

The paper system also meant Molly cooked all night while we ran orders back and forth across a crowded apartment, and often it was hard to know whose wrap was up next.

This year, the morning of the party, I sat down with Claude, and we built an app.

The World’s Most Specific Piece of Software

Here’s what 45 people ended up walking into on a Saturday evening: a QR code sat on our living room TV. When you scanned it, you could type your name and build your wrap. The form walked you through your choice of tortilla, filling, queso, sour cream, cheese, fixings, all of them swappable, all of them with a “none” option, and vegan options throughout (we knew the dietary needs of our community).

A kitchen counter staged for the party: cutting board, chopped tomatoes, shredded lettuce, tostada shells, queso, plate stacks, and the kitchen iPad standing ready behind them
The mise en place. Note the iPad, reporting for kitchen duty.

After you filled out your form, your phone showed your place in line. Meanwhile, in the kitchen, Molly’s iPad showed her the next wrap with every ingredient spelled out in big letters. After it was cooked, she would press exactly one big button. Her hands would be busy manning two pans, so her main ask was: make it easy to advance the queue.

The kitchen iPad propped between plate stacks showing order number one with its ingredients in big pills and a single green button reading Wrapped. Next!
Molly’s entire interface. The next wrap, spelled out big, and exactly one button. Only one ticket per view at the time of this picture. More on that later.

My phone, meanwhile, was set up to make me the runner. When Molly triggered a wrap coming off the pan, it alerted me whose wrap was ready for delivery. I then tapped a button that said “Run it” as I left the kitchen, and that triggered a countdown in the living room, where the main TV would announce, “Wrap coming out: 10, 9, 8, 7, 6, 5, 4, 3, 2, 1.” At 0, I would time it to bring the crunchwrap directly to the diner.

We did that 53 more times.

Now, I’m not going to say everyone cheered every time the countdown came on the TV, but the fact that it happened more than once was beyond my wildest dreams.

The packed living room mid-party, guests talking in clusters with the party board glowing on the TV in the corner, faces blurred
The living room at full tilt.

Editing the App From Inside the Party

Forty-nine versions of the app shipped on the day of the party. Ten of them shipped between the first order at 4:44 PM and the last at 8:22, most of them requested by party guests or the chef herself.

We had built in a take-a-break button for Molly, but the first time she tried it, around wrap 30, nothing happened. The button had been broken since the very first deploy. The database was handing back the number 1, where the code expected the text character 1. A very small bug needed to be fixed to alert the whole party that she was taking a break, a well-deserved break.

Using my phone as a remote control for Claude, the button was fixed and redeployed in about two minutes. The TV then showed the proper take-a-break status along with a cheer, “LET’S HEAR IT FOR MOLLY,” and the room obliged.

She also asked midway through the party for two ticket orders on the screen at once, so that she could get one going while the other was finishing up. When the tomatoes ran low, we added an “86” (restaurant slang for “we’re out”), and anything she tapped would appear unavailable on every phone in the party within two seconds. An inside joke about someone spilling seltzer appeared on the TV as well, and the ticker jokes changed as the wrap count climbed, with new material joining the rotation at 15, 20, 30, 40, and 50 wraps, because I wanted the app to feel responsive and showcase the party’s collective effort.

The living room TV showing the party board mid-party: a seven-deep order line with names blurred, a wraps-served counter, the scrolling ticker, and the order QR code
Seven deep at the peak.
The board annotated with three numbered notes: the running count that reached 54, the live order line synced to every phone within about two seconds, and a working QR code that links back to this post
The board, annotated.

The Numbers, Because of Course There Are Numbers

Immediately after the party ended, I thought: we have the data. So what else to do but make a Spotify-Wrapped-style crunchwrap report, which went out by email to the entire party list the next morning?

The headlines:

  • 54 crunchwraps in 3 hours and 38 minutes.
  • The median wait was 24 minutes.
  • The fastest wrap went from phone to hands in 4.8 minutes.
  • One heroic soul ordered at 6:54 p.m., the deep end of the rush, and waited in line patiently for 51 minutes for a 5-star dinner.
  • 18 reviews came in through the app. All 18 were 5.0.

Imagine that!

Three slides from the party recap laid like printed cards: Anatomy of the Night with 391 hand-assembled crunchwrap layers, The Wait Wrap by Wrap with every wrap as a dot and a red 51-minute outlier at number 40, and When the Hunger Hit, a bar chart of the 19-order half hour
Three slides from the night’s Wrapped report.

I’ve recreated the entire Wrapped-style scroll ride, with every guest anonymized down to their wrap number, for you to see here.

Because half the party asked some version of “Wait, how exactly does this work?” I also made an interactive explainer that walks through a single order on every screen in the house, written for people who have never once thought about a database, which up until a few days ago included me. You can walk through it here.

A step-through diagram from the explainer: four screens around a central shared notebook labeled Redis, at the moment the runner taps RUN IT and the TV shows a giant countdown
From the interactive explainer: one order walking through every screen in the house.

There’s also a digital front door covered in “handwritten post-it notes,” one per order, faithful to the paper original that started it all. That one isn’t linked here. Some keepsakes are just for the hosts.

The Fifth Annual

If you’ve been following my journey on this website, you know I’ve built software before. The difference is I’ve never written a multi-screen, live-updating, simultaneous crowd-based ordering system, and I’d certainly never done it the morning of the party.

I was standing there holding a margarita when a guest asked, “Can it do this? Can it gray out ingredients when you’re out of them?” Every screen in the apartment was doing that in minutes, all night long.

Things like this used to take a team of people and a weeks-long sprint. On Crunchwrap Day, it was a dream, and a feeling like you are flying.

The fifth annual crunchwrap party may return to the post-it note. There is something classic about it, and I do kind of miss the tactile feeling, but at least for this year, the Crunch App reigned supreme.