Tausif - AS2 - Week 10 Blog: Feature Development and Presentation Preparation

By

Feature Development and Presentation Preparation

Week 10 was a solid week for the team. Despite Manzil dealing with internet issues at his place, we worked around it by having him come over to my place so we could work through the development together in person. Aman joined the session online. Getting everyone together like this made a real difference in terms of what we were able to get done.

On the development side we made good progress. The Open Charge Map API integration is now live and populating real public charging stations in the Explorer screen with distance indicators showing correctly. This is a direct response to Roshan's Week 9 feedback about needing real data in the app and it shows. The next step is making the individual pins tappable so users can see connector type and power level details when they tap a charger. That work is ongoing.

We also moved forward on the trip planner. The static range calculation is working and giving users results based on their inputs. The team identified the next enhancement which is adding a live map view after the trip summary showing the origin, destination and any suggested charging stops as waypoints along the route. This brings the trip planning much closer to what was outlined in the original proposal and will be a strong part of the Week 12 demo.

I also started building out the final pitch presentation this week, structuring it around all the assessment criteria including project background, features delivered, methodology, testing and roadmap. Having Manzil here in person meant I could also cross check the development progress directly against what we need to show in the presentation, which kept everything aligned.

Remote work continues across the team with hybrid in person and online sessions scheduled through Tuesday, Wednesday and Thursday this week. The focus for those sessions is completing the tappable charger pins, the map routing feature and pushing updates ahead of Week 11.


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