Context and Problem Statement
At what point in the app operational process will clients consume localized copy / static text, such that they can display the correct language’s text to the user?
Decision Outcome
TBD
Considered Options
- Build Time
- Run Time
- Both Build and Run Time
Pros and Cons of the Options
Build Time
The client apps will fetch the entirety of static localized text at some point during the build process, resulting in all texts being available at any point during run time of the app.
- Good, because the user will not have to wait for texts to load
- Good, because the complexity added for localization is kept to a minimum
- Bad, because the apps need new deploys to pull in updated localizations
Run Time
The client apps will delay fetching of any texts until run time, pulling up-to-date texts on demand while the app is running.
- Good, because the apps will always have the most up-to-date translations and new localized texts
- Bad, because the user will have to wait while these texts are fetched
- Bad, because the apps would need a significant restructure to accommodate this requirement
Both Build and Run Time
The client apps will include the most up-to-date texts when they are built and deployed. They will also pull up-to-date texts on demand while the app is running.
- Good, because the apps will always have the most up-to-date translations and new localized texts
- Good, because the user will not have to wait for the texts to load
- Bad, because this is an enormously costly endeavor, combining the engineering costs of the other two options
- Bad, because of the complexity added by this option invites issues within the app and introduces engineering friction