Originally I started making this for my wife, but she decided to use another app instead so I figured I would finish it out and share it.
This base is designed to hold recipes and then use those recipes to schedule meals and create shopping lists using the IFTTT applet with the trigger “When a new record is created in view”.
It’s a great way to keep track of recipes you like. The meal planner uses a simple form view so that you can choose existing recipes and then the date on which you want to make them. The shopping list view takes what meals you have scheduled and looks up the ingredients. This view only shows what meals are within the next week, but if you shop more or less than once a week, you can adjust accordingly in the filter. While the shopping view shows the ingredients for each recipe, you can use IFTTT or Zapier to create a shopping list using ToDoIst or other listing app to create a compiled shopping list. This is especially useful since Airtable only supports Grid view on the Airtable app. It makes shopping a breeze. Then, at the end of each shopping trip, simply delete the list, and the process starts over, without any adjustment to Airtable.
Feel free to copy and customize the base to suit your needs as it’s built based on my preferences.
If you have any questions or suggestions on how to make this Base better, please reply or email me! I’m always open to questions or improvements!
Certainly! I agree the ingredients part is a little frustrating. I used a long text field, but I wish Aritable would come out with a List Field Type. That way the list can easily be parsed in Zapier to create lists in other apps. You can do that now, but it’s far too complicated. Anyway, I’m glad you found this helpful! Here’s the link:
I’d be interested in knowing WHY your wife didn’t want to use this - was it she didn’t know where to click? having to scroll vertically to access different fields? not understanding the ‘linked record’ concept?
I am constantly building bases for my family and colleagues, some worked well and some didn’t. I learned that although they ‘get’ the concepts it often requires too much mental effort for them to keep using the bases (forgetting how to get to that particular view, easier just to send a chat message to people than updating the records…)
Painful to see users abandoning these well designed bases…
@Y_K It’s a shame for sure, but I think for her it was just a complexity thing. She wanted to have a simple solution that she didn’t have to think about in the rush of the day, which I understand. I have fun designing bases anyway though so I’m not too hurt.
I definitely can relate with you though.