[Due for payment 2026-01-09] Optimize loading EN/ES translations

[mountiny]

Coming from this thread

Background:

The App supports multiple languages, most of the users use fully supported EN or ES and rest of the languages are in "beta" and are AI-generated. System uses an IntlStore class that manages translation files and date-fns locales for each supported language.
Locale files are loaded via dynamic imports when the user's preferred locale is determined. The app tracks bootsplash screen performance using Sentry telemetry spans. The BootsplashVisible root span contains several child spans including BootsplashVisibleLocale, which measures the time from when locale loading begins until translations are ready for use. The bootsplash screen remains visible until multiple conditions are met and one of them is loaded locale file. Sometimes there are spikes where locale loads for >1s extending the splash screen visibility.

Let's look into production sentry logs.
Last 7 days:

• David account: avg BootsplashVisibleLocale: ~ 1.62s
• Vit account: avg BootsplashVisibleLocale: ~1.25s

Problem:

When the app starts, if dynamic imports are used for all locale files, the time to load translations increases, which may extend the splash screen duration for users.

Solution

MoveLocaleContextProvider higher up the tree as discussed here

Issue Owner

Current Issue Owner: @garrettmknight

[melvin-bot]

Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[Be-Avatar]

Dynamic imports of locale files sometimes extend the bootsplash (BootsplashVisibleLocale), especially for beta locales.
Propose moving LocaleContextProvider higher in the tree to reduce blocking, and optionally lazy-load beta locales after the main UI is ready.
This will verify improvements via Sentry spans and test on iOS, Android and Web.

[melvin-bot]

📣 @Be-Avatar! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[melvin-bot]

✅ Contributor details stored successfully. Thank you for contributing to Expensify!

[melvin-bot]

⚠️ Invalid email. Please make sure to create an Expensify account with this email first here.

[Be-Avatar]

Contributor details
Your Expensify account email: beimnet602@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~01d8ad15752bf42475