Week 8

By

 Team Re-engagement and Bug Resolution

Week 8 marked an important shift in the project as the full team came back together following a period where development had been progressing primarily on my end. The focus this week moved from individual development to collaborative review, testing and planning.

Earlier in the week I continued refining the application, making updates across multiple screens and improving the overall cohesion of the three portal system. Key updates included improvements to the host booking management, admin trust and verification flows, and the addition of new screens including a help page, wishlist and host analytics. I also worked on the Stripe payment integration and Supabase backend functions to support the booking and payment lifecycle.

On Thursday evening the team met for an in depth session. I briefed Tausif and Aman on the current state of the build, walking through what had been completed and how the different parts of the system connected. During the session we established a shared workflow for remote testing and contributions, discussing safe ways to push commits and collaborate without disrupting the main build.

During the session a critical bug was identified where a notifications API change in Expo SDK 53 was causing a render crash on startup. I resolved this during the meeting by patching the notifications cleanup code in the root layout file, allowing the app to load correctly across all devices.

We also had an initial discussion about the Week 12 final presentation and pitch, beginning to think about what the app needs to demonstrate and how we will present VehicleGrid to the board.

Challenges

The main challenge this week was the notifications crash which was blocking the app from loading after account creation. Identifying the root cause as an SDK 53 breaking change and resolving it quickly during the team session was important for keeping the testing process on track.


Comments

Post a Comment

Popular posts from this blog

Week 3 Blog: Individual Contributions

By
 This week I suggested that we build a web-based application, since it would be easier to present and maintain . I also shared my screen to walk my team through serveral of my past project s, includes a Movie Review Web App , an Advanced Web Project , a Shooter Game and a Task/Calender App . These demonstrations highlight my technical ability acrosss both web and game development and based on this the team suggrested that I would be the most suitable choice to take on the role of main developer for the project. Beyond my project showcases, I also supported our collaboration setup by creating a Discord server so the team could share updates and stay connected outside formal meetings.
Read more

Week 3 Blog: Individual Contributions

By
Tausif Rahman This week I presented the  Audit App  concept with its two parts:  Order Audit (OrderAuditPro)  and  Walkthrough Auditor . I later uploaded documentation and demonstration files of an Android version of the Order Audit module, which helped the team understand the concept more clearly. In addition, I encouraged the team to think about their  past subject projects  by asking what they had worked on in Android, iOS, cross-platform, and project management courses, to see if those experiences could be adapted into our current project. Alongside that, I shared several of my own past coursework projects, such as  ScholarSwap  (resource and book exchange platform),  SurvivAway  (a budgeting and life-flow helper), and  FocusFlow  (a study planner with ADHD-focused features). I also raised the issue of  legal risks  in some ideas, such as consumer liability in a Parking App or data security concerns in a Pass...
Read more

Week 5 Blog: Individual Contributions

By
  participated in the voting process and initially leaned toward the Audit App, but after deeper discussions, I found the Customer Service Checker and Vehicle Manager ideas more scalable and innovative. I located an academic paper titled E-Charge, which described an EV-charging-station planning system using open data and efficiency modelling. I shared the paper with the group and led a discussion on how its methods could guide our approach—particularly its use of driver-collected data, efficiency mapping, and route-planning optimisation. I also helped analyse how to simplify our version for Trimester 1, keeping it practical while leaving room for AI integration later. Additionally, I began finding and reviewing more EV-planning research papers to contribute to our shared knowledge base.
Read more