Week 6

By

 During Week 6, we focused more on the practical side of the system and how the application features would function together. At this stage, the project moved beyond only planning and design thinking, and we started reviewing the logic behind each major page and feature more critically.

A key task this week was evaluating the purpose of the main screens in the application. We reviewed whether each page had a clear role in the user journey and whether it supported the main purpose of VehicleGrid. This helped us identify areas where some sections looked acceptable visually but still lacked meaningful functionality. We discussed how dashboard-style pages, charger views, and trip-related screens should provide useful information instead of acting as placeholders.

We also continued refining the data structure of the application. More attention was given to how chargers, trips, vehicles, and user profile data should connect with each other. This was important because the application needs to support both exploration and route-planning features in a way that feels practical and organised. We considered how data would be retrieved, displayed, and updated to make the system more useful for EV users.

Another important area this week was reviewing the project from a user perspective. We discussed whether the app was truly helping users solve a real problem or whether some parts of the app still needed stronger logic and clearer purpose. This led to more consideration of route feasibility, charger relevance, and the overall usefulness of each section of the app.

In addition, we began thinking more carefully about testing and quality review. Instead of only focusing on adding more features, we started identifying possible logic gaps, weak workflows, and places where the app experience might not make sense. This helped improve the overall direction of the project and made the app feel more grounded as a practical solution.

Overall, Week 6 was an important refinement stage. We improved the internal logic of the project, reviewed weak points in the current design, and made stronger connections between the frontend and backend structure of the app.

Challenges
One challenge this week was realising that some features looked complete visually but were still weak in terms of logic. Another challenge was keeping the project structure simple while also planning more advanced functionality.

Plan for Next Week
Next week, we plan to continue refining the application, improve integration between key features, and make the project feel more complete and coherent as a working EV app concept.

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