Feature concept
Add a stop after you book
A concept for the Rapido ride app: let riders add a stop to a ride they have already requested, see the new fare first, and keep their captain. Two small fixes to the booking and orders screens come with it.
Today vs the idea
What Rapido lacks, and what changes
Once a ride is requested, the rider is locked in. Left is the live app today. Right is the concept.
1. The Active Order pill
It is the only way back to the order, but it sits on top of the booking screen.
- The pill floats over the sheet and hides content.
- The route can be read but not changed.
- An ad fills the space below the fare.
- Active Order is a row above Total Fare, so nothing is covered.
- The route card lists Pickup, Drop and an Add a stop row.
2. Changing the route after booking
The drop is fixed. To stop somewhere on the way, a rider has to cancel and rebook.
- After booking, the options are to add ₹20 to ₹50, or add another service.
- No option to add a stop.
- The pill covers part of the fare message.
- Search shows places along the route, each with extra minutes and extra fare.
- One confirm screen shows the old and new fare. The captain keeps the ride.
3. The Active Orders list
Opens from the pill. Today it tells the rider very little.
- One line per order: service and pickup address.
- No timer, ETA or PIN until the order is opened.
- Most of the screen is empty.
- Sorted by urgency: captain arriving (with PIN) first, then searching, then parcels.
- Status band with ETA or timer on every card.
- One main action per card. Add stop and Cancel are secondary.
- Parcels and rides together, with the services footer kept.
How it works
Where a stop can be added
A stop has to sit on the way, so the detour stays small and the captain's ride stays predictable.
| Rule | How it works |
|---|---|
| Along the route only | A stop must be between pickup and drop, inside the corridor. The drop never changes. |
| Corridor size | Up to 1.5 km or 10 min of extra travel versus the original route, whichever is reached first. Starting values, to be tuned. |
| How the rider picks | Type a place name or tap the map. Results come from inside the corridor, best match first, each with extra minutes and extra fare. |
| Outside the corridor | Shown greyed with the reason (for example, "Too far from your route") and cannot be selected. |
| How many, and in what order | Up to 2 stops. The captain visits them in route order, from pickup to drop. |
| When | From the moment the ride is requested until the captain starts it with the PIN. After that, Add a stop is hidden. |
| Fare | The price of the full route through the stop, shown before confirming (old fare struck through, new fare, extra distance and time). First 3 minutes of waiting at a stop are free. Removing a stop restores the original fare. |
| Captain | Sees the new route and fare before accepting. If they decline, the ride continues without the stop. |
Scope
What version 1 covers
Kept small so the idea is easy to follow.
| In | Out |
|---|---|
| Up to 2 stops, between pickup and drop | More than 2 stops |
| Cab, Auto and Bike rides | Parcel, shuttle, metro |
| Add or remove a stop until pickup | Changing the drop point |
| Stop search limited to the route (within 1.5 km or 10 min of it) | Addresses far from the route |
| Fare for the full new route, shown before confirming | New surge or boost on the change |
Design
Walk through it
Tap inside the phone, or use the steps. Pick any stop in step 2 and watch the fare change.
Concept mock. Stop names and fares are examples.