How Patch Updates Works

Learn how React Native Stallion's Patch Updates automatically generates differential updates, version targeting, and patch delivery. Technical overview of patch generation and delivery.

How Patch Updates Works

Patch Updates works automatically in the background, requiring no changes to your existing React Native OTA workflow.

Automatic Patch Generation

Step 1: Upload Releases as Usual

Build your React Native bundle and upload it to React Native Stallion using the CLI. No special configuration needed for differential updates.

Step 2: Automatic Patch Creation

When you promote a release, a patch is automatically generated with the previous version:

  • Advanced Binary Diff Algorithms: The system intelligently compares your new release with the previous one
  • Optimized Differential Update: Creates a patch containing only the changes
  • File-Level Analysis: Analyzes changes at the file level for optimal patch sizes

Step 3: Version Targeting

For example, if you release version 4:

  • A patch is automatically generated between version 3 and version 4
  • All users on version 3 automatically receive the patch update
  • Users on older versions receive full bundles

First Release Behavior

Important: The first release on an app version (V1) is not patched, as the default bundle was shipped with the app build itself.

All incremental versions after V1 will be delivered as patches:

  • Default (shipped with app): Included in app build
  • V1 (first release): Users download the full bundle
  • V2: Users on V1 receive a patch update
  • V3: Users on V2 receive a patch update
  • And so on for all subsequent releases

First Release on App Version:

The first release on an app version is not patched, as it was shipped with the app build itself. All incremental versions after the V1 release will be delivered as patches.

Current Limitations

Patch Updates currently supports patching between consecutive versions. If you release version 4, users on version 3 will receive the patch.

Future releases will expand this capability to support patching between older versions.

User Experience

From the user's perspective, nothing changes. They still receive updates automatically, but now those updates are dramatically smaller and faster. The only difference users notice is that updates are dramatically faster.

Example Workflow

  1. Initial Release (V1):

    • Upload and promote version 1
    • Users download the full 20 MB bundle

  2. Second Release (V2):

    • Make a small bug fix and upload version 2
    • System automatically generates a patch between V1 and V2
    • Patch size: ~400 KB (98% smaller)
    • Users on V1 receive the 400 KB patch
    • Users on older versions receive full V2 bundle

  3. Third Release (V3):

    • Add a new feature and upload version 3
    • System generates a patch between V2 and V3
    • Users on V2 receive the patch
    • Users on V1 receive full V3 bundle (not consecutive)

Conclusion

Patch Updates works automatically in the background, requiring no changes to your workflow. The system intelligently generates optimal patches, ensuring users get the fastest possible updates with minimal bandwidth usage.

Learn how to get started or explore monitoring to track patch efficiency.