Update: from fridge photo to expiry date and recipes
BiteDown now reads food in three ways: a photo of the fridge, a typed or spoken list, and a receipt.
Photo enrichment: after the vision model detects each food, Gemini estimates its expiry date and its nutrition per 100 g. The server checks every number. Anything out of range becomes null, so one bad estimate never breaks adding food. Recipes around what you pick: /recipes/suggest now takes item_ids, so suggestions are built around the items about to expire. Receipt scanning that always works: if the OCR service is down or slow, the API falls back to Gemini vision. We also fixed a bug where a slow OCR call could push a request past our 120 s server limit. Independent QA: separate QA agents reviewed each change before it merged. They found issues (BE-19 to BE-22, BE-26 to BE-28), and we fixed them first.
Next up are the remaining iOS screens and a polished demo path: photo, expiry prediction, remove, Impact.
Add a screenshot of the photo-review screen showing expiry and nutrition. If you’d like a code snippet, the item_ids request on /recipes/suggest is a short, clear one.
Log in or sign up for Devpost to join the conversation.