Personal Weekly Update | Carolyn | 3/22

Accomplishments

This week, I focused on enhancing the app’s onboarding and connectivity features. I implemented a new welcome screen with options to sign in and store the user’s data within the models. I also utilized @AppStorage for non-sensitive information and then plan to use SQLite to store the larger data for example data collected during the ride. I also developed a calibration page and flow that leads up to the calibration, collecting user weight, height, and device pairing data. Additionally, I improved the Bluetooth connectivity, displaying all available devices in a user-friendly list to help streamline the process of connecting to the ESP32 device. This involved refining the BluetoothManager to handle scanning, connecting, and disconnecting more intuitively and logs to provide feedback on any errors. These updates help to enhance the user experience and drive the progression of the app development forward.

In addition, I spent time this week looking into the ethical aspects of Cyclify and enjoyed the presentation I attended on Wednesday. The red teaming activity was very insightful and it was interesting to learn about another group’s project, challenge their stakeholder map, and brainstorm additional risks.

Progress Status

I’ve made good progress this week in implementing user flows from opening the app, calibration, and reaching the activity page. The next step requires connecting with the ESP32 and refining the calibration process, specifically implementing the calibration algorithms on the software side. In terms of integration, I am behind.

Next Steps

Next week, I plan to focus on integrating early on with the ESP32, especially given its the week before the interim demo. I also plan to focus on integrating more workout logging functionality to store ride data with SQLite. Additionally, I’ll enhance the calibration process by implementing a system that signals the ESP32 to collect data for the various poses.

Carolyn’s Status Report 3/22

Leave a Reply

Your email address will not be published. Required fields are marked *