Android

dependencies {
  // Compose
  implementation("io.rerune:rerune-android-compose:1.8.0")
  // Views
  implementation("io.rerune:rerune-android-views:1.8.0")
}

Choose the Compose or Views dependency for your app module and enable Maven Central. Keep your strings.xml and plural resources. You no longer need a packaging rule for license files. ReRune no longer includes OkHttp: if your app used OkHttp only because ReRune brought it in, add it to your own dependencies. The public example apps use the same 1.8.0 release.

1. Initialize ReRune.setup in the Application with the project read-only OTA Publish ID.
2. Wrap the activity base context with newBase.reRune() so native resource lookup can resolve delivered strings.
3. For Views, install ReRuneViews in the Application and rebind existing widget text when strings update. XML layouts are localized in activities with a layout inflater factory, such as every AppCompatActivity. Styled app strings keep their own text in getText and XML; OTA text replaces them through getString.
4. For Compose, wrap the whole content of each setContent in reRuneObserveRevision. It refreshes ReRune texts in place, so remembered state, scroll positions, and text fields stay.

The runnable examples show the complete Application and Activity wiring. Compose uses reRuneObserveRevision; Views uses reRuneOnStringsUpdated with a lifecycle scope. Copy the setup for your SDK version together with its imports and lifecycle handling.

The fragments below belong in your existing Application and Activity. Register the Application class in AndroidManifest.xml. For Views, install the integration in Application.onCreate and add the update listener after view binding is initialized. Replace binding.title and R.string.title with your actual view and resource. SDK imports use rerune.ReRune and rerune.reRune; UI hooks are in rerune.compose and rerune.views.

ReRune.setup(
  app = this,
  otaPublishId = "<READ_ONLY_OTA_PUBLISH_ID>",
)

override fun attachBaseContext(newBase: Context) {
  super.attachBaseContext(newBase.reRune())
}

reRuneObserveRevision {
  Text(text = stringResource(R.string.title))
}

ReRuneViews.install(this)

binding.title.text = getString(R.string.title)
reRuneOnStringsUpdated(lifecycleScope) {
  binding.title.text = getString(R.string.title)
}

• Android setup and runnable examples

Continue using native resource identifiers in application code. Keep bundled resources for offline fallback and ensure quantity arguments match your plural resources. Rebind or recompose existing UI after an update; fetching data alone does not rewrite text already assigned to a widget. In Compose, a text read outside composition and kept, for example in a ViewModel or in a remember block without keys, is not refreshed; key that remember with ReRune.revisionFlow. The ReRuneUnkeyedRememberText lint check flags such code. After a switch to a language that is not loaded yet, the app shows its own text until ReRune loads it, then ReRune.revisionFlow increments.

Dashboard-managed languages can appear after a successful fetch. Use runtime locale availability for an in-app picker. On Android 14 and newer, the SDK can also update the system per-app language list through LocaleConfig. New resource IDs, application code, and store metadata still require their normal release or store update.

• Preview drafts with OTA staging

1. Start with local resources and confirm the app renders without a network connection.
2. Publish a changed value for an existing key and use the correct project OTA ID.
3. Trigger an update check and confirm both newly created and already visible UI display the expected text.
4. Restart offline after a successful fetch to check cache restoration.