-
Title
-
Road Trip Stats
-
Map and Stops
Inspiration
You’ve heard of study breaks, work breaks, breaks from stress, breaks from life, etc… What about breaks from driving? Some of us recently took a road trip during Spring break around Texas. On the first drive between cities, we did not take a break and did it in one go. Around when we got to the second city, we started to regret not taking a break as we needed a stretch and rest. We wanted to create a car application to help users have a great road trip experience!
What it does
Our application adds breaks to a user's road trip plans. The user would enter their starting point and destination on the top, and select either ‘Gas Station’, ‘Restaurant’, or ‘Coffee Shop’ for the breaks. The application then displays the map of the route and opens a Google maps link to provide directions to those locations. By using this, the driver gets to take a break and the passengers can stretch their legs.
This application also provides your trip statistics (total distance and total duration), and the potential stops listed at the bottom.
How we built it
We built our application using HTML, CSS (with Bootstrap), and Javascript. We used the Google Maps API for all the directions and stops calculating and displaying.
Challenges we ran into
When using the Google Maps API, we ran into issues with promises. The API didn't support await/async syntax which we needed to get the result of the requests. We ended up implementing functions to wrap the API calls in promises which helped clean up the code.
Accomplishments that we're proud of
We found solutions to a problem that we faced while on a road trip.
What we learned
We were able to apply what we learned in class to this project. Some of us took CS6314 and learned how to use Bootstrap. We took this knowledge and used the React version of it.
What's next for RoadTripHelper
We could implement multiple drivers on the dashboard so people can split driving. The drivers could enter any of their customizations and preferences and a path would be decided based on that. We could also find roadside attractions for users. If they're interested in circuses for example and will drive by one, we could recommend it to them.
We could also add stops for gas based on how much is left and the price of gas. On our road trip, we noticed Austin had cheaper gas than San Antonio so we waited till we got there to fill in gas but it was very manual as we had to use GasBuddy rather than it being integrated into the car.
Log in or sign up for Devpost to join the conversation.