4 ms·
Past discussion on why Uber's app is so big, many of the points are relevant: https://news.ycombinator.com/item?id=25376346 https://news.ycombinator.com/item?i
by david_allison 4y ago
Past discussion on why Uber's app is so big, many of the points are relevant:
https://news.ycombinator.com/item?id=25376346 https://news.ycombinator.com/item?id=25376346
- jrvarela56 4y agoThis comment is a gem. Every HNer who has thought 'why do they need 100 engineers, I could do that in a weekend' should go read this now.
- criddell 4y ago> why do they need 100 engineers You're off by an order of magnitude. Hundreds of developers? Sure. But Uber has thousands of developers.
- jrvarela56 4y agoI think the point stands: the amount of complexity involved in each little piece of app is huge when taking into account dozens of countries and customizations by city. If it still doesn't seem worthy of 'thousands of engs', imagine breaking down every point in the list to the level of detail the author broke down payments. And then apply the logic in the top comment mentioning backend systems + teams to support other processes (and internal tools needed). Edit: sorry too much caffeine got me edgy.
- naikrovek 4y agoI feel like 10 million lines is still massive, given all of the points mentioned in that comment. UI pages must be immense in terms of lines of code.
- awinter-py 4y agointeresting how much of this is glue -- like if mobile had better support for inter-app handoff, these flows could be entirely delegated to external provider's app (paypal, venmo, support saas) (though hard to generalize to other parts of the app, bc payments is inherently glue-y) constantly wonder what kind of support layer would make UX integration user-friendly, but also developer-friendly