Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I worked at Uber. The UX designers were pretty obsessed with the iPhone app, making sure it was pixel perfect and the little cars in the city view moved smoothly and every transition was crisp and so on. The vast majority of new users at the time were on the comparatively ugly Android app.

Things got pretty bad. More than 95% of all employees (and I'm guessing 99% of designers) were using iPhones at the time. There would be rough edges all over the Android app, but as one of our designers said "people with taste don't use Android".

Imagine knowing that most of your new users were getting a subpar experience, and that not being enough motivation to expense a flagship Android and drive it daily.

But the new users kept coming, and despite mostly being Android users, they still used the product. Turns out that legacy taxis are themselves an ugly interface, and ugliness is relative.





> The vast majority of new users at the time were on the comparatively ugly Android app.

Probably the vast majority of profitable Uber users were still on iOS, though, like most apps?

> but as one of our designers said "people with taste don't use Android".

Based lol


> people with taste don't use Android

Probably true at the time.


I remember excitedly switching to a Nexus 5X and then going back to my old iPhone a few months later because every app felt like a bad port of the ”original” iPhone app.

Using the term "Legacy Taxi" to imply that a taxi you don't summon by phone is somehow out-dated is wild. I understand the reason you would use it, especially at a company like Uber, but it still seems hilariously delusional.

I've never worked for Uber and I see the old model as a barbaric non-starter, why on earth would I want to flag a car down instead

The point is that a taxi is a taxi. It's like calling cash "Legacy Payments"



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: