3 ms·
> 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?
by adwn 3y ago
> 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.
- SOLAR_FIELDS 3y agoThe simple example I gave in a sibling comment is that in India you have the option to call a tuktuk or a scooter which has a whole different guide set, flow, more screens. And lots of different airport specific, town specific, county specific, country specific regulations about things that need to be shown, taxes, etc. For all of that to be seamlessly available as you travel you need to be downloading a pretty large bundle upfront. Else you end up in a situation where you need the service’s reliability the most (travelling in a foreign country) and not being able to use it easily (because you have crappier data from bad infrastructure or a cheap SIM card and can’t download a location specific bundle)
- namrog84 3y agoIn the case of uber. Maybe they have a local list of every city and street of thr world localized on device?
- canucker2016 3y agoThis "localization" also includes the code for online payment methods available in a particular locale. 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...