Advanced Studio 1 Group 1

 During Week 4, the project moved from early planning and concept definition into a more structured design and implementation stage. The main focus this week was to refine the core idea of VehicleGrid and make sure the app features were aligned with real EV user needs. The project scope was reviewed again to confirm that the application would not only help users locate charging stations, but also support route planning, charger visibility, and trip-related decision making. A major task completed this week was the further development of the application structure. The key modules of the system were identified more clearly, including user authentication, charger browsing, route planning, trip management, and preferences. This helped create a stronger understanding of how the pages and features should connect together. The user flow of the application was also considered more carefully so that the app could feel practical and easy to use for drivers. This week also included work on i...

This week we had our first mandatory checkpoint presentation. Manzil and I presented our frontend progress and received feedback from Roshan, particularly around focusing on phone-based features and leveraging native device capabilities. Following last week's news about Jayden leaving the team, I had begun task redistribution. During the checkpoint class, Jayden attended and we learned there had been a subject enrollment mixup. He is back on the team, requiring workflow readjustment. After the checkpoint, I focused on extracting specific requirements from our original proposal. I noticed some of our development work had diverged from what we committed to deliver. Team members also asked me to clarify the actual proposal requirements so everyone could understand what we need to build. I am systematically working through the entire proposal document, pulling out concrete requirements, technical specifications, and feature commitments. This involves reviewing each section to identify ...

 In Week 3, we focused on expanding functionality and demonstrating interactive features for the checkpoint presentation. The goal was to move beyond static UI and implement working logic across multiple screens. I worked on implementing the  Maps screen , including charger markers and a detailed information card displaying charger power, reliability, and status. I added interactive buttons such as “Confirm Working” and “Report Broken” to simulate community feedback mechanisms. I also built the  Add Community Charger screen , creating a structured form that allows users to input charger details such as name, location, reliability, and power output. I connected this to the in-memory state system so new chargers could be integrated into the network. Additionally, I improved shared state handling across screens to ensure consistency between the Home summary, Maps view, and user inputs from Settings. This week required more problem-solving than Week 2. Navigation logic, state...

Week 3 brought another shift in the team dynamic. Jayden's absence turned out to be the result of an enrolment mixup rather than a deliberate departure, and he rejoined the group this week. This meant another round of recalibration as we adjusted the task distribution again to bring him back into the workflow. It was a bit of back and forth in the early weeks but having the full team back together was a positive thing going into the checkpoint. The main event this week was the first checkpoint presentation with Roshan. I contributed to the frontend progress that was shown, providing suggestions and feedback on the UI direction as Manzil developed the core screens. Going into the presentation I had been given clearer roles within the team and was more actively involved in the frontend development side. Presenting what we had built in the first three weeks and getting direct feedback from Roshan was useful in understanding what the project needed to focus on going forward.

 In Week 3, I focused on fixing problems with my connection and communication to the rest of the group. The rest of the group worked on adding functionality to the static UI at the same time as fixing my communication. Since I was not able to access the project up until now so I am now spending time on getting familiar with the project through GitHub.

 Near the end of this week, I learned that Jayden would not be continuing with our team. I began the recalibration process, assessing how we would redistribute tasks and adjust our workflow. With Jayden's absence, I worked with Manzil to position him as the core developer. He stepped up to the challenge and showed real initiative, beginning development work on core features based on his understanding of the proposal. I also continued planning the Git repository setup to meet Roshan's tracking requirements.

Week 2 brought an unexpected change to the team. Jayden would not be continuing with the group which meant the remaining three of us had to recalibrate and redistribute responsibilities. Tausif led the restructuring process and I was assigned new roles within the project to help cover the workload going forward. It was a quick adjustment but the team handled it well and we moved on with a clearer picture of who was responsible for what. On the development side I worked with Manzil on UI ideas for the app, discussing the layout and visual direction for the key screens. Getting aligned on the interface early was useful so that development could move in a consistent direction. I also got my Git set up properly this week, making sure I had access to the repository and understood the workflow for pushing and pulling changes. Having version control in place from early on meant the team could collaborate on the codebase without stepping on each other.

 In Week 2, we focused on establishing a stable development foundation and moving from planning into structured implementation. The priority was to set up the Git repository correctly and begin building the core architecture of the application in preparation for the Week 3 checkpoint. I set up and configured the Git repository and ensured proper version control practices were followed. Once the repository was active, I began implementing the project structure using Expo Router. I removed the default template components and replaced them with our own application screens to align the project with our EV Trip Planner concept. I developed the initial versions of: The  Home screen , displaying EV system summary and vehicle information. The  Trip Planner screen , allowing users to input origin and destination details. The  Settings screen , including default safety reserve, efficiency input, and theme toggle. The tab navigation layout connecting all primary sections. We fo...

This week marked the beginning of Trimester 2 for Advanced Studio. I attended the first class where Roshan outlined the structure: weekly blogs, mandatory checkpoint presentations at weeks 3, 6, 9, and 12 requiring full team attendance, a prototype submission at week 6, and a final board presentation. The immediate priority is establishing a Git repository with Roshan added as a collaborator by Week 2 to track commits and development progress. After class, I organized a meeting with Manzil to explore development tools and review class overviews. We met at Manzil's place to test GitHub Copilot, Codex, and other AI-assisted coding tools to determine how they could accelerate our development workflow. We discussed using these tools for code generation before pushing to Git. I also discussed team management techniques with Roshan, focusing on non-verbal communication strategies and positive reinforcement approaches to improve team coordination. These tactics will help me assign clear t...

This week marked the start of Advanced Studio 2. I attended the first class where Roshan outlined the trimester structure including the checkpoint schedule at weeks 3, 6, 9 and 12, the prototype submission requirements and the expectations around weekly blogs and Git contributions. It was a good overview of what the trimester would involve and what was expected from each team member going forward. After class I worked with Tausif and Manzil to get set up on the project. We went over the tools and workflow we would be using for development, discussed the project direction and made sure everyone was aligned on what needed to happen in the early weeks. Getting set up properly in week one was important to make sure we could hit the ground running as development began in the coming weeks.

 This week I attended Advanced Studio 2 and learned about the trimester structure including checkpoint presentations at weeks 3, 6, 9, and 12, prototype submission requirements, and the need to set up a Git repository by Week 2 with Roshan added to monitor development progress. After class, I discussed project directions with Tausif and we organized a meeting to explore development acceleration tools. We met later that day to test GitHub Copilot and Codex. I worked on tuning Codex settings and checking its code generation capabilities to understand how it could support our workflow. We examined prompt handling and whether to integrate these tools directly into our Git workflow or use them for prototyping. I provided my availability schedule and work shift information to support project coordination. This information will help Tausif organize team meetings and establish regular collaboration sessions moving forward. This week established clear expectations for the trimester and intr...