This past week I finished implementing APIs in the web app backend which are called from the frontend to access the database to search and add recipes. I also created a “New Recipe” form to the UI which the user can fill out to upload a new recipe to the database and added routing between the web app home page and the page with this new recipe form. I also set up a local PostgreSQL database instance and wrote code in the web scrapers and the backend APIs to create tables and add and retrieve recipe data from a PostgreSQL database. I also worked with Alena to integrate the web app with the voice commands and audio output by setting up APIs and using a Python interface within Alena’s code. This integration allows Alena to send voice command data from the user, such as ingredients, to the web app, and the web app can access the database and relay recipe information to be used in audio output. Next week, I will set up the web app and the database hosted on a Raspberry Pi and finish up the search feature to display search results in the UI.
I will test the web app latency using Chrome DevTools, which collects data such as DNS lookup time, time to first byte, and frontend rendering time in Network, Performance, and Lighthouse categories. The measurements collected by Chrome DevTools will allow us to verify the web app latency requirement. Additionally, for the recipe recommendation requirement of 95% or more recipe recommendations consisting only of ingredients explicitly listed by the user, I will include unit tests for the recipe recommendation function. These tests will provide the recommendation function with a list of ingredients and a category and will sift through the recipe recommendations returned to verify this accuracy requirement.
