Localization

Over the Air Translations in React Native (Expo and Bare)

CMSCure team, November 15, 2026

Updating your React Native app's translations over the air means changing text in users' hands without requiring a new app store submission. This approach can significantly speed up localization efforts and content updates. You can achieve this through either code-based updates or dedicated content management solutions.

What are over the air translations in React Native?

Over the air (OTA) translations refer to the ability to modify the text displayed in your React Native application after it has been installed on a user's device, without needing them to download an update from an app store. This capability is crucial for agile product teams and marketers who need to react quickly to feedback, fix typos, or adapt messaging for different regions or campaigns.

There are two primary ways to implement OTA updates in React Native: through code-based updates and through content-based updates. Code-based updates typically involve pushing new JavaScript bundles that contain updated strings, while content-based updates fetch text from a remote service, allowing for more granular control over UI content separate from the app's core logic. Understanding the distinction helps you choose the right tool for your specific needs.

Why update translations over the air?

The traditional method of updating app content involves submitting a new version to the Apple App Store and Google Play Store. This process can take days, or even weeks, due to review times and user adoption rates. For translations, this delay can be particularly problematic, slowing down localization efforts and delaying market entry for new languages or features.

Over the air updates bypass this lengthy process. They allow you to deploy text changes instantly, ensuring your app always displays the most current and accurate translations. This agility is invaluable for A/B testing different messages, correcting errors quickly, or responding to urgent market demands without waiting for app store approvals. It also reduces the burden on developers, as content changes can be managed by product or marketing teams.

How do code-based OTA updates work in React Native?

Code-based OTA solutions, such as Expo EAS Update or Microsoft CodePush, enable you to push updates to your app's JavaScript bundle directly to users' devices. When you make changes to your app's code, including translation files embedded within the bundle, these services can deliver the new bundle. The app then downloads and applies the update, often on the next launch or in the background.

For translations, this means your localized string files (e.g., JSON, YAML, or JavaScript objects) are part of your app's source code. When a translation needs to be updated, a developer modifies the relevant file, rebuilds the JavaScript bundle, and pushes it through the OTA service. While effective for code changes, this approach still tightly couples content updates with development cycles and requires a full app restart to apply the new bundle, which might not be ideal for every user experience.

What are the limitations of code-based OTA for translations?

While powerful for code deployment, using code-based OTA for translations has specific drawbacks. First, it often requires a developer to initiate and manage the update process. Product managers or localization specialists might not have direct access or the technical expertise to push these updates independently, creating a bottleneck.

Second, every translation change, no matter how small, typically results in a new JavaScript bundle being downloaded. This can increase bandwidth usage for users and potentially lead to larger app sizes over time. Finally, these updates usually require the app to restart for the changes to take effect, which can interrupt the user's flow. For dynamic content like UI text, a more immediate and less disruptive update mechanism is often preferred.

How do content-based OTA updates work for translations?

Content-based OTA solutions separate your app's UI text and other content from its core code. Instead of embedding translations directly into the app bundle, your React Native app fetches them from a remote content service. This service provides a dashboard where non-technical users, like product managers or translators, can manage and publish content.

When content is updated and published in the dashboard, the changes are immediately available to your app. Many services use real time push mechanisms, like WebSockets, to notify your app of new content, allowing it to update text without a restart or even a manual refresh. This approach gives content owners direct control over translations and other UI elements, making the localization process much more agile and independent of development cycles.

How CMSCure helps with React Native over the air translations?

CMSCure is a hosted content service designed for app UI content, including over the air translations for React Native. Teams define keys for text, colors, images, and structured data stores in a web dashboard. You can then translate these keys into several languages, with AI translation built in to fill missing translations or translate a key across all languages using OpenAI.

The CMSCure React Native SDK (`@cmscure/react-native-cmscure-sdk`) fetches this content and receives live updates over WebSockets when you publish changes. This means copy, translations, colors, and images can change in your shipped app without requiring a new release or app store review. The dashboard also offers features like draft and publish workflows, per key revert, and activity logs, giving content teams full control.

While CMSCure is UI-first and not a full headless CMS with page modeling, it provides essential features for dynamic app content. For Pro tier projects, you can also access versioning and rollback for text, colors, and data store items, as well as scheduled publishing. This allows for precise control over content deployment, ensuring your app's UI is always current and localized effectively.

When should you use content-based OTA solutions?

Content-based OTA solutions are ideal when your app's UI text and other content need frequent updates, or when non-developers need to manage these changes directly. This is particularly true for marketing messages, product descriptions, legal disclaimers, or any text that might change based on user feedback or market conditions. If your localization process involves multiple languages and frequent iterations, a content service can significantly reduce overhead.

Consider a content-based solution if you need:

<ul><li>Instant updates to app text without app store submissions.</li><li>Non-technical team members to manage translations.</li><li>AI assistance for translation workflows.</li><li>Real time content changes without app restarts.</li><li>Centralized management for text, colors, and images.</li></ul>

CMSCure fits these scenarios by providing a dedicated platform for managing and delivering UI content. It helps teams maintain consistent branding and messaging across all languages, while keeping the app experience fresh and responsive to user needs.

Choosing the right OTA strategy for your React Native app

The best over the air strategy for your React Native app depends on your team's structure, update frequency, and the type of content you manage. If your updates are primarily code-related and translations are static, a code-based OTA solution like Expo EAS Update might suffice. However, if you need dynamic UI content, frequent localization updates, or want to help content teams, a content-based OTA service is a more suitable choice.

For teams focused on agile content delivery and localization, separating content from code offers greater flexibility and speed. Solutions like CMSCure allow developers to focus on app functionality while product and localization teams manage the user-facing text. By carefully evaluating your requirements, you can select an approach that optimizes your development workflow and enhances the user experience with up-to-date, localized content.

Frequently asked questions

Can I update React Native app text without a new release?

Yes, you can update React Native app text without a new app store release using over the air (OTA) update methods. This can be done either by pushing new JavaScript bundles with updated text or by fetching content from a remote content service.

What is the difference between code OTA and content OTA?

Code OTA updates deliver new JavaScript bundles containing code and embedded text, often requiring an app restart. Content OTA updates fetch text and other UI content from a remote service, allowing for real time changes without code deployments or app restarts.

Does Apple allow over the air updates for React Native?

Apple's App Store Review Guidelines generally permit over the air updates for JavaScript-based apps like React Native, provided the updates do not change the primary purpose of the app or introduce functionality that requires a new review.

How does AI translation work for app content?

AI translation services, like those built into CMSCure, use artificial intelligence to automatically translate text keys into various languages. You can use it to fill missing translations for a language or translate a single key across all languages, speeding up the localization process.

Is CMSCure suitable for full headless CMS needs?

CMSCure is a UI-first content service focused on app UI content like text, colors, images, and data stores. It is not a full headless CMS with visual page builders, page modeling, or extensive content workflows, but it excels at managing dynamic UI elements.

Related features

Related guides

Ready to stop waiting on UI releases?

Read the docs to see how fast you can integrate, or start building with CMSCure today.

React Native Over the Air Translations | CMSCure