Hacker News new | past | comments | ask | show | jobs | submit login

This comment got my gears turning about good ways to split up Uber in an anti-trust case. One possibility is to have Uber A provide dispatch as a service, while Uber B collects fares, disburses driver payments, and provides the front-end UI. Uber B could also set up whatever driver incentives they wanted. Uber A would be a regulated monopoly, and would have to allow other companies to compete with Uber B on its platform.

In this scenario, dispatch would basically be a public utility, and drivers could trust the algorithm not to cheat. I.e. since Uber B and its competitors would be running any driver incentives, Uber A wouldn't even know about it. (And legally shall not know such things.)

I realize this is a half-baked pipe dream, but an interesting thought experiment.




> Uber A would be a regulated monopoly, and would have to allow other companies to compete with Uber B on its platform.

But since Uber B has the brand recognition (through its UI), the question is if there will be a competitor. Nowadays, it seems that consumers converge more and more on a single brand for any service/product, which is probably due to the internet/social media.


>Nowadays, it seems that consumers converge more and more on a single brand for any service/product, which is probably due to the internet/social media.

This only seems true (at least over medium to longer times) for certain classes of product/service, namely those where network effects actually provide real value to consumers. Many products have tried to artificially integrate features that would initiate network affects (for example niche social networks for fitness trackers) but they end up making the product less usable because they're not part of the core value proposition consumers are looking for with that product.


usually "free" products where the consumer is paying in time watching ads and the user can't determine easily how much the "value" actually has changed. ie. no ads --> lots of ads




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

Search: