4 ms·
I agree. But that's true for current Uber . But once we start talking about UberPool and via its pretty close for the problem I describe, especially if we're t
by petra 10y ago
I agree. But that's true for current Uber .
But once we start talking about UberPool and via its pretty close for the problem I describe, especially if we're talking about the commute , with a possibility of people preordering rides sometime in advance(or even some prediction abilities about that).
As for the other option, carpooling ,it depends how far will people be willing to drive out of their way for that extra income. But being conservative and I they won't go out of their way , the problem becomes assigning riders to a million bus routes with small capacity, which seems to naturally break this problem into many ,largely independent problems , and may prevent any big exponential complexity.
Don't you agree ?
- deleted 10y ago[deleted]
- lern_too_spel 10y agoI suspect that preordering rides will be a niche case. Most people will be happy with the latency of ordering a car when they need one with an estimate of how long it will take to be picked up when they open the app (like existing Uber Pool). They will only order a car in advance if they need a guarantee that a car will pick them up at a particular time and wait for them, and in that case, it will make sense to dedicate a car to the user for that trip — nobody else will want to wait in the car while the scheduled user gets ready. That particular users have commutes at around the same time every weekday, plus or minus half an hour depending on their first meeting and when they finish their work or close their shift or socialize with coworkers, will be better handled by the system placing empty cars appropriately.