pmiklos / orider Goto Github PK

On payment received save the payment unit on reservations.

On payment confirmed set paid or failed status. Failed if there was a double spend (sequence=bad)

Currently only drivers can post a ride and passengers book a ride. However, it would make sense for passengers to post rides they are looking for so people with car might consider sharing their car if they happen to have some business on the posted route and around the indicated time.

The login screen offers 3 ways of logging in. It may be confusing for the user what to do, so make these options available on devices where it makes sense:

1. log in by link --> mobile only
2. log in by QR code --> desktop only
3. log in by copy pasting pairing code --> desktop only

Rides can be auto-completed by tracking the driver's device location and comparing it to the drop-off coordinates. The driver should still have the option for manual completion in case the automated arrival detection wouldn't work. Ideally the auto-completion process could be canceled by the driver:

• coordinates of drop-off location are sent to the driver device (myride screen)
• location is tracked on the driver's device after boarding
• when driver's location is at the drop-off location the auto-completion triggers and is displayed on screen
• after 5-10 seconds the completion is executed unless the driver cancels it.

Allow drivers to enter vehicle information so passengers can find the car.

Show vehicle info on reservations screen so passengers can see what car they should be looking for.

Currently passengers can make a reservation with a click of a button. It is not possible, however, to cancel the reservation.

• add a cancel function to remove the reservation
• notify the driver about cancellation

Let users add their real names using the attested profile. Also, allow people to verify if they have a drivers license by requesting the id_type and checking if it is DRIVING_LICENCE and so earn a "verified driver" badge.

Allow passengers send message to drivers and vice versa. Both the driver and the passenger are paired with the ORider bot so the bot can dispatch messasges between them without any additional pairing.

The carpool contract is relatively big and it costs about 1500 bytes when spending the funds from the contract due to the inclusion of the contract definition. The introduction of definition template would greatly reduce the costs since it the actual contract would only refer to the template hash and the actual parameters.

The template has 4 parameters:

• carpool oracle address
• carpool payout processor address
• driver's payout address
• passenger's refund address

The carpool oracle address and payout processor address are relatively stable and not expected to change, so they could be hard-coded into the template to further save cost.

Try some ways to keep the screen on while driving so location tracking would be continuous and so trip auto-completion would actually kick in automatically.