slrp
Tools + comparisons8 min readUpdated

AnyList alternatives
when a shopping list stops being enough

AnyList is a genuinely good shopping list. Here's the moment couples outgrow it, and what to look for when the plan matters more than the list.

AnyList alternatives — when a shopping list stops being enough

There's a particular Tuesday evening that most couples who share a shopping list will recognise. The list is immaculate. Aisles grouped, duplicates merged, both phones in sync, that satisfying little strike-through as things go in the trolley. And then one of you asks what the milk and the coriander and the two tins of chickpeas are actually for, and nobody can quite remember.

That's the moment. Not a bug, not a failure, just the point where a shopping list has done everything a shopping list can do. AnyList is very good at being a shopping list. The question worth asking is whether a shopping list is still the thing you need.

What AnyList genuinely gets right

Let's be fair to it, because a lot of "alternatives" posts aren't. AnyList has been around a long time and it earns its fans.

  • The list itself is excellent. Items auto-categorise into aisles, it learns your phrasing, and it handles quantities sensibly. Very few apps get this unglamorous part right.
  • Sharing actually works. Two phones, instant sync, no arguing about whose version is current. For a lot of households that alone is worth the subscription.
  • It's fast. Open, type, done. No ceremony, no onboarding flow standing between you and adding milk.
  • Recipes are supported. You can store recipes and push their ingredients onto a list.

If what you want is a shared list that two people can trust, AnyList is a perfectly good answer and you can stop reading here. Genuinely. Switching apps for the sake of it is a hobby, not an improvement.

The moment a list stops being the thing

Here's what changes. Early on, the list is the plan. You decide roughly what you fancy, you write down what you need, you shop, you cook. The list carries the whole idea.

Then a few things pile up. You start cooking more deliberately. One of you takes Tuesdays and Thursdays, the other takes the weekend. You notice you've made the same four dinners for a month. Someone asks on Sunday what you're eating on Wednesday, and the honest answer is "there are chickpeas involved".

At that point the artefact you're actually managing is no longer the list. It's the week — which meals, on which nights, cooked by whom, and whether you already own half the ingredients. The list becomes an output of that, not the source of truth.

A list-first app can't really help you there, because it doesn't know what you're cooking. It knows you need coriander. It doesn't know the coriander is for Thursday, that Thursday is the night you get home at seven, or that Thursday's recipe also wanted the chicken thighs you've already got in the freezer.

The two-app trap

Most couples don't switch at this point. They add. A list app for the shopping, and something else for the planning — a notes app, a shared calendar, a whiteboard on the fridge, a recurring text thread called "dinner???".

It works for about three weeks. Then the two drift. The plan says Thursday is the salmon, the list still has last week's salmon on it because nobody ticked it off, and now neither artefact is trustworthy. You end up doing the reconciliation in your head at the supermarket, which is exactly the job you downloaded an app to avoid.

The tell is when one of you starts prefacing things with "is that the current list?". That question means you now have two sources of truth, which is the same as having none.

Adding a second tool is a reasonable instinct — each one really is good at its own job. The problem is that the handover between them is manual, and manual handovers are where households lose things. If you're going to run two apps, at least make the list the one that's downstream, so there's a clear direction of travel.

What to look for once you've outgrown a list

If that's where you are, the features worth caring about change. Ignore the marketing bullet points and check these four.

  1. Does the grocery list build itself from the plan? This is the whole ball game. You should choose meals and get a list, not choose meals and then write a list. We've gone into the mechanics of this in how to auto-generate a grocery list from your meal plan.
  2. Does it handle two people as first-class? Not "share a link" — genuinely two accounts, one library, either of you can add a recipe or claim a night. Our guide to setting up a shared grocery list covers what that looks like in practice.
  3. Can you get recipes in from anywhere? Your recipes live on blogs, in screenshots, in your mum's handwriting. If an app only works with recipes you type in by hand, you won't use it past week two.
  4. Does it know what you already own? A list that cheerfully tells you to buy a third jar of cumin isn't saving you anything.

The alternatives worth a look

Rough shape of the landscape, so you can skip the ones that aren't for you.

