UberCraft6 min read

Designing the two minutes before the car arrives

The wait is the product, so the map never stops moving.

The surface: Setting a pickup point, the fare and vehicle choice, the request, and the waiting screen with the moving car and the ETA.
What the user wants: I need a car now, I want to know what it will cost, and I want to stop worrying about whether it is coming.

Pickup already guessed

The app opens with a pickup location pre-filled from device location and a map already centred, with recent and saved destinations listed.

Smart defaults

The two inputs the product needs are the two things it can often infer. Pre-filling turns a form into a confirmation, which is a much lighter action. Recents matter more than search because trips are overwhelmingly repeated.

Price before commitment

Vehicle options are presented with an upfront fare and an arrival estimate, side by side, before the request is made.

Uncertainty reduction

The original friction in taxis was not hailing, it was not knowing the cost until the end. Naming the price before the ride converts an open-ended risk into a decision. Placing the options side by side also reframes the question from whether to ride to which ride.

The tiers as an anchor set

Options are listed as a ladder from cheapest to premium, with the middle tiers visible next to the cheap one.

anchoring: The first number you see shapes every judgement that follows. and compromise effect

A price shown alone has nothing to be judged against. A ladder makes the cheap tier feel like a saving and the top tier makes the middle feel reasonable. The set is doing more persuasive work than any individual price.

The car on the map

After the request, a vehicle icon moves along the map toward the pickup point, with a countdown and the driver's name, photo, plate and vehicle.

Operational transparency

Waiting with visible progress feels shorter than waiting the same time in silence, because the anxiety being managed is uncertainty rather than duration. Showing the car working also makes the service feel like effort is being spent on the rider. The plate and photo answer the separate question of which car to get into.

Surge as a confirmation step

When demand pricing applies, the higher fare is shown before the request and historically required an explicit acknowledgement.

Informed consent at the decision point

A price rise discovered after the ride would break trust permanently, so the cost is moved to the front where it can be refused. It is a rare case of a product making itself harder to use in order to stay credible. The mechanism only works if the acknowledgement is genuinely legible rather than buried.

Rating after arrival

The trip ends with a star rating prompt and optional tip, shown before the app returns to its normal state.

Peak-end and forced closure

Asking at the moment of arrival catches the rider while the experience is intact, which is when the rating is most informative. Placing it in the path back to normal use maximises response rate without a notification. The rating is also the main quality lever over a workforce the company does not directly manage.

The same wait, told two ways

A schematic four minutes. The clock is identical in both; what differs is whether anything on screen is moving. An unexplained wait gets worse the longer it runs, because with nothing to read the only available activity is doubting the app.

What not to copy

The moving car on the map is a smoothed representation, not a raw GPS trace, and ETAs shift. A rider who trusts the animation literally is being given more precision than the data supports.
Surge pricing is transparent to the rider and opaque about where the money goes, which lets the rider assume a driver benefit that is not guaranteed.
The five star rating system with a high effective pass mark turns a rating into a punishment mechanism for drivers, and riders are not told what a four actually does.
Tipping is prompted at the end with preset amounts, which uses the social awkwardness of the moment to set the default contribution upward.

The takeaway

When people are waiting, show the work. Visible progress buys more patience than a shorter wait with no information.

Finished the teardown? Bank it and the day counts toward your run.

Where the principles come from

The Design of Everyday Things (feedback), Don Norman
Thinking, Fast and Slow (anchoring), Daniel Kahneman
Operational Transparency, Ryan W. Buell, Harvard Business Review
Response Times and the psychology of waiting, Nielsen Norman Group

Written from public behaviour of the product, not from inside it. Interfaces change often, so treat the flow described here as of the time of writing and check the live product before quoting it.