Skip to main content

How OTA Updates Work

TkushPatch delivers instant code updates to production Flutter mobile applications without requiring App Store or Google Play re-validation.


1. Operating Principle​

Over-The-Air (OTA) updates rely on sending optimized binary diffs:

  1. Automatic Check: The mobile app queries the TkushPatch server on startup or in the background to check if an update is available for its release.
  2. Eligibility & Targeting: The server evaluates delivery policies (staged rollout percentage, target countries, track) and returns patch metadata if the device is eligible.
  3. Optimized Download: The app downloads only a lightweight compressed patch (a few hundred kilobytes) instead of an entire multi-megabyte app package.
  4. Integrity & Signature Verification: Before any local installation, the app validates the digital signature and cryptographic hash of the patch.
  5. Seamless Activation: The patch is prepared in the background and activated smoothly on the next app restart.

2. Update Flow​

StepClient Action (Mobile)Server Action (TkushPatch)
1. CheckApp sends current release version and target architecture.Server evaluates rollout rules, patch status, and governance.
2. DecisionIf no patch is available, execution continues normally.If an eligible patch exists, server returns secure download metadata.
3. DownloadApp downloads the compressed patch file in the background.Server logs delivery metrics for real-time fleet analytics.
4. ValidationApp verifies the digital signature to ensure authenticity.—
5. ActivationPatch is stored locally and activated on next launch.Installation success events are reported to the web dashboard.

3. Built-in Security and Safeguards​

Security is enforced at every step of the delivery lifecycle:

  • Cryptographic Signatures: Every patch is digitally signed before distribution. Devices strictly reject any tampered or unverified files.
  • Strict Version Binding: Patches are tied to specific release versions and cannot be cross-applied.
  • Instant Rollback (Kill-Switch): If an issue occurs, operators can revoke a patch instantly, returning devices to the base release.