![]() add more veg, swap some ingredients, etc). If I must, I modify a recipe to satisfy dietary wants (i.e. How a recipe ends up on this list is one of us will try it out for a weekend dinner, and if it pleases both of us it's now part of the rotation. This is the compromise arrived to with my partner. We have a selection of "go-to" recipes that we choose from every week, based on what we feel like. But as others have said here, there probably will be a solution out there that will meet your needs. Then it will have all the features YOU want. So if you know how to code, you code probably just roll your own as I did. However, although the app does provide an accurate list of ingredients, it hinges on me updating the ingredients I have in my pantry and I don't typically do this as it is manual and too time consuming - It was neat to do an initial inventory of ingredients when I built the app, and the app does subtract ingredients out when used in meals for the week, but i no longer update the ingredients when I purchase from store each week. The app also will print out a weekly shopping list of ingredients based on meals selected, AND will take into account what ingredients I have on hand. ![]() I can search by cuisine, ingredients, score, and a few other bits of data. Each family member can choose one meal for the following week, or I can generate a random list for existing meals. It allows me to add recipes, photos, type of cuisine (italian, indian, etc), and allows each family member to score the meal from 1-10.Įach meal is then automatically kept in rotation or dropped based on the score (i can keep ones my wife and I especially like even if the kids don't). Rather than continue the constant battle of wills to get my oldest to eat what we cook, I built a family meal planner. My son is a picky eater and his younger brother, though he eats everything, will follow his lead during dinners. It's easier to build a robust workflow on a flexible substrate than on a brittle bespoke substrate like an app. You see, any app that replaced this would have to handle this specific workflow. It works as a substrate for a process rather than railroading the process itself. The flexibility of email is an advantage here. I can pull up the recipe on my phone in the kitchen and follow the recipe there, or again, pull the cookbook from the shelf. The reference system work great during cooking too. It's easy enough to go back and search for any old "menu" email as far back as we want and because everything is referenced by url or citation, we can add it to the next menu by navigating to the url or pulling the cookbook from the shelf. Sometimes we'll chain menu items like chili -> chili dogs or tritip -> sandwiches, but for the most part it's operates like a grab bag for the week. When we wish to make dinner, we reference the latest "menu" email and simply pick one of the items from the list. We then enter an order online for grocery pickup and stock the fridge. Then one of us drafts and email, referencing each recipe and the list of required ingredients, and finally sends it to both of us. ![]() My wife and I semi-asynchronously, find 3-4 recipes each and send each other links/(book,title,pg no) in chat.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |