Team Status Report 2/15/25

The most significant risks for the project that we discovered during the design portion is how we are organizing and constructing the pressure sensors. Since the sensors are smaller, we want to ensure that an item placed on a portion of the pad is actually detected. In order to mitigate this, we plan to arrange the sensors in an array like formation to ensure equal distribution.

While thinking through our design, we also ran into the problem of the details on how our hardware will be able to interact with our software. We decided to specify our ESP32 to be a MCU with wifi capabilities so we can use that to communicate with the software backend.

No drastic updates have been made to the team schedule but our Gantt chart has added more detail and specifics on each person’s tasks. We also want to start testing MVP soon after Spring break.

For progress this week, we are finishing up the design and presentation of our product and trying to start rapid prototyping in order to get the basic functionalities of our product operating as well as finalizing the hardware components we choose to use.

Part A written by Sarah Yang

Our GlowFresh system contributes to public health, safety, and welfare by preventing spoilage and addressing waste. On the health perspective, our product ensures well-being by preventing people from eating expired or spoiled foods, particularly those with expiration dates that are hard to spot. Tracking the state of food in the fridge mitigates food born illnesses and ensures better nutrition management.

In regards to safety, the pad notifies users of expiration, which prevents health hazards. The use of silicon for our pad also reduces chances of external contamination.

Finally, in terms of welfare, our system aids in reducing food waste by raising awareness of expiration. On a large scale, it encourages sustainable food habits and reduces environmental impact caused by waste.

Part B written by Jessica Chan

GlowFresh addresses several social factors by tackling the widespread issue of food waste, which has significant economic and environmental consequences. Food waste is a major global problem, affecting households, restaurants, and food suppliers, with direct financial burdens and ethical concerns about resource distribution. By providing a system that enhances food management, GlowFresh encourages more responsible consumption habits and helps users reduce unnecessary waste and save money.

GlowFresh fosters shared responsibility in both household and communal settings. In multi-person households, such as families or shared apartments, GlowFresh can improve coordination by allowing members to track food items collaboratively, reducing redundant purchases and forgotten groceries. Similarly, in restaurants and community kitchens, GlowFresh supports better inventory management, which can contribute to cost savings and ensure food is used efficiently before it goes to waste. This is particularly relevant for food banks and donation centers, where maximizing food use is critical for addressing food insecurity.

The project also aligns with cultural and social movements that emphasize sustainability, mindful consumption, and technological solutions to everyday problems. By integrating mobile connectivity, GlowFresh supports modern, digitally connected lifestyles, making it easier for individuals and families to organize food storage collaboratively and reduce waste as a shared social responsibility.

Part C written by Gina Seo

GlowFresh is providing an economic recalibration of how households, businesses, and communities manage perishable goods. At its core, our solution addresses the financial losses associated with food waste, a multi-billion-dollar issue affecting individuals and industries alike. For the average household, where grocery expenses represent a significant portion of the budget, GlowFresh transforms passive consumption into active food management. By providing real-time visual and digital reminders of food freshness, it reduces the likelihood of impulse repurchases and unnecessary waste, stretching every dollar spent on perishable goods. This is particularly impactful in budget-conscious households, where maximizing food longevity can directly alleviate financial strain.

On a larger scale, GlowFresh has the potential to create economic ripples in the food industry, particularly in sectors where perishability dictates profitability. Restaurants, grocery stores, and communal kitchens operate on tight margins where spoilage directly cuts into profits. By integrating GlowFresh mats into storage systems, businesses can optimize inventory turnover, reduce shrinkage costs, and streamline purchasing decisions based on real-time food status rather than reactive estimations. But beyond individual businesses, GlowFresh aligns with the economic realities of large-scale food logistics where fresh produce, dairy, and meats move daily across borders in refrigerated trucks, through distribution centers, and into retail supply chains. In these systems, where timing is everything, even slight inefficiencies in expiration tracking can lead to tons of wasted food and lost revenue. By enabling smarter food monitoring at the consumer level, GlowFresh will help stabilize purchasing patterns and reducing strain on suppliers. In doing so, it indirectly supports a more efficient movement of fresh goods across supply chains, where every crate of produce and every gallon of milk reaches its intended destination before its value is lost.

Sarah’s Status Report for 2/15/25

This week, I focused on narrowing down the design scope specifics, particularly on the software side. I decided the exact frameworks and applications we would use to design our frontend and app backend logic. I am also going to be presenting the design slides in the following week so I spent a lot of time creating the presentation and deciding what type of content I want displayed. I created a block diagram of our software frameworks, hashed out a detailed Gantt chart with due dates and assignees, and started creating design choices for the frontend in Figma.

Our progress is currently on schedule as we are finishing up the design portion and will start development soon.

