Week 10

By

API Integration and Feature Progress

In Week 10 the main development focus was completing the Open Charge Map API integration and beginning work on the trip planner map feature.

Due to internet issues at my place this week, I worked from Tausif’s place for our main session with Aman joining online. This allowed development to continue without interruption despite the connectivity setback.

The Open Charge Map API is now fully integrated and returning live data in the Explorer screen. Public charging stations are populating correctly with distance values displaying for each result. The next stage of this feature is connecting the charger pin tap interaction to a detail view showing connector type, power output and availability information from the API response. This is currently being worked on.

On the trip planner side, the static range calculation is functioning as expected. The planned enhancement is rendering a map view after the trip summary is calculated, showing the origin, destination and any charging stop waypoints using the existing map component already in the codebase. This will give the trip planning feature a complete and demonstrable end to end flow for the Week 12 presentation.

Remote development continues throughout the week with additional sessions scheduled to maintain progress toward the final deadline.

Challenges

Internet outage disrupted the usual workflow early in the week. Resolved by relocating the development session.

Plan for Next Week

Complete tappable charger pin detail view, implement post trip summary map routing, continue addressing outstanding bugs and ensure the codebase is stable and up to date ahead of Week 11 class.

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