Inspired by the need for a way to keep up with our hectic schedules, we decided to create a tool to help plan for the distances between meetings and classes.

What it does

We would like to introduce: nav.igate, as a webapp tailored to the needs of stressed out students. By using Google Calendar’s API, we can import user calendars and plan out the next week accordingly, accounting for meetings, classes, travel times, mode of transportation, and distance. Our smart backend optimizes the user’s week, and our crisp user interface cuts through complexity and allows our users to focus on what’s important.

How I built it

Our backend is built and deployed in Google Cloud with Python Flask. We’ve hooked up a Firebase server to handle flexible data loads, and we’ve built from scratch a front end UI to match each user’s dynamic lifestyle. We also deployed with both Google calendar and Google map APIs, which enable us to provide interesting user stories.

Challenges I ran into

The project ran into several challenges: deploying onto Google Cloud Platform, passing data from the front end to the back end and vice versa, working with several APIs that grew increasingly more complex as we realized the deceptive scope of our project. Putting together the individual bits and pieces grew more complex as we moved on, and we were forced to make tradeoffs between functionality and presentability. The tall task of weaving numerous APIs together became a formidable hurdle.

Accomplishments that I'm proud of

Overall, our team has been mostly successful in deploying nav.igate on Flask and GCP. Additionally, our team was able to establish secure Google authentication along with a clean user interface. The frontend and backends both maintained their integrity. Our team is most proud of how we were collectively able to collaborate with a pressing time limit of 36 hours. In this time, we were able to develop a prototype for nav.igate that demonstrates key functionality.

What I learned

Nonetheless, we’re proud of what we’ve learned along the way. We absorbed the advice of our talented mentors, resolved ourselves to seeing the project through to the end, and gained valuable insight into the rough nature of software/product development. The developers of nav.igate have grown a lot in 36 hours and have no plan to stop. From a technical standpoint, we were able to learn aspects and concepts of:

  • Google Calendar, Distance Matrix and Maps API Integration
  • Flask
  • Firebase
  • GCP
  • Frontend and Backend interactions

What's next for nav.igate

We foresee nav.igate to be adopted by students all across North America, enabling a myriad of possibilities. We have plans for future integration with Google APIs including reminders, messaging, analytics, mobile support, social networking and more. We envision nav.igate as the premier time management app, becoming a common fabric in society.

Share this project: