[kmeisthax]

Uber is a bad example because they need to have support for literally every payment method on the planet. And all of that needs to be preloaded ahead of time just in case the user decides they're going to fly to Mumbai tomorrow. Their app absolutely needs to be bloated or it won't work at all.

Likewise, Amazon needs to run on all sorts of different smart TV platforms, not just iOS and Android. All of those apps need to be consistent to each other, rather than to their host platforms. That's almost the textbook case for using a cross-platform framework.

[saagarjha]

> Their app absolutely needs to be bloated or it won't work at all.

It really doesn’t. I remember this being brought up back when the Uber engineer crying about how their compiler couldn’t match their scale was making the rounds, and in the end the numbers just did not add up to support the app size they have right now.

> All of those apps need to be consistent to each other, rather than to their host platforms.

Why? Platform-specific apps, for the most part, should feel at home on their platforms. Not doing this is how you get YouTube for Apple TV and similarly bad apps.

[littlestymaar]

> Uber is a bad example because they need to have support for literally every payment method on the planet.

How is the breadth of their payment back-end and excuse for a bloated client?

[ksec]

>And all of that needs to be preloaded ahead of time just in case the user decides they're going to fly to Mumbai tomorrow.

This is Interesting. So essentially Uber is a "Global" App by default?

[sofixa]

Yes, that's why it works everywhere* with local specifics ( e.g. proposing tuk-tuks where available, or bike rentals where Uber have the service or a partner, etc.) directly without new downloads or anything.

* of course where Uber are on the local market, i doubt it works in North Korea