CodePush updates control (#3459)

* CodePush updates control

Explains how to have control over launching updates

* Update telegram.md (#3433)

* Update telegram.md

* Update content/yaml-notification/telegram.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Codepush analytics (#3460)

* codepush analytics with other options

* codepush analytics

* api removal

* few more clarifying points

---------

Co-authored-by: Tirth Patel <tirth@nevercode.io>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: 3 people

content/rn-codepush/concepts.md

@@ -74,7 +74,7 @@ CodePush updates this **JavaScript bundle and its assets**. As long as JS remain
 
 ## What can and cannot be updated
 
-✅ Can Be Updated via CodePush (OTA-safe):
+Can Be Updated via CodePush (OTA-safe):
 
 * Fixing JavaScript bugs
 * UI or layout adjustments
@@ -85,16 +85,21 @@ CodePush updates this **JavaScript bundle and its assets**. As long as JS remain
 
 These updates modify only the JavaScript bundle, so they can be safely delivered over the air. 
 
-❌ Require a New App Release
+Require a New App Release
 
 * Adding or modifying native modules
 * Upgrading React Native or native dependencies
 * Editing native configuration files (build.gradle, Info.plist, etc.)
 * Changing app permissions (camera, location, etc.)
 * Adding platform-specific features or integrations
 
- These changes affect compiled native code, so they must go through the App Store or Play Store.
+These changes affect compiled native code, so they must go through the App Store or Play Store.
 
+### Delta updates
+
+CodePush uses delta updates (file-level diffs) for each release and delivers only the JavaScript files and assets that changed.
+
+Instead of redownloading a complete bundle and all static assets on every update, users receive a smaller delta package. This keeps OTA updates faster and reduces bandwidth usage.
 
 ## How the update flow works
 
@@ -113,6 +118,21 @@ The update replaces the previously installed JavaScript bundle while keeping the
 
 If an update fails or causes the app to crash on startup before it is marked as successful, the client can automatically revert to the previous working bundle.
 
+### Prerequisite: a native build with the SDK
+
+Because CodePush relies on the client SDK to check the server, download bundles, and swap the JS layer at launch, **the SDK must already be present in the native binary running on each user's device**. A store build that does not include the SDK cannot install OTA updates — `release-react` will still publish the bundle, but no client will pick it up.
+
+The first time you add CodePush to an existing app, you therefore need to:
+
+1. Integrate the SDK in your React Native project (see [Setup](/rn-codepush/setup/)).
+2. Produce a native build that includes the SDK and the deployment key you want to target.
+3. Install that build on the devices you expect to receive updates — local dev machines or QA devices for **Staging**, App Store / Google Play for **Production**.
+4. Only then start shipping JS changes to that deployment as OTA updates.
+
+For Staging validation this usually just means running a fresh debug build on a test device; no store release is required. For Production, end users must actually update to the new store binary before they can receive anything CodePush publishes.
+
+After that, the usual pattern — occasional native releases for native changes, OTA releases for everything else — applies.
+
 ## Deployment model
 
 CodePush organizes updates using **apps** and **deployments**.

content/rn-codepush/releasing-updates.md

@@ -85,7 +85,7 @@ Think of this as a single pipeline with two decision points:
 
 CodePush delivers only JavaScript runtime assets and the files required by the application’s JS layer.
 
-A typical update includes:
+A typical update includes only changed files and assets, such as:
 
 * JavaScript bundle
 * Static assets (images, fonts, etc.)
@@ -95,6 +95,12 @@ CodePush does not include native binaries such as **.apk** or **.ipa** files. OT
 
 Any modification involving native code (e.g. Swift, Objective-C, Java, Kotlin, or native modules) must be released through the App Store or Google Play.
 
+### Delta updates
+
+CodePush uses delta updates (file-level diffs) for each release and delivers only the files or assets that changed.
+
+This means users download a lightweight delta package instead of the full JavaScript bundle and all assets every time, resulting in faster updates and smaller downloads for users.
+
 ## Version control
 
 CodePush uses a two-layer versioning model that separates native app versions from JavaScript update versions. This ensures updates are only delivered to compatible app binaries while still allowing fast OTA iteration.

content/rn-codepush/setup.md

@@ -176,7 +176,45 @@ function App() {
 export default codePush(App);
 {{< /highlight >}}
 
-This enables the SDK to automatically check for updates on app start (or based on your chosen update strategy).
+This enables the SDK to automatically check for updates on app start (or based on your chosen update strategy). By default, CodePush looks for updates each time the app launches. When an update is found, it downloads it quietly in the background and applies it the next time the app restarts, whether triggered by the user or the operating system. If you want your app to detect updates faster, you can configure it to sync with the CodePush server whenever the app returns from the background:
+
+{{< highlight bash "style=paraiso-dark">}}
+let codePushOptions = {
+  checkFrequency: codePush.CheckFrequency.ON_APP_RESUME,
+};
+
+class MyApp extends Component {}
+
+MyApp = codePush(codePushOptions)(App);
+{{< /highlight >}}
+
+Alternatively, if you need more precise control over when update checks occur—such as after a button tap or at scheduled intervals—you can invoke CodePush.sync() whenever needed with your preferred SyncOptions. You can also disable CodePush’s automatic update checks by setting the checkFrequency to manual:
+
+{{< highlight bash "style=paraiso-dark">}}
+let codePushOptions = { checkFrequency: codePush.CheckFrequency.MANUAL };
+
+class MyApp extends Component {
+  onButtonPress() {
+    codePush.sync({
+      updateDialog: true,
+      installMode: codePush.InstallMode.IMMEDIATE,
+    });
+  }
+
+  render() {
+    return (
+      <View>
+        <TouchableOpacity onPress={this.onButtonPress}>
+          <Text>Check for updates</Text>
+        </TouchableOpacity>
+      </View>
+    );
+  }
+}
+
+MyApp = codePush(codePushOptions)(App);
+
+{{< /highlight >}}
 
 ### CodePush iOS Setup (React Native)
 
@@ -346,13 +384,6 @@ This single command:
 
 For the full release workflow, see [Releasing updates](/rn-codepush/releasing-updates/).
 
-✅ Best Practices
-* Use Environment Variables – Avoid hardcoding deployment keys.
-* Separate Staging and Production Keys – Always validate updates in Staging before promoting to Production.
-* Confirm Connectivity – After configuration, make sure the app can fetch updates from the server by testing a Staging release.
-
-Properly configuring the server URL and deployment keys ensures that CodePush can deliver OTA updates reliably and safely for each platform.
-
 ## Next steps
 
 After completing setup, use the following sections to continue:

content/yaml-quick-start/building-a-react-native-app.md

@@ -274,6 +274,11 @@ If you are going to publish your app to App Store Connect or Google Play, each u
 {{< include "/partials/publishing-android-ios.md" >}}
 
 
+## OTA Updates with CodePush
+
+Our hosted CodePush service lets you publish OTA updates for React Native projects directly to users' devices, without going through the App Store or Google Play. Read the [concepts page](../rn-codepush/codepush-concepts/) for how it works, or the [setup page](../rn-codepush/setup-codepush/) to get started.
+
+
 ## Conclusion
 Having followed all of the above steps, you now have a working `codemagic.yaml` file that allows you to build, code sign, automatically version and publish your project using Codemagic CI/CD.
 Save your work, commit the changes to the repository, open the app in the Codemagic UI and start the build to see it in action.