Household Sharing

Your family's recipes live in five different phones. Here's how to fix that.

Screenshots on one phone, WhatsApp links on another, a laminated card in a drawer — your household's recipes aren't disorganised, they're just scattered across everyone who happens to remember them.

Ask most households where "the recipes" actually live, and you won't get one answer. You'll get five. One partner has a folder of screenshots on their phone. The other has a stack of half-remembered links sent over WhatsApp months ago. The kids' favourite dinner exists only as a memory of "the one Mum makes with the chicken." Grandma's trifle recipe is on a laminated card in a drawer nobody's opened since Christmas.

None of this is disorganised, exactly — everyone's kept track of what they personally know. The problem is that a household doesn't cook from one person's memory. It cooks from whatever's collectively known, and right now, that collective knowledge is split across however many phones and drawers are in the house, with no single place that reflects what the family actually knows how to make.

Why "just ask each other" doesn't scale

The obvious fix — just ask whoever knows the recipe when you need it — works fine occasionally. It falls apart as a system, for a few predictable reasons.

The person who knows the recipe isn't always around, or isn't always in a position to dig through their camera roll to find it. Recipes get slightly misremembered in the retelling ("was it two cloves of garlic or three?"). And the whole approach puts the burden of memory on individual people rather than on a shared system — which means every recipe is one lost phone, one deleted app, or one bad memory away from actually being gone.

A household doesn't cook from one person's memory. It cooks from whatever's collectively known.

This shows up most obviously with shared cooking duties. If one partner does most of the weeknight cooking and the other does weekend batch-cooking, they're often working from two completely separate, informal recipe collections that never actually merge into one household resource — even though, logically, they're cooking for the same family, from the same kitchen, often the same ingredients.

What a shared system actually needs to do

A genuinely shared household recipe system isn't just "let more than one person log in" — plenty of apps technically allow a shared login, which just means everyone's using one person's account and hoping nothing gets confused. What actually works needs a few specific things:

• Real multi-person access, not one shared password everyone half-remembers — each person able to add, search, and use recipes under their own account, contributing to one shared pool
• A shared weekly plan, so meal planning isn't one person's solo task that they then have to communicate to everyone else after the fact
• One shopping list that reflects everyone's contributions, not separate lists that need manually merging before the shop
• No loss when someone's not around — if the person who usually plans is away, the recipes and the system are still there for whoever's cooking that week

Where mmmiso fits

This is the part mmmiso's household sharing is built around: up to four people sharing recipes and a single subscription, so the family's actual collective recipe knowledge lives in one searchable place instead of scattered across separate phones. Whoever adds a recipe — whether that's photographing a card from a parent, saving a link from a friend, or screenshotting something from social media — it's there for everyone in the household from that point on, not locked to whoever happened to save it.

mmmiso also takes the weekly plan out of one person's head, because it generates a week's plan in a single tap rather than leaving someone to work it out. One honest limit: the plan and shopping list live on the device that made them, so household sharing covers the recipe collection, not the plan itself. If someone else is doing the shop, the plan needs passing on the old-fashioned way.

The honest starting point

If your household's recipes are currently split the way most are — some on one phone, some on another, a few only in someone's memory — you don't need a big reorganisation project. Just ten minutes each, pulling your own scattered favourites into one shared place. What comes out the other side isn't just tidier — it's a genuine shared resource that doesn't depend on any one person being around, remembering correctly, or having their phone charged.