Last updated: 2026-11-06

The Friendsgiving Menu You Cook Together

A friendsgiving menu usually gets written as a list of dishes. The list misses what actually makes the meal work: who is making the stuffing, whose oven the mac and cheese bakes in, and when each cook needs to start so everything lands at the same time. Put those answers next to the dishes and the friendsgiving menu becomes a plan the whole group can run, whether everyone cooks at your counter or each dish happens in its own kitchen.

The keeping-everyone-together part is what momoChef's cooking sessions do. A session follows one recipe: everyone who joins sees the same current step, the same finished-step check-offs, and the same timers. Sessions are part of Premium, $0.99 a month or $9.99 a year. The recipes, the planner, and the grocery list are free.

Build the friendsgiving menu as a map

For each dish, write down three things: who is making it, where they're cooking, and when they need to start. The start times matter more than anything else on the list, because they're what lets four separate cooks land six dishes on one table at once. Plan the week in the planner and the grocery list builds from the planned recipes with duplicates combined, and the recipes themselves can live in one book the whole group can open.

Written that way, the menu shows the collisions before they happen: two dishes that need the same oven at the same time, two cooks who both planned to start at three, the one dish nobody has claimed. Those are easier to sort out on the plan than in the kitchen. If the holiday table grows after you've planned, add the dish to the map first and only then to the shopping, so the list stays one list instead of a text-message pile of "can you also grab."

Cooking together in the same kitchen

Several people cooking one recipe at the same counter works best on one shared session. Start the session from the recipe and give everyone the join code. The session shows each of them the same current step, so when whoever is at the stove advances the recipe, it advances on every phone at once. Finished steps get checked off once, in view of the whole group, so nobody re-chops onions somebody else already handled. Timers are shared too: there is one timer for the group, and if someone pauses it, it's paused for everyone. Tell each person which task they're handling, and use the shared step to keep track of the recipe.

Cooking together across kitchens

Cooks in different kitchens join a session the same way, with the dish's code. Start one session per dish that has a group working on it; each session carries that dish's current step, check-offs, and timers for everyone in it. For talking while you cook, use the video or voice call your family already has. momoChef's part is the shared recipe state, which is the thing a group call can't show: which step the dish is on and what's finished. Anyone in the session can see it, so when one cook hits a hands-busy moment, someone else can read where the dish stands and talk them through the next step. The same view lets a helper take over a step entirely, because the session shows what's already done.

The day-of run-of-show

1. Confirm the plan the night before. Every dish has its owner, location, and start time, and the recipes sit in one book everyone can open.
2. Have each cook check their own kitchen. The recipe's ingredient list against what's actually there; the app's pantry and the recipe's check-off list both help.
3. Start each dish's session at its planned time. The owner starts it and shares the join code with whoever is cooking or helping on that dish.
4. Follow the shared progress. Everyone in a dish's session sees the same current step, check-offs, and timers, so helpers in other kitchens know where the dish stands.
5. Check in before serving. Ask each cook where their dish is, and adjust the order or timing if one is running late.
6. Note what to change next year. Two minutes after the meal on which timings held and which didn't saves reworking the plan next November.

FAQ

Does cooking together in momoChef cost anything? The recipes, the planner, and the grocery list are free. Shared cooking sessions are part of Premium, $0.99 a month or $9.99 a year. Participants join a dish's session with its code.

Do my relatives need to install the app to cook along? They need momoChef to join a session, either the web app or the iOS app, plus the session's code from whoever started it. The video call can stay on whatever your family already uses.

Can the host see where everyone's dish stands? Anyone in a dish's session sees that dish's current step and completed check-offs; that progress is shared, not per-person. Each dish runs its own session, so the menu map is the overview across dishes.

What if a kitchen falls behind? Check that dish's session: its current step and completed steps show where it stands. Then decide whether to hold serving or lean on a dish that can wait or be reheated while the rest catches up. This is also why the start times live on the plan rather than in someone's head: when one kitchen slips, everyone can see which sync moments have slack and which don't.

Is this just for Friendsgiving? No. The same plan works for any meal cooked together: Christmas Eve split across houses, a dumpling day at Lunar New Year, a Sunday sauce with family on a call.

Start small: pick the dish several people will cook together, start its session, and send everyone the join code. momoChef is free to start and works in the web app or the iOS app.