Risks & Management:
Feature Prioritization
-
- Risk
- We may not be able to implement our full list of features such as AI meal recommendations or allergen substitutions
- Contingency Plan
- We are prioritizing our different features. The main functionality is cart tracking and item scanning. Then, we will prioritize allergen substitutions.
- Risk
MQTT Connection & Network Issues
-
- Risk
- Network instability may cause message loss / delays in product updates.
- Contingency Plan
- Implement retry mechanisms to resend messages in case of failures.
- If the network is unstable, store scanned product data locally on the mobile app & sync when online.
- Risk
Design Changes & Justification:
- Transition from Database to Open Food Facts API and Cache
- Originally we planned to build our own database of aldi foods and information. However, we recently found an API online that is able to access the aldi inventory and return a product through its UPC, which is the output of the barcode scanner. Therefore, instead of using memory and time to build this database, we will query for it during the shopping
- A concern of this is latency. Therefore, we want to use a cache to retrieve frequently used item in order to still meet our quantitative requirements.
Progress:
-
- Started integrating LangChain to process scanned grocery items, cross-check them with planned meals, and request substitutions when needed
- Created a schema to store scanned products, user dietary preferences, and updated meal plans, with basic CRUD for efficient data retrieval
- Implemented MQTT client in the mobile app