AppBest atWeak spot
AnyListThe shared list itselfDoesn't plan the week for you
PaprikaRecipe collecting and scalingSharing between two people is clunky
Plan to EatCalendar-style planningFeels heavy if you only plan a few nights
MealimeFast weeknight cookingIts recipes, not yours
slrpTwo people, one plan, list falls outNewer, smaller recipe catalogue

If you want the longer version of that comparison, meal planners that also do grocery lists goes app by app.

If you mostly want better lists

Stay where you are, honestly. AnyList does lists better than most planners do lists. Bolting a planner on top of a workflow that isn't broken is how you end up with two apps and neither is current.

If you mostly want your recipes organised

Paprika is the veteran and it's still good at hoarding. The catch for couples is that it was built around one person's library. You can make sharing work; you'll just feel the seams every time.

If you want the plan to be the thing

This is where the newer couple-shaped apps live, including ours. The test is simple: can both of you see Wednesday, change Wednesday, and have the shopping list update without anyone retyping anything?

Where slrp fits, honestly

Since you're on our blog, here's the straight version rather than the pitch.

Both of you share one library, one plan and one list. You paste a recipe URL and it lands in the library, structured, without the four paragraphs about someone's trip to Puglia. You drag meals onto nights. The grocery list assembles itself from whatever is on the plan, merges duplicates, and checks the pantry before telling you to buy more rice. Something like Classic Beef Stew with Potatoes, Carrots, Celery & Crusty Bread goes on Sunday, and Sunday's ingredients appear on the list without either of you thinking about it.

What we're not is a bigger AnyList. The list is deliberately the last step, not the first. If you love curating a list, you may find that annoying rather than freeing — that's a real preference and it's fine.

We're also newer and smaller. If your deciding factor is a decade of polish on list-editing specifically, AnyList wins that one.

Moving without losing everything

The reason most people don't switch isn't the app. It's the sunk cost of a recipe collection.

  • Don't migrate everything. Nobody cooks their whole archive. Bring across the fifteen or twenty you actually make.
  • Start with next week only. Plan four nights. Not seven, four. Leave room for leftovers and the night you order in.
  • Run both for a fortnight. Keep the old list alive while the new plan proves itself. If it doesn't stick, you've lost two weeks and nothing else.
  • Move recipes as you cook them. Making Spinach Lasagna with Ricotta on Thursday? Import it Thursday. In a month the library builds itself out of things you genuinely eat.

So should you actually switch?

A short and slightly boring decision guide.

Stay with AnyList if the list is the only shared thing you need, you already decide meals in your head, and the shopping trip is the only bit that needed fixing. It's good software and there's no prize for churn.

Look elsewhere if you've noticed the same four dinners on rotation, if "what are we eating Wednesday" is a recurring conversation neither of you enjoys, or if one of you quietly does all the planning and would like that to stop being true.

That last one comes up more than people expect. A shared list splits the shopping. It doesn't split the thinking. If the thinking is the part that's lopsided, a better list won't touch it — and no app fixes it by itself either, though it helps when both of you can see the same week and change it.

Whichever way you go, the useful question isn't which app has more features. It's which artefact your household actually runs on: the list, or the week. Pick the tool that's built around that one, and the other thing tends to sort itself out.

Written by the slrp team
A meal planner for couples who cook together

We’re a small team building slrp from Melbourne. Field notes is where we share what we’ve learned about meal planning, splitting cooking, and surviving the weeknight “what’s for dinner?” loop.

Keep reading.

All field notes → /blog

Tools + comparisons

3 Aug 20268 min read

Mealime alternatives — for couples who cook together

Mealime is closing on 21 October 2026 and your saved recipe list goes with it. Here are the meal planners couples who share a kitchen should look at instead, and how to get your recipes out first.

Tools + comparisons

8 June 202613 min read

Meal planner with grocery list — apps that do both well

Looking for a meal planner with grocery list built in? Here's how to pick an app where your week's plan and shopping list actually talk to each other.

Tools + comparisons

7 Sept 20268 min read

Shared shopping list apps — the best options for two people

Most shopping list apps sync fine. The differences show up in how they handle two people, recipes and the stuff you already own. Here's the honest rundown.

One short email a week. Recipes, plans, no spam.

Field notes, new posts, and the occasional half-finished thought — straight from the team building slrp.

Accept turns on replay and ad cookies (PostHog, Clarity, Meta, Google). Decline stays cookieless. details