RideStork - The Carpool Orchestrator

• 

  Event Creation Page. Intakes event data utilizing Google Maps API and a custom pin location retrieval React component.

• 

  Registering for a Unique Event.

• 

  Driver Registration Form with Google Maps API Location Input React Component

• 

  Confirmation Page and Optimal Route for Passengers Serving. Once a user is confirmed, the event's routes are optimizedd and routes served.

What problem are we solving?

Event organizers like our fantastic UCF KnightHacks president Nick rarely have the opportunity to have bus seats available for everyone interested in participating in a shared event. As such, carpools are essential to getting the most out of the interest from tight-knit groups like ours.

With spreadsheets, Discord channels, and Google Forms being the main avenue for event organizers like Nick to start matching driver-passenger groups, our vision with RideStork is to make manual carpool organization a task of the past.

What does RideStork do?

RideStork allows for any user to sign up to a common event through their organizer's link, and concatenates the departure and pickup location of all drivers and passengers event to automatically match drivers with eligible passengers with the lowest detour time from their original route.

RideStork offers a high-ease, low-stress platform for drivers, passengers, and organizers alike.

How we built RideStork

RideStork utilizes micro-service architecture to serve our the users' data stored on a serverless postgres instance (Supabase) for Express.js and Flask to employ our data processing pipeline, which is delivered through Next.js on our React frontend.

Under the hood, our algorithm efficiently utilizes the Google Maps API to not only optimize the best routes for our users, but also provide a unique bi-directional pipeline for them to input location data and receive routing and event information.

Challenges we ran into

Throughout the 36-hour ShellHacks challenge period, we had many hands-in-face realizations and jump-up-high-five moments to follow. What we're most proud of in RideStork is that despite these challenges, we never doubted our ability to see RideStork's finalization.

• In a data-driven application like ours, efficient database queries are essential. We spent a fair share of time on writing constructing Prisma queries to retrieve all needed data at once.

• User experience was a large consideration when creating a platform that aims to perform intense calculations on many data points at once. Creating a model that could serve as an efficient backbone of RideStork's implementation was a large hurdle we think we graciously overcame.

• Aiming to create a maintainable, seamless, and reliable data pipeline meant that we had to consider the many ways we'd use user data and implement the most complex API any of us on the team have worked on to this point.

Accomplishments that we're proud of

Here's a list of first-time accomplishments for us at team RideStork: • Our first micro-service architecture! • Our first Google Maps API implementation! • Our first Auth0 implementation! • Our first hackathon!

What we learned

We learned far more than we were excited to when we decided to work on our first hackathon. Aryaan, Antoni, and I (Gabe!) have each worked on at least one aspect of the paradigm used to employ RideStork, but the exciting pace of Shellhacks this weekend not only challenged us to hone in on our time management skills, but also our teamwork skills! As such, our initial workload partitioning quickly evolved into rapid pair programming spurts and 'brain huddles' for hurdles.

We learned that we love hackathons, and that the opportunity to work together has been an impactful experience on our outlook in project building.

What's next for RideStork - The Carpool Orchestrator

Aryaan, Antoni, and I have high hopes for RideStork. Believe it or not, Aryaan and Antoni were looking for a third member and we happened to meet at this hackathon! We're incredibly lucky to have been able to form such an energetic team, and we're excited to say RideStork will continue development after Shellhacks. Our immediate aim is to allow for RideStork embeds for event organizers to easily deliver the platform to their users.

Built With

• amazon-web-services
• auth0
• bun.sh
• express.js
• flask
• github
• google-maps
• next.js
• postgresql
• prismaorm
• python
• react
• react-query
• supabase
• tailwindcss
• typescript
• vercel