Carpool Connect (2021)
Embedded Files
Rideshare application exclusively for university students with the aim of reducing carbon emissions
Created using Android Studios
Coded in Java, Javascript, and Kotlin
Submitted to Florida Hacks with IBM Hackathon
Overview
Carpool Connect is an Android app for Florida university students who want a way to save money when traveling or don’t want to travel long distances alone. Carpool Connect is a carpooling app that focuses on a community-based way to travel together with other students traveling to the same place as you, saving both of you money and reducing your carbon emissions. Unlike other “carpooling” services, our product caters specifically to university students so that they may have a comfortable and efficient trip.
Carpool Connect allows users to input their starting and ending locations and matches them with potential users that are driving to similar spots. The core idea revolves around carpooling to save on car emissions while also saving users money compared to driving themselves. Additionally, by catering specifically to university students, this creates a safe environment as every user has to be authenticated with their university email.
Features
Google Maps API
We have implemented Google Maps API to allow users to input their starting point and destination. Once they have done so, this information is used to create a “Trip Post” which will be shown to other users nearby looking to drive to the same destination. We also use this information to determine how much the Rider should pay the Driver for gas depending on how long the drive is and taking into account how much of their travel is on highways versus normal roads. A user can input a general name of a place, such as “University of Florida”, or they can input a specific address.
PayPal API
To ensure safe and reliable payment between Riders and Drivers, we have also implemented a PayPal API to allow for in-app payments. One can pay directly through their PayPal account, scan their card to automatically input the card information, or manually input their card information. Using the PayPal API ensures that if a Driver does not follow through with picking up the Rider, the Rider will be fully reimbursed.
User Accounts and Profiles
In order to use the app, every user must create an account. In order to create an account, they must provide their full legal name, .edu email, phone number, and age. Their profile will reflect all of this information, with the option to add a profile picture.
Trip Posts
Drivers who are going on trips can post open invitations for their rides, which include the vehicle they will be driving, their destination address, their departure address, and when they will be leaving.
Requests to Join Trips
Before a Rider can join a Driver’s trip, they must send a request to the Driver, who can briefly review the Rider’s profile and rating before deciding to add them to the ride.
Car Identification System
This algorithm is used to retrieve MPG, Emissions, and Engine Displacement from the user’s provided Make, Year, and Model of their car.
Rider Gas Price Algorithm
This algorithm automatically determines the amount the Riders need to pay to the Driver for gas by taking into account the number of Riders, the emissions of the car, and the mileage.
Demo of Carpool Connect Main Features
demo.mp4Demo of Integrated PayPal API for In-App Payments
PayPal Demo.MOVDocumentation
Basic Wireframe of User Interface
Screen 1 - User selects the Carpool Connect app from their phone home screen.
Screen 1 - User selects the Carpool Connect app from their phone home screen.
Screen 2 - User signs into their account or creates a new account. To create an account, they must provide their full legal name, .edu email, phone number, and age.
Screen 2 - User signs into their account or creates a new account. To create an account, they must provide their full legal name, .edu email, phone number, and age.
Screen 3 - The user will then be redirected to the home screen in which a user can choose to select which screen to go to next. They may choose to post an upcoming drive, request a ride to a specific location, look at current posts and see where other users are traveling to, or go to their profile.
Screen 3 - The user will then be redirected to the home screen in which a user can choose to select which screen to go to next. They may choose to post an upcoming drive, request a ride to a specific location, look at current posts and see where other users are traveling to, or go to their profile.
Screen 4, Profile - Here, a user may see all the information that they provided at sign up plus have the option to add a profile picture. If they have received ratings from previous travels, they will also be able to view that here.
Screen 4, Profile - Here, a user may see all the information that they provided at sign up plus have the option to add a profile picture. If they have received ratings from previous travels, they will also be able to view that here.
Screen 5 & 6, Post a Drive - If a user is planning on driving and is looking for Riders, they may post so here. Firstly, they will choose their starting and final destination using the Google Maps API. Next, they will select their departure date. Finally, they will confirm that all the information is correct before posting this drive onto the Trip Posts screen. Their drive will be visible by other users in said screen.
Screen 5 & 6, Post a Drive - If a user is planning on driving and is looking for Riders, they may post so here. Firstly, they will choose their starting and final destination using the Google Maps API. Next, they will select their departure date. Finally, they will confirm that all the information is correct before posting this drive onto the Trip Posts screen. Their drive will be visible by other users in said screen.
Screen 7, Request to Ride - If a user is looking to find a ride to a specific location, they may do so here. Firstly, they will choose their starting and final destination using the Google Maps API. Next, they will select their departure date. Finally, they will confirm that all the information is correct before posting this drive onto the Trip Posts screen. Their ride request will be visible by other users in said screen.
Screen 7, Request to Ride - If a user is looking to find a ride to a specific location, they may do so here. Firstly, they will choose their starting and final destination using the Google Maps API. Next, they will select their departure date. Finally, they will confirm that all the information is correct before posting this drive onto the Trip Posts screen. Their ride request will be visible by other users in said screen.
Screen 8, Trip Posts - The posts that are created from the Post a Drive and Request a Drive screens will be displayed here. Drivers who are going on trips can post open invitations for their rides, which include the vehicle they will be driving, their destination address, their departure address, and when they will be leaving. Riders who are looking for Drivers will also be able to be seen from this screen. If a Rider sees a drive post that they would like to go to, they may request the Driver to join them. On the other side, Drivers that see a Rider that is looking to go to the same destination as them may reach out to them.
Screen 8, Trip Posts - The posts that are created from the Post a Drive and Request a Drive screens will be displayed here. Drivers who are going on trips can post open invitations for their rides, which include the vehicle they will be driving, their destination address, their departure address, and when they will be leaving. Riders who are looking for Drivers will also be able to be seen from this screen. If a Rider sees a drive post that they would like to go to, they may request the Driver to join them. On the other side, Drivers that see a Rider that is looking to go to the same destination as them may reach out to them.
Other, PayPal / Payment Screen - Once a Driver and Rider combination has been confirmed, the Driver may request the Rider to pay their share of gas money. The Rider may then pay the Driver within the app through PayPal or by entering their card information.
Other, PayPal / Payment Screen - Once a Driver and Rider combination has been confirmed, the Driver may request the Rider to pay their share of gas money. The Rider may then pay the Driver within the app through PayPal or by entering their card information.
System Context Model
Carpool Connect connect is a web app designed natively for Androids. The front end is designed in Android Studio, using Java and XML. The front end handles all user inputs, displays, and map data. Dependencies used for the front end include the Google Maps API for handling address data, okHttps for making HTTP requests to the backend, and GSON for parsing JSON data.
Carpool Connect connect is a web app designed natively for Androids. The front end is designed in Android Studio, using Java and XML. The front end handles all user inputs, displays, and map data. Dependencies used for the front end include the Google Maps API for handling address data, okHttps for making HTTP requests to the backend, and GSON for parsing JSON data.
The back end is written in Java using the Spring Boot framework. The back end handles the storage and transmission of all data for profiles, trips, trip requests, vehicle data, and pricing. Consequently, all computations involving this data, such as the gas price algorithm, are also done on the backend. All of this data is stored on a SQLite database. Dependencies used on the back end include SQLite JDBC for connecting the database to the backend, and Hibernate for simplifying storage and retrieval of data from the database.
The back end is written in Java using the Spring Boot framework. The back end handles the storage and transmission of all data for profiles, trips, trip requests, vehicle data, and pricing. Consequently, all computations involving this data, such as the gas price algorithm, are also done on the backend. All of this data is stored on a SQLite database. Dependencies used on the back end include SQLite JDBC for connecting the database to the backend, and Hibernate for simplifying storage and retrieval of data from the database.
The overall architecture of the backend is designed around the database tables. For each table in the Database, there is an API and Service class associated with that table. The API class handles all HTTP requests from the front end, receiving and sending data in JSON format as requested. The Service class takes said data and stores and retrieves it from the database as necessary, as well as performing necessary computations on it.
The overall architecture of the backend is designed around the database tables. For each table in the Database, there is an API and Service class associated with that table. The API class handles all HTTP requests from the front end, receiving and sending data in JSON format as requested. The Service class takes said data and stores and retrieves it from the database as necessary, as well as performing necessary computations on it.
View the official Hackathon submission by clicking on the link above!
Team:
Project Manager: Maia Gervasone
Scrum Master: Yonas Bahre
Development Team: Nicolas Perez & Hunter Rafferty
Page updated
Google Sites
Report abuse