Posted on

Team Status Report for 04/26/2025

Risks & Management

  • Risk: Raspberry Pi connection to Hotspot. During our real-world testing at Aldi, we observed that scanned items were not properly passed to the app, even though the Raspberry Pi was connected to a hotspot. In contrast, the system worked reliably during testing at Entropy. This inconsistency suggests that the Pi’s network may vary depending on environmental factors such as hotspot stability.
  • Management: It is good that we are doing a demo on campus, where we have better control over network environments. While the app and backend will operate over a hotspot, the Raspberry Pi may still be configured to use the campus WiFi as a fallback if necessary. This ensures more reliable data transmission for the demo.

Design Changes & Justification:

  • Shifted to regular email login for iOS Simulator testing, while keeping Google OAuth for web access, to avoid additional Apple Developer fees and simplify testing. This allows to check both implemented signup/login page and Google OAuth are working correctly.

Progress:

  • Completed in-store testing at Entropy and Aldi for scanning, cart updating, and mobile app integration.

  • Completed main sections of the final design report
  • Discussed overall plan for demo as a group
Posted on

Lois’s Status Report for 04/26/2025

Work Accomplished:

This week, I worked on:

  • Conducted in-store testing sessions at Entropy and Aldi as a group to verify scanning performance, real-time updates, and user flow
  • Optimizing and debugging the mobile app
  • Writing the final design report

Progress Status:

The app now has all parts required for all actions. I still have to make improvements on manual input scanning page and allergen flagging page.

For the Google OAuth issue that I have been dealing with, I decided to use the regular login/signup page only for the iOS Simulator to avoid the $99 Apple Developer Program fee. On the web, Google OAuth remains supported for smoother user experience. On iOS Simulator, users will log in through the manual phone signup page that I implemented. I think this is good in that I am able to check both session works correctly.

Next Week’s Goal:

For next week, my focus will be on:

  • Finalize plan for our demo
  • Finalize testing for scanning accuracy, allergen detection, and cost tracking estimation
  • Complete final design report, poster, and video
  • Continue on improving the app
Posted on

Team’s Status Report for 04/19/2025

Risks & Management

  • Risk: Occasionally, the MQTT client loads multiple instances, which causes message collisions. As a result, some product search responses are not received properly in the mobile app.
  • Management: Adding safeguards to prevent multiple MQTT client connections.

Design Changes & Justification:

  • Improved shopping session handling:

    • Added a “Newly Added Items” section in the Shopping session page, allowing users to separately manage unexpected purchases.
  • Instead of removing the allergen flagged items, in case the user needs to buy those items, we modified so that it is still shown when related product is searched, but the product card color will flag the user.
  • Preparing for WiFi to Hotspot communication for portability enhancement.

Progress:

  • Integrated dynamic frontend to search and assign real product options through MQTT

  • Developed and integrated real-time barcode scanning to dynamically update shopping session
  • Created full communication structure from the device to MQTT to backend to the mobile app
Posted on

Lois’s Status Report for 04/19/2025

Work Accomplished:

This week, I worked on:

  • Finalized the selection UI:
    • After product search, users can now select one product for each ingredient.
    • Once a product is selected, other product cards are hidden, showing only the selected item with an orange highlight.
    • Implement swipe actions on selected products for change and delete
  • Started preparing for the final presentation

Progress Status:

The app is now able to search for specific products and go to start shopping page. Barcode scanned items do show on the app. There are some minor errors in storing the products saved. Also in shopping session page, I added a ‘Newly Added Items’ section for user to easily add items on site, but not just moving to in cart so that the user is aware of the items that were not planned ahead.

Next Week’s Goal:

For next week, my focus will be on:

  • Fix minor errors related to saving selected products persistently and google oauth for iOS simulator
  • Finalize shopping session UI
  • Finalize allergen flagging UI
Posted on

Lois’s Status Report for 04/12/2025

Work Accomplished:

This week, I worked on:

  • Continued implementing the shopping session flow, with most features complete except for MQTT integration.
  • Enhanced menu search and my menu functionalities:
    • Built a clickable ingredient list, allowing users to choose which items they want to generate a shopping list for.
    • Implemented the ability to assign specific products to menu items.
  • Integrated to send to backend the selected ingredients along with user profile data (allergens, preferences, and cuisines) for filtering and product matching
  • Met with the team to align the backend integration and finalize the MQTT structure

