Skip to main content

TkushPatch Glossary

This glossary defines key concepts and vocabulary used across TkushPatch, the tk-ota-push CLI, and the tk_ota_push Flutter SDK.


A​

AOT (Ahead-Of-Time Compilation)​

The production compilation mode used by Flutter. Dart source code is transformed into native machine code prior to app installation for optimal runtime performance.

Application ID (app_id)​

The unique identifier of your mobile application (e.g., com.company.banking), corresponding to the package name on Android and bundle identifier on iOS.


C​

Canary Cohort (Rollout Bucket)​

A deterministic assignment calculated from a device's unique identifier. Ensures that a device included in an initial rollout cohort will consistently remain eligible as rollout percentage increases.

Canary Rollout (Staged Rollout)​

Progressive patch distribution strategy targeting controlled fractions of users (e.g., 5% → 25% → 50% → 100%), limiting blast radius in case of regressions.

Channel​

Logical delivery tracks (staging, stable, or custom). Each channel carries its own targeting rules and security policies.


D​

Device Registry​

Fleet inventory of mobile clients that have checked in with TkushPatch, recording active patch numbers, hardware models, channels, and health state.


K​

Kill-Switch (Emergency Rollback)​

Administrative action that immediately stops patch distribution and commands mobile clients to revert to the safe base release.


M​

Maker-Checker (Four-Eyes Principle)​

Enterprise governance policy requiring that a patch created by a developer (Maker) must be approved by a distinct authorized team member (Checker) before production release.


P​

Patch (Over-The-Air Update)​

A compressed binary differential containing Dart code changes, digitally signed for authenticity and activated on mobile devices without going through app stores.

Patch Number (patch_number)​

A strictly increasing integer (1, 2, 3...) identifying each patch published for a given release version.


Q​

QA Device Whitelist​

List of authorized device identifiers eligible to receive test updates on internal and pre-production channels (staging).


R​

Release (Base Binary)​

The complete application binary (.apk, .aab, .ipa) published on official app stores, acting as the base reference for incremental patches.

Release Version (release_version)​

Official application version string (e.g., 1.4.0+42). Every patch is strictly tied to an existing base release.

Rollback​

Action of revoking an active patch across the fleet and restoring devices to their previous verified stable state.


S​

Store Review Shield​

Protection mechanism that automatically suspends OTA updates on public tracks while a new version is under review by Apple or Google, preventing review rejections.


T​

Target Countries (Geo-Targeting)​

Distribution policy restricting patch availability to specified countries (ISO 3166-1 alpha-2 codes).

Tenant (Organization)​

An isolated workspace containing an enterprise's mobile applications, team members, security policies, and credentials.