A shopping list for couples that actually stays in sync
Two people, one household, and a running argument about whether anyone bought milk. The usual fix is a WhatsApp thread, which works until you're actually in the shop trying to scroll back through it past three photos of the cat.
A shared list solves this, but only if it handles the awkward bits: both of you editing at once, one of you underground in a car park, and the fact that you probably don't have the same kind of phone.
Both of you, at the same time
Once you're in a shared household you see the same list. Your partner adds bread at home, it appears on your phone in the shop. You tick off tomatoes, they see it happen.
Changes travel over a live connection, with a slower check every thirty seconds sitting underneath as a backstop, so a dropped connection means a short delay rather than a lost item.
Different phones, same list
An iPhone and an Android phone work together on the same list at the same time. So do two iPhones, or a phone and a laptop, since there's a browser version at app.forkandspoon.app that runs the same account without installing anything.
This is worth saying out loud because a lot of the neatest sharing features in this category quietly assume everyone's on Apple. If one of you switched phones last year, that shouldn't cost you your shopping list.
Only one of you pays
A subscription covers the household. Whoever set it up pays, everyone else joins for free and gets the same shared list, the same week menu and the same cookbook.
That's a deliberate choice rather than an oversight. Charging both halves of a couple for one kitchen is the kind of thing that makes people go back to WhatsApp.
The bit to know before you join
When you accept an invitation to someone's household, your own personal list is wiped and theirs becomes the one you share.
There's a reason for it: two lists merging automatically produces a mess that neither person recognises, and somebody's carefully organised sections lose. Picking one as the starting point is cleaner. But it does mean that if you've got a list you care about, you should screenshot it or move the items across before you accept, because they aren't coming back afterwards.
Leaving a household later gives you a clean break rather than taking a copy with you.
In the shop, without signal
The list lives on your phone, not on a server you need to reach. Tick things off in the freezer aisle or a basement car park and it all still works; the changes queue up and go out when you surface.
For a shared list that's the part that matters most. If one of you is offline and still ticking, nothing is lost and nothing overwrites the other person's work when the connection returns.
Beyond the list
The same sharing covers the cookbook and the week menu. You plan Tuesday, they can see Tuesday. One of you adds a recipe, it's in the collection for both of you.
And for anyone outside the household, any single recipe can go out as a link that opens as a normal web page in any browser, with no app and no account needed at the other end. Handy when your mother asks what you made.
Questions
Do we both need to pay?
No. One subscription covers the household, and everyone else cooks along on the free tier. Sharing lists and cookbooks isn't behind the paywall.
Does it work between an iPhone and an Android phone?
Yes, at the same time, on the same list. There's also a browser version if one of you would rather not install anything.
What happens to the list I already had?
When you join someone's household your own personal list is cleared and theirs becomes the shared one. Screenshot anything you want to keep before you accept the invitation.
How fast do changes show up?
Within a second or two normally, with a slower check every half minute as a backstop. If one of you is offline the changes queue up and land when the signal comes back.