Tag: status report

This week, I made significant progress by developing a functioning prototype of our app based on the design presentation specifications. The app now has three key sections:

• A main page that displays real-time statistics collected from the IMU, providing users with immediate feedback on their movement data.
• A history and trends page that shows past performance, allowing users to review historical data and track improvements over time.
• A settings page, where users can set customizable thresholds for specific metrics (e.g., speed or stride efficiency) and receive alerts if they fall below the set limits.

I faced some challenges setting up the iOS simulator for testing, mainly due to issues with dependencies in my development environment, which delayed the testing by a few days. Despite these challenges, I was able to get the prototype working on an IOS simulator however android testing will require a little bit more time to ensure the app runs smoothly on both platforms.

Next Steps:

Going forward, my focus will shift toward data integration:

1. I plan to work closely with Vansh to receive the IMU data values via Bluetooth. This will involve using Flutter’s Bluetooth package to establish the connection and ensure smooth data transmission from the IMU to the app.
2. Once I receive the data, I will begin integrating it into the app, developing a system to analyse + present the information graphically to users in real-time.
3. I will also continue addressing the iOS simulator issues and aim to get the app running on both iOS and Android devices for a more robust testing process.

This week, I focused on the software architecture for our project’s app, carefully evaluating various software platforms in terms of usability, flexibility, and development efficiency. After considering the trade-offs between different technologies, I decided to use Flutter, a cross-platform framework, to build the app. This decision allows us to target both iOS and Android devices simultaneously, ensuring a wider user reach and optimizing the development process in terms of cost and time. Additionally, I laid out the structure of the app into three primary sections: one for viewing historical data and trends, another for displaying real-time data collected from the motion-sensing shoe sole, and a settings section for customizing user preferences. This architecture is designed to provide users with seamless access to essential features, improving their experience by offering an intuitive interface. With the software choice and structure finalized, I’m confident we are on schedule. My next step is to begin implementing the app in Flutter, setting up the basic layout and navigation between these sections.

No significant risks have been identified at this stage, but I will continue to monitor the development process for potential issues, particularly around cross-platform performance and ensuring the app remains intuitive and accessible to a broad audience.

This week, I helped Vansh rehearse for the project proposal presentation, which was successfully delivered. I also focused on the software architecture looking at how I can build an app to take data from our BLE module, and researching how to process IMU data for analyzing metrics like foot strike and stamina some of our use case metrics. The project proposal presentation was completed on time, and I’ve begun planning the software design for data processing. Next week, I will focus on data processing for the IMU sensor and begin initial test scripts, as well as support Vansh in selecting suitable hardware components. The main risk is ensuring the accuracy and frequency of IMU data. I plan to conduct testing and calibration to mitigate this.