How CityRide Works
A simple, transparent flow from discovery to trip completion.
Client flow
- 1
Client opens the CityRide mobile app
- 2
Location is used to find the client's position
- 3
Nearby riders are discovered
- 4
Client views rider information
- 5
Client taps Call
- 6
A Contact Event is created
Contact Event vs. Trip Request
Calling a rider creates a Contact Event. It records the client's attempt to reach a rider — it does not automatically represent a completed trip.
Trip Request lifecycle
01
→Contact Event
02
→Trip Request
03
→Requested
04
→Accepted / Rejected
05
→In Progress
06
Completed / Cancelled
This distinction is core to how CityRide works: a Contact Event is a record of contact intent, while a Trip Request follows its own lifecycle from request to completion.