Here is the shape of it. One of you found the recipe, so it is on their phone. One of you does the shop, so the list is on the other phone. Both of you have opinions about Thursday. By the time the recipe has been screenshotted, sent, lost in the chat, re-sent and read out loud over the noise of an extractor fan, you have spent more effort on logistics than on the actual dinner.
None of that is a cooking problem. It is a sharing problem, and it is worth solving properly because cooking with someone is one of the good ones. It is the bit of the day where you are both in the same room doing something with your hands.
The four things a household actually needs to share
Any two people who cook together are sharing four separate things, and most tools only handle the first one.
1. The recipes
A shared cookbook that either person can add to, edit and search. The test is whether your partner can find the curry you made in March without asking you where you put it. If the answer involves scrolling a chat thread, the recipe is not really shared.
2. The plan
What you are eating this week, visible to both of you, agreed once rather than renegotiated nightly. A calendar you drag recipes onto does more for household peace than any amount of meal-prep advice, mostly because it turns "what do you fancy" into a question with an answer already written down.
3. The shopping
The list has to build itself from the recipes, and it has to update on both phones live. Whoever is nearest the shop buys the things. This is also the single best fix for the quiet imbalance where one person carries the whole plan in their head and the other genuinely does not know what is needed.
4. The cooking itself
Two people, two phones, one dish. Both of you should be able to follow the same steps at the same time without one person reading aloud while the other stirs. Timers that belong to the recipe rather than to whoever remembered to set one.
What this looks like in Manjo
Everyone gets their own account and cookbooks get shared between them, which matters more than it sounds. Sharing one login means sharing notifications and stepping on each other constantly. Separate accounts means your own phone behaves like your own phone.
- Shared cookbooks anyone in them can add to, edit and cook from. Save a recipe from a link, a photo or a cooking video and it is there for everyone straight away.
- Shared shopping lists that build from any recipe and sync live, including offline in a supermarket basement.
- Meal planning you both look at, so Thursday is settled on Sunday.
- Let's Cook, which walks through the steps hands-free with the timers built in, on each phone separately.
- Twist It, for when one of you is vegetarian this month. Remix the recipe and the original stays untouched for everyone else.
Households this suits
Couples. The core case. One cookbook called something daft, a shared list, and the end of forwarding links to each other.
Families with teenagers. Usually two cookbooks: the household one, and a smaller one of things a fifteen year old will genuinely cook unsupervised. Being able to send someone to the shop with a list on their own phone is worth the setup on its own.
Flatmates. One shared cookbook for the meals you cook together, one shared list, and everything else kept private. Shared cooking is much easier to sustain when the admin is not somebody's unpaid job.
Family spread across places. A cookbook shared with a parent or a sibling is a surprisingly good way to pass recipes down, especially the ones nobody ever wrote out properly because they live in someone's hands.
The recipes that are already on paper
Every household has some. A card in handwriting you would recognise anywhere, a page torn from a magazine in 2009, a book that falls open at the same three recipes. Those are the ones worth rescuing first, because they exist in exactly one copy and the kitchen is a dangerous place for paper.
Photograph the card and Manjo turns it into a typed, searchable recipe you can cook from and share. Keep the photo too. The handwriting is half of why the recipe matters.
A shared cookbook is a private thing
What a household eats is quietly personal. It says who is ill, who is pregnant, who is skint this month, who has stopped eating meat. So Manjo carries no ads and no ad tracking, and never will, which is a public commitment rather than a phase. Your recipes and your account live on EU infrastructure in Frankfurt, and you can export or delete the lot whenever you like.
Cookbooks are private to the people you put in them. Nothing you save is public unless you decide it should be.
Common questions
What is the best way to share recipes with your partner?
A shared cookbook both of you can add to beats sending links back and forth, because the recipe stays findable after the conversation scrolls away. Look for something where either person can add and edit, where the shopping list is shared too, and where you can both cook from it at the same time on your own phones.
Can two people use the same recipe app account?
Sharing one login means you also share notifications, meal plans and any private list, and only one of you can be signed in comfortably at a time. Separate accounts with shared cookbooks is the setup you want: your own phone, your own view, the same recipes.
How do you organise family recipes that are on paper?
Photograph each card or page, then get them turned into text so they are searchable and safe from a kitchen flood. Keep the photo of the original alongside the typed version, because the handwriting is half the point.
Is there a recipe app that works for a whole household?
Yes, as long as everyone gets their own account and the cookbooks are shared rather than the login. Flatmates usually want one shared cookbook and one shared shopping list; families with teenagers often want a second cookbook for the things the kids actually cook.