Jahnvi’s Status Report for 4/25/26

This week I focused on more backend development and full system integration as well as software testing. I worked on connecting the app with the backend device side flow so that schedule data, compartment assignments and device configurations can be transmitted correctly between the app and the esp32. We also began testing the system as an integrated app-backend-device pipeline.

For the software unit testing, i tested schedule management, compartment assignment, next-dose display, HTTPS communication and dose state logging. The completed tests so far show a 100% accuracy and I am planning to do the next set of tests this week like offline behavior, reconnection sync, and error notification. These are the last tests to do for software and depend more on full hardware software integration as well as end to end testing.

From the testing, one key finding was that the backend to device communication should stay minimal and structured so that the ESP32 receives only the configuration data it needs. Another finding was that the app logs and streaks should updated based on dose events and not just scheduled reminders. Based on this, i changed the design to separate scheduled dose display, confirmed dose logging and error state reporting. One difficulty we faced during integration was connecting ESP32 to Wifi. Since our school wifi uses individual login credentials and is not straightforward for embedded design connection, we had a lot of trouble getting a stable connection. To work around this, we tested our system using a personal hotspot so ESP32 and app could work on the same network with same name and password. This helped us continue integration testing and verify communication flow.

We have also decided to keep offline behvaior as a separate test category since the pillbox must support local reminders and scheduled dispensing even when the app is not synced.

Given that we have a week left till our final presentation, we need to focus the next couple days on thorough testing as well as human testing. We should be done in time if we keep up with out gantt chart.

Jahnvi’s Status Report for 4/18/26

This week I finalized the software architecture for the Magic Pillbox by working through various aspects of the backend design step by step. First I identified the core system requirements like structured medication and schedule data, reliable read and write operations between app and device a secure storage for our data, and a clean method to communicate with the ESP32.

Based on these requirements, I chose a relational SQL database because our system depends on strongly connected data such as users, devices, medications, schedules, and dose logs. After this, I compared various relational options and selected PostgreSQL as the best for due to its strong support for relational queries, data integrity and future adherence analytics. After this, I chose Supabase as a PostgreSQL platform because it provides authentication and secure user level access which aligns well with our Magic Pillbox requirements. After this, I finalized hybrid communication architecture in which the web app interacts with Supabase for user-facing data while the ESP32 connects over the Wifi using HTTPS requests to backend Route Handlers which then eventually reads from and writes to Supabase.

To make these design decisions, I had to learn and deep dive into backend system architecture, mainly the differences in databases, how webapps communicate with embedded hardware like ESP32 and I had to learn more about tools and concepts. To build this understanding, I used a mix of learning strategies rather than just using one website. I read some official documentation for the relevant platforms, which ones the industry prefers and uses and compared technical features as well as tradeoffs across options. This entire process helped me move from a broad understanding of possible software architectures to a more concrete and justified system design project.

I am a little behind schedule, I aim to finish most of the integration in the next 2 days so we can start testing. In terms of the overall schedule, I think we are on track for the final presentation, and we aim to start testing this week and complete all testing by mid next week, giving us enough time to write the report.

Jahnvi’s Status Report 4/4/26

This is week I just focused on fixing the app and making it ready for the interim demo. Most of the work went into improving stability and making sure the core workflows were in place. I also made sure they were smooth transitions between pages, and that time based features were correctly synced.

As we move into verification and validation, I mainly plan to test the app by running feature based tests for each of the major screen and user flow. This would include checking whether the medication setup saves and displays correctly, whether the Home page shows the right upcoming dose and countdown values, whether the logs appear with the correct status and whether the app handles issues like missing data or any other kind of errors. I will analyse the results by comparing the app’s actual output to the expected behavior for each requirement and noting which tests pass. This will also allow me to reveal bugs or any missing functionality. I will also test for structured test cases like expected user actions as well as edge cases. All in all, it will help show whether my software contribution meets the engineering and use-case requirements for reliability, clarity, and safe medication management support.

At the validation level, the app will be considered as part of the entire Magic Pillbox workflow rather than just an isolated sub-system. The key question here is whether the app supports our overall usecase of helping an older adult or caregiver safely manage medications. To evaluate this, we will look at whether the app makes it easy to set up medications, review the next scheduled dose and understand logs in a way that matches the goals for our project.

Currently, in terms of the schedule we are on track with the app. The only thing left is to integrate it with the software. I am currently researching methods that would be most ideal for such a system and will implement them by next week.

In terms of the overall schedule, we are slightly behind on the mechanical parts but should be caught up and ready by end of next week.

Jahnvi’s Status Report for 3/28/26

