[skobovm]

This is a weird take, and I highly doubt retention is the primary reason they choose to limit the use of their web interface. In fact, I’m generally suspect of the hand-wavy speculation that some less savvy business unit made a decision in isolation. The two drivers that I would expect are: reducing friction and native compute capabilities.

People generally gravitate towards the path of least resistance, which is something you already see companies exploiting with things like unfavorable privacy settings defaults. Having an app is another instance of that. There is much less mental friction in pushing a button on a home screen compared to opening a browser, punching in a URL, possibly having to log in, etc.

Given that this is rideshare, this is important, because the services offered by other companies are effectively identical. If someone has Uber installed, they would be much more likely to go the path of least resistance — using the installed app — as opposed to going out of their way to use an equivalent offering.

Additionally, there are problems in mapping that would be very difficult, if not impossible, to solve in a browser. For example: localization (precise positioning) would be incredibly difficult without a native library, you wouldn’t be able to do any offline re-routing, like gmaps does, among other limitations.