The most standard localization package, flutter_localizations, requires developers to store their translations locally on their apps in addition to writing a lot of boilerplate code and following a tedious setup process. Surprisingly, there are not many out of the box solutions in Flutter that support real-time updates. A world where your team needs to release new app updates whenever you modify existing translations and add new locales hardly seems efficient or a good use of an engineer’s time. One of the important steps towards providing a scalable localization approach is supporting real-time updates. When localizing your apps, it is important to think about the future. Having multiple engineers, product managers, and translators downloading and editing one or several files is certainly not scalable when you have over a hundred strings and ten locales. Unless your engineering team is multi-lingual, you will also need to utilize professional translation services. You will most likely need to support new locales and translations as you add new features and expand your customer base across different regions.
What some engineers fail to realize is that the process of localizing your apps does not stop after translating all of the text on your apps. Many of the existing packages for this task require a lot of time to setup and certainly do not come with any UI tools for updating translations, especially in real-time. Initially, the process to localize your apps can be both daunting and confusing. We needed to localize our mobile apps to support deployments in countries outside of the United States, where English is not the primary language.
#Flutter language localization software
To provide some context: I am a software engineer at The Routing Company, a startup that partners with cities to build smart, sustainable transit solutions.
In this blog post, I will outline certain techniques that I found helpful for localizing Flutter apps.
0 kommentar(er)
