Today I explored an Uber ride-request status component with one question:

When the driver is still completing another trip, does the interface clearly explain what is happening and when the rider should expect them to arrive?

In the current experience, “Mateus is on the way” can sound like the driver is already heading directly to the rider, while other information shows he is still completing a nearby trip. The 3-minute ETA is visible, but its meaning is explained elsewhere.

In my design exploration, I: made the driver’s current state explicit connected the ETA directly with “Estimated arrival to you” grouped current activity, expected arrival, and ETA into one persistent feedback block

The goal was to reduce interpretation during a waiting moment and make the system response easier to understand at a glance.

Business hypothesis: clearer ride-status feedback could reduce rider confusion, improve trust in the system, and make the waiting experience feel more predictable.

This is an independent design exploration based on the visible Uber experience, not a claim that the current solution is wrong. Real impact would need validation through rider behavior, support data, cancellation patterns, and product metrics.

When you’re waiting for a ride, what matters most to you: what the driver is doing, the ETA, or where they are on the map?