| Thank you for the response! > support splitting ingredients by typing a comma That sounds sensible, yep; filed as https://github.com/openculinary/frontend/issues/210 > "Are there any ingredients that are not available?" ... I knew what you meant, the search will exclude recipes with those items, but it felt weird to read That makes sense too. If I remember correctly, that prompt was most-recently rephrased during a pandemic-related lockdown (with subsequent unpredictable ingredient shortages), and so that context may have affected the choice of wording; either way, I agree that it's odd phrasing and should be updated. Hopefully that'll be a relatively quick correction, although it will require internationalization (currently machine-translated without review by native language speakers, not ideal); it's filed as https://github.com/openculinary/internationalization/issues/... > box around the search form has a huge gap to the right of the form inputs > I'd probably expect to see filters for vegan/veggie/pescatarian / low gi etc but then maybe not Two good points here, and possibly combinable. Perhaps those dietary recipe filters could be placed in the excess space available next to the search controls. Today the search API does theoretically support filtering[1] on a few dietary properties -- but that functionality isn't yet visible and available to the user. Feature tracker filed as https://github.com/openculinary/frontend/issues/211 - Shopping list feature ... your icons seem too small and fiddly, and I'd want a few buttons on screen of common things - so I can tap those instead of typing The frequently-added-items shortcut idea is smart. The shopping list feature and the meal planner are under-attended components of the app relative to the recipe search/explore components, in my opinion. Let me think about this for a while, there are a few considerations and I'd like to be concise when responding about this in more detail. [1] - https://github.com/openculinary/api/blob/72075f66cd6fda5b809... |
All I'll say for now is that arguably the shopping list should become an important nexus within the app. Like an accounting entry-book with both order history and also yet-to-be-filled orders, it could be used to approximate the kitchen inventory at points-in-time. That should become powerful when changes in inventory are used to feed back into current and future meal planning.
Separately: advice noted about testing with friends and family. My partner and I use the app at home once or twice a week, and following recent improvements it's probably time to reach out for more feedback from others.
I find maintaining a balance between asking for (re)evaluation of the app and a hope for regular everyday conversations a little tricky; but to be honest I've always found the latter challenging, probably.