Progress Status:

The app is now able to request product options through sending the list of necessary ingredients for menu. The team will meet tomorrow to work on receiving the product options, and this will allow completion towards menu search and my menu pages, as well as progress in shopping session page.
I am still having issues with Google OAuth when opening the app with an iOS Simulator. This is a minor issue as I am able to open the app through web, though for visuals in the future demo, I would have to fix this.

Next Week’s Goal:

For next week, my focus will be on:

  • Complete the MQTT response handling to receive and display product options
  • Finalize selection UI to save chosen products per menu item
  • Implement shopping session transitions (scanning screen, shopping summary page to conclude the session)
Posted on

Lois’s Status Report for 03/29/2025

Work Accomplished:

This week, I implemented Google OAuth login using Expo’s AuthSession. I also make improvements to the Shopping List UI. It now cleanly separates drafts into liked/saved drafts. I removed the recents logic to streamline the experience and reduce confusion. I’ve also been refining the UI with the demo in mind, focusing on improving clarity and layout for a smoother presentation.

Progress Status:

I am on track. Our team will be meeting on Sunday to finalize demo preparation and align on next steps moving forward.

Next Week’s Goal:

For next week, my focus will be on improving the UI for product substitution when suggesting or swapping items in the cart.

Posted on

Team Status Report for 03/22/2025

Risks & Management:

NLP Integration Delay

  • Risk: The integration of the NLP-based allergen filtering is still in progress. While initial development has started, coordination is needed between team members to complete the logic and begin testing.
  • Management: Our team meeting is scheduled to align on integration tasks and finalize implementation. Progress is being tracked to ensure real-time testing can begin as soon as integration is complete.

Design Changes & Justification:

  • No design changes have been made

Progress:

    • Partially completed UI optimizations
    • Debugged and stabilized preference/allergen comparison logic in the product card UI.
    • Initial work on NLP-based filtering has started, focusing on extracting keywords from user inputs.

 

Posted on

Lois’s Status Report for 03/22/2025

Work Accomplished:

This week, I focused on optimizing the UI and debugging the allergen and preference based filtering system. I refined how flagged allergens and matched preferences are displayed in the app to improve clarity and user experience. I also began exploring the NLP-based allergy filtering logic.

Progress Status:

I am a bit behind on the progress. While Aanya and I haven’t yet met to fully integrate the system, we’ve laid the groundwork for detecting and comparing keywords from user inputs and product data. Testing for real-time allergen flagging is still pending, as it will depend on completing the NLP-based integration.

Next Week’s Goal:

For next week, my focus will be on:

  • Meet with Aanya to complete NLP-based allergy filtering integration
  • Begin real-time product testing to verify accurate allergen detection
  • Continue refining filtering accuracy using user-defined preferences and ingredient data
Posted on

Team Status Report for 03/15/2025

Risks & Management:

  • NLP-based Allergy Detection Accuracy
    • Risk
      • The NLP-based allergy detection may fail to accurately flag allergens due to variations in ingredient names, formatting inconsistencies, or missing data in product ingredient lists.
    • Risk management
      • Implement keyword based filtering as a baseline before integrating AI-driven NLP
      • Cross-check allergens with multiple data sources (Spoonacular, Open Food Facts API)
      • Display AI-identified allergens and preferences on the User Settings page, beneath the profile text input, where users describe their allergens and dietary habits in natural language, allowing users to review and confirm which items are correctly flagged as allergens or preferred products.
    • Contingency Plan
      • Allow users to manually confirm flagged items
      • Implement a highlighting feature for uncertain matches for additional user validation

Design Changes & Justification:

  • UI Enhancement for Allergy & Preference Filtering for clarification of product selection and improvements in user accessibility of managing allergens
    – Allergen flagged items now appear in red highlighted boxes for visibility
    – User preferred products based on dietary preferences are displayed in green highlighted boxes

Progress:

  • MQTT connection & data transmission
  • Ingredient Substitution & allergy filtering UI
  • Obtain product UPC value
  • Spoonacular API requests