130 likes | 274 Views
Driver. Ridetaker. E ASY RIDE. Interface. A location-based Driver- Ridetaker interface application. Yaron Inger , Asaf Kotzer, Shir Peled. Introduction. Key Concept. A location-based pick up application Reduces waiting time both sides spend when sharing a ride
E N D
Driver Ridetaker EASY RIDE Interface A location-based Driver-Ridetaker interface application YaronInger, Asaf Kotzer, Shir Peled
Key Concept • A location-based pick up application • Reduces waiting time both sides spend when sharing a ride • Alerts the ride-taker when driver approaches • Machine learning algorithm will learn when to alert
The Market • Carticipate • iPhone app • Location based social network addressing transportation needs • Users are able to car pool, even if they are not acquainted • CarBuddy • Web site • Similar service, not meant to be a social network • Calculates fuel costs and divide among participants (+8% fee for the website) • OpenRide • iPhoneapp • Spontaneous rides: a driver publishes path while driving, passengers may also look for ride now, rather than scheduling in advance
Easy Ride – The Edge • We don’t focus on finding the rides, but on reducing the waiting time upon pick up • The infrastructure will not be tailor-made for rides, and can be employed for other uses • Target audience: • Young people going out together • Co workers car pooling • Parents picking up their children from school
Step 1 • User (driver) starts application and sees current location
Step 2 • User enters pickup location (ridetaker): • By address • By location on map • Online
Step 3 • When approaching destination, the application alerts the ride taker, prompting them to meet driver: • By text message • By phone call
Step 4 • Driver and Ridetaker ride safely to destination
Difficulties • Technical • Communication –the two phones are not necessarily connected, and are not necessarily smart-phones. • Possible solutions: Rider’s phone will publish GPS coordinates via SMS, or web service • Maps (in Israel) • Algorithmic – learning is difficult • Possible solutions: Add prior knowledge of rider (e.g. sex, age) • Design • Key concept: complete separation between infrastructure and Driver/Ride-taker interface • Learning engine: based on reinforcement learning algorithms • Interface: keep it big and simple • Keep it simple (and low on time-consumption)
Open Forum • Question and suggestions are welcome