Team Null pointers Present Track Travel Disruptions
present

Track Travel Disruptions Demo video

Track Travel Disruptions Demo video

Always Stay On Track

TTD is an app that helps commuters stay informed about incidents on their regular commute without having to look it up every time. Journeys which include time of departure and frequency (days) of travel can be saved. Commuters then can at a glance check the status of their train and plan accordingly.

We arrived at this idea as we all know the trains seem to always be delayed or changing platforms. When you have a season or weekly ticket you don't get notifications for repeat train journeys, we created this with the goal of being able to notify users about updates to platforms and times on their journey to help increase convenience.

The Team

  • This Student did not supply a photoPreview: This Student did not supply a photo

    Ahmed Mohamud

  • Jasmanjot RaiPreview: Jasmanjot Rai

    Jasmanjot Rai

  • Sunny LawPreview: Sunny Law

    Sunny Law

  • Elliot Grabowski-JavedPreview: Elliot Grabowski-Javed

    Elliot Grabowski-Javed

Technologies

Spring Boot, Java, Android, PostgreSQL, YouTrack, GithubPreview: Spring Boot, Java, Android, PostgreSQL, YouTrack, Github

We used: Spring Boot, Java, Android, PostgreSQL, YouTrack, Github

We decided on this stack due to the team's familiarity and comfort with these tools and technologies, which allowed us to work efficiently and effectively. YouTrack was chosen for its robust project management and issue tracking capabilities, enabling us to seamlessly track tasks, bugs, and feature requests while facilitating agile project management and team collaboration. GitHub served as our version control system, providing a reliable platform for source code management and collaboration. Java, known for its versatility and performance, was our primary programming language, while Spring Boot enabled us to create a stand-alone application quickly and with minimal configuration.

Challenges Faced

  • Extracting relevant information from the API because the API returned highly nested Json difficult to work with and map to front end.
  • Darwin API was our first choice but was down for development.
  • Dealing with merge conflicts when one change would break the other feature.
  • Not always keeping our kanban board updated/ using as much as we should be.