- [How to make client and server communicate so that client listens for changes in DB continuously]
- How will the driver know when the user has requested a ride in his location
- How will the user know when the driver nearby has accepted his ride
- Live tracking the driver in user app
- Able to select destination on map
- Gets fare and ETA estimate before booking
- [Optional] Optimize so that nearest drivers are shown in map on user side
[nearest drivers can be chosen by ETA or Euclidean distance]
- Book the ride
- Route the path to driver
- Able to cancel ride
- Emergency contact option
- Receives notification when ride arrives
- Route path to destination
- Ride completes and receives bill receipt as notification
- Payment interface GooglePay
- Receives notification to accept ride or not
- When accepted route the path to user
- After reaching route path to destination
- Show bill amount after ride
- [New db design is yet to be made] Use two json files for user and driver
- All the files in the git repo are hosted on the server in the same directory.
- Header ["Content-Type: application/json"]
- /adduser
- Request {"phone_no" : "", "name" : "", "email" : "", "password" : ""}
- Response {"error" : true/false, "message" : "", user_obj_that_got_created}
- 201, 202, 405
- /login
- Request {"phone_no" : "", "password" : ""}
- Response {"error" : true/false, "message" : "", user_obj_that_logged_in}
- 200, 202, 405