Back
NoteAug ’22

The city you test in

Uber Studio’s extensions changed the Rider, Driver, Eats and Freight apps’ environment on the phone itself, so you could see the product as it would behave in Bangalore or Dublin. Teams test from where they sit, and the product drifts toward that place.

Typeface

At Uber, almost everything depended on the city you were in.

That makes the most ordinary kind of testing quietly incomplete. An engineer opens the app on their own phone, at their own desk, and sees the product their city gets. It looks right, because for that city it is. The same build can behave differently somewhere else, and nothing on that desk would show it.

Uber Studio began as a web app for running the marketplace from a chair: spawn riders and drivers, walk trips through their states, call any internal service. It also reached past the browser. Extensions in the iOS and Android apps for Rider, Driver, Eats and Freight changed the app’s environment on the device itself, so you could see the product as it would behave in Bangalore or in Dublin.

Where that switch lives matters. A simulation in a browser can show you another city’s data. Changing the environment on the phone shows you the real app, on real hardware, behaving the way it would there. You check the thing people will actually hold.

Every team tests from where it sits, whether it means to or not. Its city, its language, its network and its own accounts become the default case. The product drifts toward that case, because it’s the one everyone on the team looks at every day.

Telling people to remember other places doesn’t survive a busy week. What works is putting the other place one switch away, on the device already in their hand, so that looking at Dublin costs about as much as looking at home.