-
Notifications
You must be signed in to change notification settings - Fork 3
Use location #12
Description
I think the following flow could bring two things: a faster interaction and infinite pickup points.
1) Driver starts
Driver is about to start driving and tell the system he is a driver. Exactly as he does in the current version. He send his position to the bot.
2) Passenger starts
Passenger is at the bus stop. He says is a passenger (as he does in the current version) and sends his location to the bot. The bot replies with an approximation of the location to the nearest bus stop (easy to do since all the data are available).
3) Destination
Passenger send his destination. How ?
- By selecting from a closed list (now he would see only ['Trento','Povo'])
- By texting it (i.e. "povo, alla malga")
- By sending a voice message
4) Waiting
Now passenger is waiting for a driver
5) About to leave
Driver is in his car and is about to leave for his way to work. He has already declared himself as a driver and has sent his position to the bot.
6) Broadcast
Driver receives a list of ALL the ride requests within a given range from his position. The item of the list he receives are tuples: (request_index,waiting_position,destination).
7) (driver_x,passenger_y)
Driver accept to satisfy one request from the list and a message is sent to the waiting passenger. The message contains also driver position and an estimation of the time it will take. The passenger request is cancelled from the list and new drivers are not going to see it.
8) Feedback
Driver leaves and stops to pickup the user. At the end both of them send a confirmation and leave a feedback.
9) Learn
The system will try to offer the best possibile order of the list by analyzing previous rides: i.e. passenger going to a specific location, particulare passengers, distance from waiting position, etc.