Inspiration
Velocity was inspired by a desire to make cycling an efficient and viable option for everyone everywhere. Based off of experience as students at Texas A&M, we believed that improved access to bike routes and locations would provide incentive for students to make the switch to biking.
What it does
Velocity make bike sharing more accessible. It’s a website that could serve as a standalone app or be integrated into Google Maps or Veoride.
Velocity helps users (specifically mobility sharing users) optimize their travel time, travel costs and eco-friendliness by suggesting fully routed biking navigation as a alternative to driving. It tackles pitfalls of popular mapping and bike sharing apps by providing complete navigation to users from their location to the nearest bike to their destination, including time and cost information.
How we built it
Backend: Velocity uses two APIs primarily: Google Maps API for routing and navigation, and VeoRide API for bike locations and statuses. We have a Flask server which contacts the VeoRide APIs and encapsulates it in endpoints optimized for our needs. This also helps us forego CORS measures that would apply if we tried to directly called the VeoRide API from our frontend.
The website and the API is all served from the same domain and port. Different calls are routed through an nginx reverse proxy, which routes API calls to the docker container running the server.
Frontend: Our website is built using HTML, CSS & Vanilla JS.
Dev Infrastructure: We used Google Cloud's Compute Engine as our server. All our services run in docker containers (specified in a docker-compose.yml file), which makes development and future continuous integration easier.
Log in or sign up for Devpost to join the conversation.