Most people only go to another city once or twice a year, so it's not a significant issue for them.
Personally, I use other apps when in NYC, but fall back to Uber when I'm somewhere else and can't find a local app.
Is that so? I'm not aware of anybody that never goes to another city multiple times per year and that includes infants and the elderly.
There, now we've both shared our experiences!
I've got acquaintances from all over the planet though, and even there most people travel with some regularity to other cities. Holidays, family visits and so on, and then of course there is business travel which I would assume is one of the larger customer groups for Uber/taxis.
Don't worry, once there are enough apps someone will figure out how to scrape and aggregate the info. The same thing happened when airlines and hotels started putting booking info online except at the time it was websites instead of apps.
Ride hailing is extremely fluid. Must be real-time. Must be able to provide GPS coordinates of the user to the service in question.
I don't think you'll see an aggregation app until there is some ride hailing standard that is adopted by the various providers.
But what does that API look like? What are the MVP operations required to make a successful ride hailing API? Will that API provide realtime location info of the driver, or allow payment, or <insert myriad of questions here>.
Without a standard, the Taxi API landscape will be a mess.
> Apps like "Transit App" will just integrate them all
This is a pretty major oversimplifications of this issue. Sure, this is technically possible, but it sounds like a horrible solution.
Bringing in the considerations about the actual API design, this also means that user experience may vary wildly depending on which service they're interacting with.
Can != should. If aggregating many systems is the future, we should push for a technical solution that doesn't suck.
Not having some API standard is usually how it's done with many services nowadays, and the market/comparison apps have to integrate multiple APIs. Big deal.
Again, I should reiterate: I'm not arguing that it can't be done or that it's not possible. I'm arguing that the result will be subpar. Let's remember that the parent discussion is about the creation of a system that rivals the Uber/Lyft experience. If you want to do that, someone (probably someone big like Google as suggested in another comment) is going to have to influence the design of these APIs so the end user experience is a consistent/good one.
There very well may be one ride hailing app to rule them all, but implementing it will be an entirely different beast.
However, as an example, when Uber and Lyft left Austin, one of the companies created locally (RideAustin) to replace the gap does allow payments via Apple Pay. Very convenient, and they also give you the option of rounding up to donate to a charity of your choice.
I guess it's just up to all the other options to realize what people want.
Apple Pay is great if you're immersed enough in that ecosystem, but otherwise? Uber and Lyft store CC info, allow for easy deletion, and take PayPal. I'm glad Ride Austin exists, but they still seem to be several laps behind on letting you give them money.
Second, none of these apps I have seen thus far even attempts to make it easier for the user to add payment methods. Each time I need to put in my credit card information? Twice if I am on business? Nobody has taken advantage of Apple or Android pay integration.
I don't consider myself a heavy cab user, but I probably take at least ~200 rides a year, and unless the city is regulated (credit cards) I am using Lyft.