Felipe’s Status report for 3/7/2026

As a reminder, this status report includes two weeks, starting from 2/21 and ending on 3/7.  Of course, the second week was Spring break and as per the TAs recommendation little work was done over that time.  In terms of the week prior to spring break, the majority of that time was spent on creating the design report document incorporating feedback received from the design presentation.  My contributions to that report, which can be found in the design review tab on this blog, was the sections regarding the companion application as well as a fair portion of the reports introduction, use case requirements, and high level overview.  Also in response to issues our team had in the design slides, I spent time learning how to ensure that images were correctly displayed when using overleaf to create the document.  I believe that myself and the team was able to create a readable report but I understand that I am still not experienced in overleaf and will likely make edits when adapting the design report to our final report.

 

In terms of work on the application I have created a list of tasks that will inform my development process, first prioritizing JSON editing and saving before moving to Bluetooth integration.  Hopefully the app will start to come together in the coming week and I will have a basic, if ugly UI by the time of my next status report.

Felipe Status Report for 2/21/2026

The main bulk of this weeks work was preparing for the design review presentation I gave on Monday and then incorporating feedback into the design review paper due in a weeks time.  This also represents the main deliverable that will be worked on in the coming week.

Despite spending most of my time this week focusing on the design presentation, I also was able to spend some time into setting up resources for the companion app.  I added my teammates to a GitHub repository that allows them to view and interact with the flutter/dart code that makes up the companion app.

In terms of scheduling I feel mostly on pace.  In the design review I included sketches of what the app UI will look like and have reviewed the material library to ensure that it is possible to build with the dart libraries I have selected for use.  Once the design review document is finished I feel comfortable in starting work building the application in full.

Team Status Report for 2/14/2026

This week, our team spent the majority of its time preparing for the design review presentation this coming week.  It was decided that Felipe will be giving this presentation, whose slides will be posted to the design review section once they are completed.

Those slides represent the main physical deliverables as we are still waiting for physical parts to arrive, meaning we have little hardware to show off.  This is well within our scheduled expectations, so this is not an indication that we are behind schedule.

While we do not have much physical work, all team members have been able to complete research into their aspects of the project, including many key design decisions like PCB design and software libraries, which puts us on track and in a solid position for the coming week.

As of now, we have made few changes to our design, but I predict that will change once we receive feedback from our design presentation and finalise our design review document.

With respect to public health, safety, and welfare, Remigochi will preserve users’ privacy by not uploading or sharing the schedules they programed in to any online servers.  The data will live on users’ devices locally, mostly likely solely on Remigochi’s micro SD card and the applications local files.  In addition the user has control of the name and description of the events they put in the schedule, meaning that they can control how much information is included in the schedule.  For example, a user could create an event called pain medication one as opposed to naming it ibuprofen if they don’t want it known in the schedule that they are taking ibuprofen.  We believe that this should provide sufficient security and privacy for most users as medical devices are generally trusted if they are proven to provide some benefit to the user even at the cost of some PII.  However, should feedback from the design review prove that additional methods are necessary, the team will look into encryption libraries that seek to protect the user uploaded schedules.

As for other physical aspects of health, we will make sure the Remigotchi undergoes thorough testing to minimise the risk of it reminding users to take a medication at the wrong time leading to a health accident.

Another thing that This project will need to balance in terms of health and psychological needs is how much motivation in the device is motivated through reward and how much is motivated through punishment of the digital pet.  In a nightmare scenario the user missing reminders will cause the pet to be sad which in turns makes the user feel worse and lead them to making even poorer health decisions as they feel bad for failing their “pet”.  Possible solutions are twofold.  First we can remove negative displays for missing reminders and hope that the positive displays will provide sufficient motivation, and secondly we can try and make sure that the negative displays are cartoony enough that while they trigger a users sense of guilt they don’t not actively worsen their mood.  Both methods have their advantages and disadvantages and it may be possible to survey potential users in the CMU community to determine which method would be more motivating without being damaging.

With consideration of societal factors, we will design our Remigochi character(s) to be almost universally cute such that the widest range of users are motivated to take care of this small digital creature.  Our device will be designed to consume no more power than necessary to function under mild to moderate daily use, when it comes to environmental and economic factors.

Parts A was in part written by Felipe and Delaynie, B, and C were written by Delaynie.

Felipe Status Report for 2/14/2026

The main focus of this week was getting ready for the design review presentation approaching next week.  I was selected to give the presentation so I spent a lot of my time this week taking a look at our slides in order to give a well rehearsed presentation.

In addition for the design review I made some decisions regarding what platform the companion app would use and how it would be organized.  The platform I decided on was Flutter, as it contains multiple BLE libraries that have received somewhat recent support which means that should some libraries fail I will have additional options in the Flutter space that will prevent me from having to delete all previous work.  Another advantage of flutter is that is is easy to integrate with vs code and naturally contains a material library with easy to use UI elements.  Unfortunately the dart language does contain some specifications that I will have to learn, but there are plenty of resources online that I can reference in the creation of the necessary app screens.

In terms of scheduling I feel that I am on pace for our current schedule.  Due to the design review I have largely finished my research and design decisions and will be ready to jump into app programming immediately after the presentation and feedback have been gathered.

Future deliverables for this week will be finishing the design review slides and creating the design review document.

Team Status Report for 2/7/2026

This week, our team spent most of Sunday preparing for the proposal presentation, a link to the slides created can be found in the proposal section of this website.  Slide drafting was done by Felipe, while Italia and Delaynie to keep the slides from being too text heavy as we wanted to make sure our presentation was engaging for an audience of college students at 10am.

 

Fortunately our presentation went well and we were able to properly explain our use case and reason that our product is viable when compared to a standard cell phone.  We did receive questions regarding the structure of our device and the companion app, so future presentations will likely seek to better explain our solution approach now that a solid use case has been established.  While at the time of writing this we have not received feedback from the peer review forms, we do plan on spending some time this week reviewing that in preparation of the design review presentation.

 

Post proposal presentation, as per our Gantt Chart we focused on part research in preparation for the release of the purchase form.  Unfortunately, due to other commitments in the team we were unable to collectively agree on parts to purchase before tonight, each member has given assurances that by Monday all members will have recommendations allowing for early purchase of initial materials to ensure that should issues arise we will have time to make a second order.

 

Currently no changes need to made to the initial design, but we are preparing backups should something occur during the ordering process.

Felipe’s Status Report for 2/7/2026

This week was overall another week of research and preparation before the purchase request form was released on Wednesday.  Work on Sunday was focused on finishing the proposal presentation slides, for which I provided rough drafts that were eventually altered by the rest of the team to make them less text heavy.  Since the schedule was only finalized on Sunday, it is somewhat early to tell if I am truly ahead or behind on finishing research.  By next week, I will hopefully have sufficient notes on integrating BLE (Bluetooth low energy) with desktop/android apps which will serve as the groundworks of our companion app that allows users to upload schedules.  Hopefully the team will also decide on a board so I can do additional research into what languages I will be using, as well as downloading necessary tools/libraries so I can write clean code in a manner that will be easy to share with teammates.  Overall I feel that we are in a good spot as we can probably finalize board decisions on Monday during lab time, which allows me to research on Tuesday night before reporting on Wednesday in lab before spending the rest of the week sketching designs for app interface.