Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passenger Pickup ambiguity #52

Open
TSampley opened this issue Sep 23, 2024 · 0 comments
Open

Passenger Pickup ambiguity #52

TSampley opened this issue Sep 23, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@TSampley
Copy link
Contributor

We want to track when 1) the driver arrives at the pick up location as well as 2) when they begin travel to the passenger destination. These should be separate events; ideally they occur within seconds of each other: the provider arrives at the pick up location and the passenger enters; the provider then confirms the ride start. In the worst case, the provider may arrive and need to wait for the passenger to arrive.

  • Problem: Arrival confirmation and Trip start confirmation may be annoying to Providers
    • Solution: Origin arrival event could be automated by GPS proximity to origin
      • Problem: Temporary loss of GPS accuracy could prevent registering provider arrival
        • Solution: Provide button to manually progress to arrived state
    • Solution: Origin departure event could be automated by accelerometer and/or GPS
      • Problem: Same as above - temporary loss of GPS accuracy could prevent registering provider departure a.k.a. trip start
        • Solution: Provide button to manually progress to trip started state
          • Problem: Provider would be moving at this point - distracting from driving; minor concern?

We cannot account for all potential issues; we need to determine the most reasonable cases to support.

  • Problem: Passenger phone has died
    • Solution: Automatically cancel trip request after some time with no communication from passenger
    • Solution: Continue with trip since all necessary interaction is on Provider-side; allow Provider to cancel if necessary
  • Problem: Passenger is not at pick up location
    • Solution: Driver can message passenger
      • Problem: Passenger is not able to reach location (in timely manner or at all)
        • Solution: Driver can cancel trip
    • Solution: Reference passenger location
      • Problem: Passenger GPS is not working
        • Solution: Driver can message passenger
          • Problem: Passenger is not able to reach location
            • Solution: Driver can try to find passenger
              • Problem: Expects driver to potentially go on wild-goose chase for ornery passengers

We expect the passenger to be at the agreed/confirmed pick up location.

@TSampley TSampley self-assigned this Sep 23, 2024
@TSampley TSampley added the enhancement New feature or request label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant