Localization
Add a new language to a live app without a release
CMSCure team, November 22, 2026
Adding new languages to your mobile or web application traditionally means releasing a new version through app stores or redeploying your website. This process can be slow and delay your ability to reach new audiences. Fortunately, modern development practices and content management tools allow you to update your app's language content remotely, without requiring users to download an update. This approach helps you respond quickly to localization needs and expand your app's reach efficiently.
Why is adding a new language a problem for apps?
When you build an application, all its user interface text, messages, and labels are typically bundled directly into the app package. For native mobile apps, this means the strings.xml file on Android or .strings files on iOS are compiled into the final .apk or .ipa. For web applications, translation files might be part of the build artifacts.
If you decide to support a new language after your app is already live, the traditional method requires you to add all the new translations to these bundled files. Once the translations are in place, you must then rebuild your application and submit it for review to platforms like the Apple App Store or Google Play Store. This review process can take days, and even after approval, it depends on users updating their app to the latest version to see the new language. This delay can be a significant hurdle for product teams and marketers aiming for rapid global expansion or quick fixes.
What are the options for delivering new languages to apps?
To avoid the update cycle, you need a way to deliver content, including translations, over the air. There are two primary approaches for this:
Both methods allow you to add new languages or update existing translations without a full app release. The choice depends on your team's resources and the complexity of your content needs.
- Static content hosting: You can host your translation files on a content delivery network (CDN) or a simple web server. Your app would then fetch these files at runtime, perhaps on startup or when the user changes a language setting. This gives you control over updates, but requires you to manage the hosting, file formats, and the logic for your app to download and parse the content.
- Content management service: A specialized content service can manage your text, translations, and other UI content. Your app integrates with an SDK that fetches this content from the service. When you update translations in the service's dashboard, the changes are pushed to your app in real time. This offloads the infrastructure and content management burden, allowing you to focus on your app's core features.
How can you prepare your app for remote language updates?
Regardless of the delivery method you choose, your application's code must be designed to handle dynamic content. This means avoiding hardcoding any user facing text directly into your UI components. Instead, every piece of text should be referenced by a unique key.
For example, instead of TextView.text = "Hello World", you would use TextView.text = getLocalizedString("greeting_message"). When your app starts, it fetches the appropriate language file or content from a service. Then, when getLocalizedString("greeting_message") is called, it retrieves the correct translation for the current language. This architecture is fundamental for any form of remote content management, including over the air language updates. It also makes your app more maintainable and easier to localize from the start.
Managing your app's languages and translations.
Once your app is set up to fetch content dynamically, you need a system to manage your languages and their translations. A content service like CMSCure provides a web dashboard where you can define all your UI text using keys.
This centralized approach ensures consistency and provides a single source of truth for all your app's UI content across different languages.
- Add new locales: In the dashboard, you can add new languages to your project. For example, you might add Spanish (es) or French (fr) as new locales.
- Define text keys: For each piece of UI text, you create a key, such as welcome_title or button_confirm. You then provide the translation for this key in all your enabled languages.
- AI translation: To speed up the localization process, CMSCure offers built in AI translation. You can use it to fill in missing translations for an entire language or to translate a single key into all supported languages, powered by OpenAI. This can significantly reduce the manual effort involved in adding a new language.
- Collaborate: Teams can invite collaborators with different roles like Admin, Editor, or Viewer to manage translations, ensuring that marketing, product, and localization teams can work together effectively.
Delivering new languages to your users.
With your translations managed in a content service, the next step is to deliver them to your live application. CMSCure provides lightweight SDKs for various platforms, including iOS, Android, React Native, and JavaScript.
This real time delivery mechanism is crucial for agile localization, allowing you to deploy new languages or correct typos in existing ones within seconds, without any app store review delays.
- Initial fetch: When your app starts, the SDK fetches all the necessary UI content, including translations, for the current language.
- Real time updates: When you publish changes in the CMSCure dashboard, such as adding a new language or updating a translation, these changes are pushed to your app in real time over WebSockets. This means users do not need to restart their app or download an update to see the new content.
- Language switching: If a user changes their preferred language within your app, the SDK can immediately load the corresponding translations, making the switch instant.
What about other content types?
While adding new languages is often about text, modern apps also use other UI elements that might need to change remotely. A content service can extend beyond just text.
By centralizing these content types, you gain comprehensive control over your app's UI and content, making it highly adaptable to changes and new market requirements.
- Colors: Define hex color keys with nicknames and update them remotely. This is useful for theme changes or brand updates.
- Images: Upload, replace, and crop images. Your app can fetch image URLs dynamically, allowing you to update banners, icons, or product photos without an app update.
- Data stores: Create structured collections of data with a schema. These can include translatable fields, allowing you to manage dynamic lists, product catalogs, or news feeds that are localized and updated remotely.
When might a traditional update still be needed?
While remote content delivery offers significant advantages, it is important to understand its limitations. Not everything can or should be updated over the air.
A content service focuses on managing and delivering UI content, not code or app structure. It complements your app development workflow by decoupling content updates from code deployments.
- Code changes: Any changes to your app's underlying logic, new features, bug fixes that affect functionality, or updates to third party libraries require a new app build.
- UI layout changes: If you are adding entirely new screens, significantly restructuring existing layouts, or introducing new UI components that are not driven by simple content changes, an update is necessary.
- Platform specific requirements: Major operating system updates or new device capabilities might necessitate an app update to ensure compatibility or to take advantage of new features.
- SDK updates: If the SDK itself needs an update for new features or critical bug fixes, your app will need to incorporate the new SDK version and be re released.
Frequently asked questions
Can I add a language to my app without an update if I use static files?
Yes, if your app is designed to fetch and parse external language files at runtime. You would update the files on your server, and your app would download them.
Does CMSCure support AI translation for new languages?
Yes, CMSCure includes AI translation powered by OpenAI to help fill missing translations for a language or translate a single key across all languages.
Are there limits to how many languages I can add?
CMSCure plans have limits on the number of locales per project, for example, 3, 5, or 10 depending on your plan.
Can I update images and colors remotely too?
Yes, CMSCure allows you to manage and update image URLs and hex color values remotely, which your app can fetch and apply without an update.
Is real time content delivery secure?
CMSCure uses HTTPS for all traffic, and its SDK WebSocket handshake is encrypted with a project secret (AES-256-GCM) to ensure secure content delivery.
Does CMSCure offer a visual editor for translations?
CMSCure provides a web dashboard for managing text keys and their translations, but it does not offer an in context visual editor for app screens.