This week I built the frontend of the Magic Pillbox web app and made significant progress on the main user flow. I implemented the core pages including landing page, home dashboard, setup page, setup guide, logs page, signup age and login page along with a shared navigation bar to connect them all together. The setup page allows the user to add, edit, delete and clear medications while enforcing valid compartment assignments. The assignments make sure that caregivers/anyone filling up the pillbox can only assign pills to compartments 1 to 7 and prevent duplicate compartment use. The guide page includes the full step by step loading instructions for the pillbox. The home dashboard currently shows

  1. device status
  2. next dose
  3. countdown
  4. reminder information
  5. streaks
  6. refill alerts
  7. compartment status
  8. configured medications.

I also added a calendar style logs page with date-based summaries and detailed adherence records as stated by our use case requirements. I also added in app reminder banner and notification support.

There were some issues that i came across with time formatting, mock data consistency, page routing but was able to solve the after thorough debugging. Overall, the main frontend structure of the app is now built. This is on schedule with what our group had originally planned for our interim demo.

The goal for the coming weeks is to correctly integrate the software system with hardware and backend logic.

 

Jahnvi’s Status Report for 3/21/26

This week after the ethics lecture and red teaming discussion, our team reflected on an important risk in our design. One major issue we realised is that if a caretaker enters the medication schedule or plls incorrectly, it could create serious health hazards for the user. To solve this problem, we decided that the app should include a feature where the prescribing doctor can review or verify the entered schedule before it the pill dispenser starts dispensing. This is something I plan to add on to the software design. On the software side, I have been spending time learning Typescript and practicing it before fully starting the app development. I have completed the initial set up and now preparing to build out the core app parts.

I aim to finish the basic features by the end of the week so that the software part is ready for the interim demo. Overall, in terms of the timeline, it is looking fine.

As a team, we aim to finish the hardware and software separately and integrate it post the interim demo.

Jahnvi’s Status Report for 3/14

This week  I focused on planning the software side of our project which is the app for the system. I relooked at the main features we need the app to support namely medication setup, scheduling, reminders, dose logging and displaying the next scheduled dose. A major part of this week was comparing the different languages and framework options for the app. Initially, I was considering using Flutter. However, after weighing development speed and ease of use as well as what would fit our capstone timeline best, I decided that Typescript with React Native and Expo is the best choice for our project. This kind of stack would allow the app to support cross-platform development and do all the things it need to be able to do.

I also planned the order in which the app is built so that I can focus on the features that are most important. I created a personal schedule in order to stay on track for the interim demo. I also outlined the MVP around the core workflow which is medication setup, home screen, next dose display, reminders and dose logging.

Based on this, the first thing I will start building is the basic app structure. I will begin setting up the project on VS Code, creating the main screen skeletons and building the medication setup flow.

In terms of the overall schedule, I think there is enough time for our team to build all individual components as assigned in order to have something concrete for the demo.

Jahnvi’s Status Report for 3/7/2026

This week I worked on feedback based on our design presentation. We were asked to think of better ways to connect the pillbox and phone as well as look into more edge cases. The biggest change that we made to our design was switching from Bluetooth to home wifi using a REST API on the ESP32. I thought this change would be more straightforward and reliable for communication. Along with this, I also clarified online vs offline mode behavior. In online mode the app and pillbox stay synchronized with schedules and logging. In offline mode, the device continues to operate using a cached schedule and on device LEDs and buzzers. This allows dosing to be supported even when there is loss in connectivity.

Additionally, for multi-med doses, the device dispenses them into a single tray. If an error occurs, the entire dose is retried to avoid confusion. This was another edge case consideration.

We are a little behind schedule as we needed to already have the parts to build the box as well as have the app in the works. I think post spring break, we will use the week to catch up with our timeline and be on track in the coming weeks.

Jahnvi’s Status Report 02/21

This week I designed the full app layout and created visuals for the design presentation. The app flows like: sign-up/login to guided medication set up to homepage showing next dose and quick status. The app also has a logs and calendar feature to review taken vs pending doses and adherence history. Added a lightweight motivation progress tracking feature and defined notification behavior. Additionally, I identified some key risks with our system and mitigations for them. This touched upon multiple pills dropping at the same time, no pills dropping due to low pill count and weight sensor drift. Also, I refined our key user use cases and distilled them into 5 clear, testable use case requirements that the pill box must support. Lastly, I presented our updated design in the capstone design presentation.

We are slightly behind schedule because our design plan changed a lot over the past few weeks. This next week, our priority is to finalize and lock the design so we can start ordering parts and building immediately. I am aiming to begin app development soon, while we can catch up on the items we are behind on. We definitely need to get back on schedule so tasks dont pile up later

Team Status Report for 02/13/2026

Overall Progress Update:

Our significant risks remain pretty much the same as last week, though another has been added since: we are concerned with how to handle when there are only a small handful number of pills left and if our program will be able to account for that when letting multiple pills fall. Our idea right now to handle that is to add funnels to our overall design that allows for pills to flow down regardless of orientation. Now, another risk this may have is that our sizing of the pillbox may increase significantly. We plan on first sticking with this initial prototype to have a working design first then adjust afterwards as needed.

