The last two weeks have included improvements to our ingredient search engine suggestions, meal planning improvements, and proposal of a product roadmap. We’d love feedback on these, and the roadmap in particular!

We made incremental progress on our internationalization processes (by trialing use of an application called poedit), but the process still involves some friction.

Support for viewing historic meal calendar entries remains on the near-term task list.

Partial Ingredient Name Suggestions

When you start typing ’tomato’ on RecipeRadar, the search engine will scan for suggestions across recipes that contain matching ingredient text, such as 1 tomato or two tomatoes (i.e. both plural and singular forms).

In this example, RecipeRadar suggests the plural name ’tomatoes’ to you, because the plural text appears more often in the recipe set than the singular form ’tomato'.

Until recently, these suggestions would only include ingredients where your input is a strict prefix of the ingredient name. So you might be offered “tomatoes” and “tomato sauce” as selections, but you would not be prompted with “cherry tomatoes” as an ingredient to search for.

This limitation (as reported a little over a month ago) has now been removed, making it easier to search for all kinds of ingredients and ingredient variants.

Have you encountered any problems finding ingredients or recipes on RecipeRadar? Let us know via the ‘Feedback’ button or by filing a GitHub issue and we’ll take a look.

Meal Planner Messaging

Some small changes have been applied to meal planning in the application this week.

While users can still create a shopping list without planning any meals, the ‘suggested action’ for each recipe search result now leads them towards meal planning rather than shopping list creation:

This aligns with our idea that users can save time, eat more healthily, and reduce food wastage by planning ahead for multiple meals.

To further attract users towards meal planning and to inform them about the state of their meal calendar, we have added a visual cue with the number of entries in the meal planner:

These small features will become increasingly valuable after we re-enable multi-device and multi-user session sharing.

Allowing family members and friends to view the state of meal planning and shopping at-a-glance, and providing access to the shopping list you created at home on your desktop computer while out with your smartphone are two of the cases we are considering.

Product Roadmap

Progress on RecipeRadar over the next few months should be methodical and sustainable; we have a large number of product goals, and while we can’t achieve them all instantly, we can arrange them thoughtfully so that we gradually deliver application improvements for users while retaining high quality and ensuring that our code remains easy to modify and extend, allowing us to reach our longer-term goals eventually.

To more easily communicate what those product goals are, and in what order we currently plan to implement them, we have drafted a RecipeRadar Product Roadmap. Please take a look and provide your feedback here or on the GitHub pull request.

Coming up next

As you’ll see on the roadmap, there are a number of architectural investments that we believe make sense to apply during the remainder of Q2 2020 (Apr to Jun 2020).

It’s likely that these will compose the bulk of our engineering work over the next two weeks; we may also take the opportunity to look into improving company transparency via OpenCollective and perhaps by increasing the external visibility of internal mailing lists.

As mentioned previously, adding the ability to view historic meal calendar entries in the application also remains on the near-term todo-list.