Q2 2020 is now complete, and I’m glad to say that we managed to achieve almost all of the goals for the quarter. The only task that has rolled over into Q3 is the selection of a graph database technology, in order to support the knowledge-graph component. Spelling Suggestions During the last update I mentioned that we had discovered the fast-autocomplete software library as a candidate to provide spelling suggestions on RecipeRadar.
Recipe Detail Page To make better use of device screen space, clicking on a recipe now takes you to a full-screen ‘recipe detail page’ where everything needed for meal preparation is displayed on a single bookmarkable page. The page incorporates a number of aspects from Monica’s screen designs, including the ability for the user to hover-to-highlight recipe direction steps. Recipe Scaling If you’re eagle-eyed (or had been waiting for this feature) then you may have spotted that the ‘servings’ field on the recipe details page is an edit box.
Updated Website Prototypes One of the features of the screens that may involve the most complex user interactions and information presentation is the selection, display and navigation of planned meals (calendarization). Architecture Investments When you interact with RecipeRadar on your phone or on your computer, the information presented to you is served by our recipe search engine, which is based on the open source Elasticsearch product. We also use the popular open source PostgreSQL database to store persistent data: ingredients, recipes, our progress crawling the recipe web, and user search logs (which do not contain any personally-identifying information).
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
Progress on RecipeRadar over the previous fortnight has included improvements to our data processing infrastructure, continued refinement of our screen prototypes, and exploration of collaboration tools and technology selections. As you may have seen on the discussion list, Monica has been iterating on the screen designs for web and mobile, and in particular the prototype meal planner calendar is looking great. I’d like us all to spend a bit more time to make sure these designs are simple and usable.
The last two weeks have involved quality improvements, design prototyping, and preparatory work as we prepare to introduce more contributors to RecipeRadar. Have you experienced any ingredient shortages or price changes during the coronavirus pandemic? In future we hope that RecipeRadar will automatically offer information on local ingredient availability, seasonality, and pricing. This and other plans will be detailed in an upcoming roadmap document. Design Iteration As you may have seen on the mailing list, Monica has been preparing screens to provide an improved search experience in the application.
Progress on RecipeRadar has been ramping up over the past few days; here are some updates on recent developments. Homepage Updates Thanks to Susan and Liz, the homepage search controls have had a revamp: All three of the recipe search fields are now shown by default, and the wording has been simplified and improved to cater to people finding ingredients unavailable due to the COVID-19 crisis. User Experience Improvements While more work remains to improve ingredient search, incremental progress is being made.