They have nearly 30,000 employees, mostly SDEs from what I understand. Its been discussed (and rationalized) here, but I still don't understand how that many are necessary. I read somewhere else that their engineering tend to need to rewrite their software every two years to keep up with the scale, so maybe they need them? it still seems insane to me.
This blows my mind. I used to use Uber a bunch, and I built relationships with drivers such that I could just text them and get a ride at a certain time for a discount.
Ultimately, I wonder if Uber is prime to be disrupted if drivers got together and funded a few engineers to build a city-scale service for the hailing and payment aspect.
>Ultimately, I wonder if Uber is prime to be disrupted if drivers got together and funded a few engineers to build a city-scale service for the hailing and payment aspect.
Apparently a whole bunch of folks are trying to do just that.
I was going to provide just one example, but a web search[0] shows a whole bunch of these efforts in a variety of locales. As such, I just provided the web search results here.
Austin had that for a while when they went and banned Uber/Lyft. They were... ok? The issue ends up being that it's hard to be a one-city service that's mostly used by people who don't live in the city. If I arrive in a random city, the last thing I want to do to get to where I need to go is have to search for which app I need to install and give my CC info to in order to get a cab.
NYC used to have Juno, but it went bankrupt in 2019. I feel like if you can't run a single-city rideshare app in NYC, you're gonna have a hard time doing it anywhere else.
>NYC used to have Juno, but it went bankrupt in 2019. I feel like if you can't run a single-city rideshare app in NYC, you're gonna have a hard time doing it anywhere else.
I haven't used it (I always pay cash, as the drivers are charged ~3-5% per fare for "CC processing" when a card is used), but every NYC taxi has a feature where you can pair with the onboard system and pay with your phone.
Not sure what "pairing" requires, perhaps someone else has used this feature and can comment.
>If I arrive in a random city, the last thing I want to do to get to where I need to go is have to search for which app I need to install and give my CC info to in order to get a cab.
Searching and installing a random app introduces a slight amount of friction, but I don't think payment necessarily has to be that much of a hassle. Just use apple/google pay.
That assumes the app supports on-phone payment options like that. Obviously it's gotten more ubiquitous now, but most of the non-Uber/Lyft apps I've used in the past didn't. They often will require me to make a full account as well, give them name, address, email... I think one of them tried to make me upload a picture of my Driver's License, even thought I was very sure I wasn't signing up to be a driver.
Obviously this all could be easy, but it's amazing how many apps fail to make things easy to onboard. When I've just gotten done traveling for hours and just want to get to some place to relax, the last thing I want is to wrangle new account creation in some app where they're trying to be cheap and haven't hired any UX designers to smooth out the process because "you can rebuild Uber with 3 smart devs" as everyone on HN says.
Already happening in NYC w/ Curb, though many (like me) are staying the fuck away from it and sticking w/ Uber/Lyft. It's a matter of trust and operational complexity (that's not easily "solved" from the ground up), imho
I agree and am not quite sure where it's going (other than software).