the dead end, on camera
Gateway at Tempe is a large gated student complex on University Drive, 1.7 miles from Arizona State University by the app's own search. Booking from inside it returns "Pickup unreachable. Can't get to that spot right now" and a single button: a blank search box.
the constraint is visible and reasonable
Waymo doesn't serve curbs inside the gates: private internal roads, no approved pullover. The car staying out is correct behavior.
the copy says "right now"
"Can't get to that spot right now" implies something temporary, like traffic. The real cause is permanent. Riders retry later, fail again, and conclude the product is flaky.
the only exit is a blank search box
"Search for pickup" hands the entire recovery job to the rider. No suggested spot, no pin at the gate, no walk estimate. An error that reports instead of resolves.
the answer is 373 feet away
Manually drag the pin to the leasing office and the booking goes through. The system can serve this address. The app just never says so.
the lost demand is invisible
The error event is surely logged. What no dashboard shows is the demand it suppresses: the resident who never tries again, the complex that quietly learns Waymo "doesn't work here." Funnels count failed attempts, not the rides that stop being requested.
a pickup that fails by design
Even when a spot is found, the mechanics quietly work against the rider. On this booking the app proposed a pickup that is an 8 minute walk away, for a car that waits 5 minutes after arriving. The design only works if the rider leaves home before the car shows up. Watch what happens if they don't.
a rider who watches the map can pre-walk and make it. but every cue the app sends is tied to the car ("arriving soon", "your car is here"). the cue that would actually help is tied to the walk: "time to leave" = walk minus wait. that one is missing. the fix is a single notification.
the long way, unexplained
A secondary observation, held to a lower confidence bar than the error screen: on short trips across Tempe and Mesa, my Waymo has taken visibly longer surface-street routes than a typical driver would choose. I'm not alone. Riders have publicly reported a 2-mile trip turned into an almost 30-minute ride and a commute that roughly doubled. Residents on one San Francisco street reported Waymos repeatedly spending 30 minutes navigating it (anecdotal reports via InsideEVs, SFGATE, and r/waymo).
the cost is time, not money
Fares lock upfront, so a longer route doesn't raise the price. It quietly raises the trip duration, and on short in-city hops the difference is very noticeable from the back seat.
scoped out: the freeway half
Freeways are Waymo's known lever here: routing launched in late 2025 with claimed savings up to 50%, then paused in May 2026 for construction-zone work, with a return expected. Either way this section is about the short surface-street trips, where freeways never enter the route.
the short-trip gap remains
In-city trips never touch a freeway. When the car picks a conservative surface route, the rider sees a longer ETA and hears nothing about why.
same disease as the error screen
The system has reasons. The rider never hears them. One line of "why this route" plus the ETA delta would convert mistrust into understanding, the exact transparency fix the booking flow needs.
the constraint is fine. the handling isn't.
This distinction is the whole memo.
Waymo's help center is equally candid: cars choose spots they can best navigate to, and red curbs, bus stops, construction, and parking rules push pickups away from the rider. The constraint lands exactly where people live and gather: gated complexes, private lots, regulated curbs. And to be clear about what I'm not claiming: I know the mitigations exist.
All real, all shipped. That's the point. The system has answers, and the error state uses none of them.
it dead-ends
The app knows the nearest reachable curb (it accepts the leasing office instantly) but returns a blank search box instead of offering it. The burden of discovery lands on the rider.
it never explains
"Right now" framing implies a temporary glitch. One honest line, "we can't stop inside this community," converts frustration into understanding. Silence converts it into churn.
it never learns
Saved places exist, but no pickup knowledge attaches to them. My correction has to be re-made, and it teaches the system nothing for the next resident. Free training data, discarded.
waymo already built the answer
This is not a request for new technology. It's a request to surface existing technology at the exact moment of failure. Both screens below are live, try the buttons.
Pickup unreachable
We can't reach that exact spot
Waymo holds granted patents for suggesting reachable pickup spots and for scoring candidate stops by inconvenience. One of them spells out the exact logic this screen needs: the most convenient stop is right in front of the entrance, because that is the point of least inconvenience. The suggestion engine is not speculative. It is Waymo's own granted IP, and it simply never appears at the error state, the one moment the rider needs it most.
never dead-end
Replace the blank search box with the nearest reachable spot, walk time, and one-line reason. Pure app-layer work. No driving-stack changes, no new validation burden, no map edits.
remember the correction
Attach a confirmed pickup point to saved places, then learn in aggregate: where many residents of one complex drag their pin to the same leasing office, that spot becomes the default suggestion for everyone at that address. Rider corrections are free, labeled training data.
negotiate the curbs that don't exist
Where no reachable spot is acceptable, create one. Property-operator partnerships can validate in-gate pickup points across hundreds of communities per deal, and the city precedent already exists: Nashville approved 24 geofenced rideshare zones in April 2026, and the playbook is Waymo's own, the same patient arc that took Sky Harbor from a train-station dropoff to full 24/7 curbside in under two years.
small screen, compounding cost
Every number below multiplies the population walking into this error, and the newest riders are the ones most exposed to it.
Expansion is concentrated in famously gate-heavy Sun Belt metros, and the riders Waymo is courting hardest are the ones least likely to drive: college students behind leasing-office gates (mine sits 1.7 miles from ASU), and teens, whose Phoenix accounts ship with Waymo's own advice to "minimize walking time." The growth strategy and the failure mode point at the same addresses.
And the first booking from a new rider's home is the highest-leverage moment in the funnel. At these addresses, it opens with the word "unreachable."
how i'd measure it
metrics
open questions for internal data
this is a sample of how i'd work on rider experience. more teardowns at chetanjonnalagadda.com