georg
8
Hi @boston85719,
re changing number of servings. There are three possibilities:
- I usually pre-populate the servings with a standard number of servings for that user (stored in their profile). If the user then selects that recipe straight from the main page, I use that standard servings.
- If a user goes into the recipe page, changes the number of servings there and then adds the recipe to the menu, I use that recipe specific servings instead.
- The user is still able to adjust the number of servings at a later stage - in that case I run another API workflow on the list of shoppinglist items which updates the required quantities based on the updated servings number.
The app is usually meant for people to select meals at home and then go to the shop or fill their online basket. But we also see people who are more spontaneous shoppers, i.e. they select a recipe pretty much while they are at the store.
Lately I have thought about splitting the two processes of adding a recipe to the menu and creating the shopping list, currently I create all shoppinglist items as soon as the recipe is added to the menu all in one flow.
However, often we see people first creating a longlist of recipes and then cutting it down again to a short list of recipes. This usually goes in pretty quick succession and creating all the shoppinglist items along the way is really interrupting that experience. So now I think, maybe first let customers finalize their menu of recipes and once the selection has settled create the different shoppinglists and shoppinglist items.
What is your opinion for the best way to go about that?