Earlier quoted context omitted.
Uber actually had a pretty reasonable explanation for their app being huge when their rather large app size made the rounds several years ago. Turns out localization takes a lot of space. I wonder how much of LinkedIn’s insane size can be attributed to that vs just lazy coding
> Turns out localization takes a lot of space. Does localization involve more than a few hundred strings per locale, all of which should compress really well? Maybe add in some localized icon sets, but much fewer than the number of supported locales. I'm not saying you're (or they're) wrong, I'm genuinely curious.
So for the traveler, when they arrive in a new area that's supported by Uber, the app will just work instead of a "Please wait while we download the necessary payment SDK for your current location..." notification.
You didn't just download Uber "for USA" - you've downloaded Uber for "all countries where Uber exists" just in case you might leave your home area and travel a location that Uber operates.
Testing matrix must be complex...