I want to be able to finish the design slides and give a good presentation that accurately goes over the details of our product. I also want to get all the software downloaded and setup so that it is ready to integrate with the hardware. I also want to start on the design paper that must be turned in the following weeks.

Gina’s Status Report for 2/8/25

This week, I focused on creating the Proposal Deck with my team. I refined the storytelling and flow of our presentation to ensure clarity and engagement, carefully structuring the slides to effectively communicate our project’s goals, requirements, and challenges. This meant delving deep into the root causes of the problem and identifying user pain points and drawing a direct connection to our proposed solution and the ways in which it can address them. Additionally, I practiced delivering the pitch to ensure a compelling and coherent narrative.

On the technical front, I conducted preliminary research to identify suitable hardware components, focusing on sensor accuracy, power efficiency, and feasibility within our design constraints. I am currently collecting components from the IDeATe Physical Computing Lab to build a mini MVP of our silicone pad. I plan to use an ESP32 microcontroller, a simple LED bulb, and pressure sensors to test the hardware and identify potential considerations before finalizing component selection.

Collaborating with team members, I dissected technical challenges, defined requirements, and strategized solutions. We addressed specific technical challenges and outlined requirements to ensure our solution is robust and effective. The positive feedback we received from peers and Professor Brumley well-reflected our efforts.

My progress is on track with the project schedule. Following the mini MVP testing, Jess and I will finalize a comprehensive list of components, ensuring each aligns with our system and performance goals. We will also incorporate feedback from Professor Brumley regarding our proposal presentation to refine our approach.

In the next week, I plan to finalize the list of components based on MVP testing outcomes, integrate Professor Brumley’s feedback into our project plan, and begin assembling the initial prototype with the selected components.

Jess’s Status Report for 2/8/25

This week, I contributed to our project by working on multiple aspects of both the presentation, refining our user flow, and coming up with possible solutions to address some of the technical concerns we had. For our proposal presentation, I helped design and structure the slides to ensure they effectively communicated our project’s goals, requirements, and challenges while also meeting the proposal guidelines. I carefully reviewed the content to make sure our ideas were presented clearly and concisely. Additionally, I worked on refining what to say on each slide, ensuring that every point was addressed logically and that our pitch was both compelling and easy to understand.

Beyond the presentation, I contributed to selecting and evaluating hardware components, researching various options that could meet our system requirements. My initial research focused on sensor accuracy, power efficiency, and feasibility within our design constraints. While I identified some promising options, I plan to take a deeper dive into these components in the coming days, assessing their tradeoffs and how they interact within the overall system rather than just as standalone parts. This will help ensure that our hardware choices align well with our system and performance goals.

Our progress is on track with the project schedule. By next week, I plan to have a comprehensive list of all necessary components, ensuring that each one meets our system requirements. I also plan to start thinking about how everything will come together for our design presentation, ensuring that we can effectively communicate our approach, technical decisions, and progress in a clear and structured manner. If given the time, I would like to outline the assembly of a barebones version of our project to test how all components interact once we are able to order them. This will help us identify potential integration challenges early on.

Team Status Report for 2/8/25

At this point in our project, the most significant risks in our project is the logical work of determining the expiration date of the food. Food decay varies widely depending on type and conditions, especially considering perishables and items without barcodes. The logic and algorithm for predicting the expiration is a big challenge of our project. In order to manage this risk, we are requiring the user to manually input expiration date for the item they are logging for our first working version or MVP. Once manual input is synchronized with LED pad colors, we will build on this to provide an expiration estimate based on product and fridge conditions.

No significant changes were made to our project this week. We simply outlined the technological design of different components in our project and how we want them to work together.

Sarah’s Status Report for 2/8/25

This week, I put in a lot of effort and time into our project proposal design and slides. Since I am on the software portion of the project, I researched different frameworks and databases we would be able to use in our application that would integrate seamlessly with the hardware and fit the needs of our mobile application. After consulting with my team mates about what type of hardware devices they wanted to use, I decided to use React Native for the app development, FastAPI for the backend and IoT communication, and Google Firebase for the database, cloud authorization, and notification system. Along with the proposal design, I also worked on the website setup. I set up the menu, pages, and categories that our team will subsequently use in the future to provide updates on our project. Finally, I worked on the Gantt chart schedule and distribution of tasks for our team. I outlined what each team member should do in Notion and set a general timeline for what to accomplish so we can stay on track as a team.

So far, my progress is on schedule. We finished up proposal presentations this week and I provided feedback for other teams.

In the next week, I hope to help my team decide what parts and materials we should order to start constructing our project. I also want to do more research on the software applications I will be using to build our web app, along with doing the setup for these frameworks.