The system has changed in the sense that we no longer have motors controlling the opening of the pillboxes, rather to allow for a better offline functionality, it will be handled through a simple lever or button system so that it’s still accessible and easier to use than normal pillboxes but without the additional wireless electrical motor system that can cause more issues than necessary. We are also adding funnels to make a better guarantee of the last remaining pills falling when we don’t have many pills left in the compartment.

Our schedule remains the same as a whole.

Additional Individual Team Update:

Part A written by Carolyn Alex:

Our smart pill box promotes public health, safety, and well-being by improving medication adherence for individuals with limited dexterity and cognitive decline, especially memory issues.  Most existing pill organizers require opening small containers, which is difficult for users with shaky hands.  Which is why our pill box will have push to open compartments, which is easier to do mechanically.  Next, most products on the market to help keep track of dosages are apps that require a user to confirm doses in an app, which becomes unhelpful with incorrect logging. Our devices will confirm doses automatically when pills are physically removed using a weight sensor.  Additionally, by dispensing medications automatically at set times, our product reduces the work needed by the user to ensure they are taking their medications on time, hence increasing the likelyhood if taking them even when the user is tired.

Overall, our product in reducing unintended and missed dosages.  From a welfare perspective, the design supports independent living forthe elderly, especially those with memory and mobility limitations.  By lowering burden and increasing reliability of routines, our product supports phisyocal well being and confidence in managing medications.

Part B written by Jahnvi Shah:

Our product is a smart pillbox designed to support aging-in-place for community dwelling older adults (65+). It helps by reducing the day-today dependence on others for medication management. By making the pill dosing more automatic and keeping the core workflow usable, the system allows users to maintain their independence and autonomy in their routines. This is especially important socially because it shifts it helps older adults handle their medicines on their own, instead of relying on a caregiver or a family member.

Our design also aims to reduce the stress and conflict in family and caregiver relationships. Taking medication often creates tension with repeated reminders that feel like nagging. Additionally, there is uncertainty about whether a dose was taken which can lead to misunderstandings or guilt. Our product has clear dose status like taken vs pending or missed which provides clarity and reduces the need for constant checking. This makes support feel less intrusive and more respectful. Further, the product is intended to be equitable across living situations. It works for older adults living alone or in multi-generational households or with rotating caregivers because the essential functions do not rely on someone being present. Lastly, as an added benefit, features like reminders and a simple streak can give user a bit of daily structure and motivation.

Part C Written by Jieun Lim:

The smart pillboxes that we have found online that have similar functionalities are priced on average around $150. As a note, this is also without all the features we plan on implementing. As a whole, in the current economy, this might be too high-priced for households who are reliant on healthcare, especially for the elderly. That’s why our design focuses first on laser cutting with cheaper but still durable acrylic as well as minimizing the number of microcontrollers. The biggest reasoning for removing the FPGA and replacing with the ESP32 is also due to the cost: an arduino ESP32 costs on average around twenty dollars while the FPGA which we wanted to use for the original design is over a hundred dollars. To make it more accessible during the production, there is necessity for using cheaper components that simply require extra logic.

There is also consideration for the distribution of this items: we wanted to make a more compact design than in previous iterations, keeping it close to the already available and smaller-sized counterparts while also incorporating it with greater functionality. This would allow for to be distributed at once, reducing transportation costs overall. Additionally, this would allow for more to be consumed/sold in stores on the shelves too, with again the lower price making it more affordable as a whole. Overall, we hope to have this device be the size of a portable coffee machine at most at half or more than half the cost. This would raise consumption as well as distribution to match the consumption levels.

Jahnvi’s Status Report for 02/14

This week I focused on making the dispensing mechanism more reliable by doing research about pill-dimension data. I looked at capsule size specification charts from LFA Capsule Fillers and Capsuline. From this, I got the standard external diameters for common capsule sizes. I also references FDA guidance on pill shape/size considerations. Using this, our team decided to design our pillbox such that the stepper motor supports a small set of discrete gate-opening positions mapped to the common capsule sizes.

Additionally, I defined the MVP app concept at the UI level so we can have the software scope directly tied to the device workflow. The app starts with a simple signup/log in page, scheduling that maps pill types to compartments and dispense times, a step by step filling guide, dose logs with a calendar view for taken vs pending and a streak feature to encourage use of the product. I also created a visual depiction of this to make the requirements concrete and reviewable. This provides a direct blueprint of how our app would look and function.

I also helped make the design proposal presentation in terms of defining our use case more deeply and then basing our user requirements based on that.

Status: on schedule. The app coding needs to begin this week to avoid falling behind. The only reason we have been holding off is because a few design details have not been finalized yet. We plan to lock these down early this week and start implementation right after.