Remote app text

Change app text live without an app store release

Update labels, titles, error messages and other UI text in your iOS, Android, React Native or web app from one dashboard, live in seconds, with no new build.

The problem

In most apps, UI text is compiled into the build. Fixing a typo, renaming a button or changing a promo line means a code change, a new build, an app store submission and a review queue, and users only see the change after they update. CMSCure moves that text out of the build so it can be changed from a dashboard and published right away.

Who it is for

  • Product managers and marketers who want to change copy without waiting for a release
  • Developers who want to stop shipping builds for text fixes
  • Teams that support several languages and want every string in one place
  • Apps on iOS, Android, React Native and the web that should show the same copy everywhere

How it works

  1. 1

    Create tabs and keys

    In the dashboard, create a tab for a screen (for example home_screen) and add a key for each piece of text (for example welcome_title or cta_button), with a value for every language you support.

  2. 2

    Add the SDK

    Install the SDK for iOS, Android, React Native or JavaScript and configure it once, early in the app lifecycle, with your Project ID, API key and project secret.

  3. 3

    Read text through the SDK

    Bind each string to its key, for example with a CureString wrapper in SwiftUI or cure.observe('home_screen:welcome_title', callback) on the web, and pass a default value for the first launch.

  4. 4

    Edit and publish

    Change the value in the dashboard and publish. Connected apps receive the update over WebSocket and the bound UI changes on its own, with no manual refresh.

Real time updates

When the SDK is configured with a project secret, it keeps a WebSocket connection open. Publishing in the dashboard pushes the change to every connected app, and reactive bindings such as SwiftUI CureString or web observe() update the UI by themselves.

Translations and language switching

Each key holds a value per language and the SDK returns the value for the active language. Calling setLanguage at runtime switches every bound string at once. The dashboard also offers AI translation suggestions for new languages.

Offline and caching

The SDK caches content on the device (localStorage on the web, UserDefaults on iOS). When the app is offline it shows the last published text, and it syncs again when the connection is back.

Control over changes

Team roles (Admin, Editor and Viewer) decide who can edit content. On the Pro plan, every published version is kept so you can roll back in one click, and changes can be scheduled for a future date and time.

More than text

The same workflow covers global colors, images and structured data stores such as product lists, news feeds or FAQs.

Set it up

The documentation covers installation and code for every SDK.

Read the docs

Frequently asked questions

Do I need a new app version to change text?

No. Once the SDK is in your app and your text is read from CMSCure keys, published changes reach the app without a new build or app store review.

What does the app show when the device is offline?

The SDK shows the content cached on the device from the last sync, and fetches the latest version when the device is back online.

Which platforms are supported?

SDKs are available for iOS, Android, React Native and JavaScript. Unity and Flutter are on the way.

Can non technical teammates edit the text?

Yes. Marketing, product and content teams can update text from the dashboard. Invite them as Editors so they can change content without admin access.

Guides

Comparisons

Ready to stop waiting on UI releases?

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

Change app text without an app store release | CMSCure