This article explains the risks of editing code directly in the pre‑release environment, outlines a standard multi‑environment branch workflow, and provides a step‑by‑step guide for creating and merging hotfix branches to ensure traceable, safe releases.
To improve QiYiGuo TV’s rapid issue resolution, the team adopted Robust as the core hot‑fix engine and extended it with KRobust to handle reflection, Kotlin methods, enum‑switch mapping, and native‑library swaps, while building an automated deployment platform that now achieves over 95% fix rate and reduces average repair time from three days to under 24 hours across hundreds of channel APKs.
This article explains how Baseline Profiles improve Android app start‑up performance, analyzes three major obstacles—unsupported app stores, dex‑crc mismatches caused by code‑obfuscation, and hot‑fix dex incompatibility—and provides concrete solutions including active optimization, dex‑name correction tasks, and profile injection during patch synthesis.
This article presents a comprehensive overview of a mobile hot‑update solution for Android, covering its motivation, goals, technical selection of Tinker, comparative analysis of existing frameworks, system architecture, implementation steps, usage workflow, and the benefits it brings to rapid bug fixing and minor version releases.
This article details ZA Bank’s implementation of a Flutter hot‑fix solution, describing the evaluation of various approaches, the selection of a FlutterWeb‑based page‑downgrade strategy, the design of backend patch management, challenges such as font loading and package size, and the resulting high fix rate and performance improvements.
Microsoft intends to introduce hot‑fix style cumulative updates for Windows 11, allowing most monthly updates to install without a reboot while still requiring restarts for quarterly releases, thereby improving update efficiency and security for both consumer and enterprise users.
The article explains how Meituan migrated its method‑instrumentation hot‑fix system Robust from ProGuard to Google’s R8 by moving change detection ahead of optimization, disabling or tuning R8’s built‑in optimizations, and implementing special handling for anonymous classes, inlined methods, super calls, constructors and static initializers to ensure reliable patch generation.
This article describes a comprehensive crash governance framework for a fast‑growing mobile app, covering monitoring, root‑cause attribution, systematic remediation steps, and detailed case studies—including MIUI system bugs, 32‑bit address‑space limits, memory corruption, and WebView crashes—while outlining future challenges and automation strategies.
This article explains how git‑worktree, a feature introduced in 2015, lets developers maintain a single repository while working on multiple branches or hotfixes simultaneously, covering common scenarios, command usage, directory structures, branch‑naming pitfalls, and cleanup procedures.
This article describes how the JAYE 2.0 project at Beike leverages abstract syntax tree (AST) generation, a custom runtime interpreter, and Dart VM execution to achieve high‑performance, hot‑fixable dynamic updates for Flutter applications, addressing packaging, hot‑reload, and scalability challenges.
This article explains the concept of edge (client‑side) computing, demonstrates how to design a generic framework for fixing tracking data issues without consuming server resources, and shows practical improvements to the DinamicX engine for more flexible, data‑driven mobile applications.
This article explains why Android hot‑fixes are needed, describes the structure and generation of class and dex files, compares popular hot‑fix frameworks such as Tinker and AndFix, and provides practical guidance on integrating and managing hot‑fix solutions in mobile apps.
This tutorial walks through the principles of Android hotfixing, explains class loaders, and provides a complete hands‑on implementation—including a buggy class, a custom Dex loader, patch creation, and runtime injection—so developers can quickly patch bugs without releasing a full app update.
This article details the evolution of Alipay's mobile architecture into a super‑app, explains the engineering and business complexity challenges, describes the layered framework, micro‑application and service mechanisms, the role of mini‑programs, agile release processes, dynamic hot‑fix techniques like AndFix, and how the mPaaS platform externalizes these capabilities.
This article explains how Alibaba's Sophix hot‑fix framework trims Android resource patches by analyzing and reconstructing the resources.arsc string pools, removing unused entries, and re‑indexing references, achieving dramatic size reductions while preserving runtime performance.
This article chronicles Alibaba's multi‑year journey in Android hot‑fix technology, compares early solutions like Dexposed, AndFix and others, and details Sophix's non‑intrusive design that unifies code, resource and native library patching while maintaining compatibility, security and ease of use across Android versions.
This article reviews a year of development on Tencent's Tinker hot‑fix framework, detailing ecosystem growth, major technical pitfalls on Dalvik, ART, OEM integrations, and the practical solutions that emerged to keep Android apps stable and updatable.
The article uses a bus‑schedule analogy to illustrate how long release intervals and frequent hotfixes frustrate customers, then proposes shorter release cycles through better iteration planning, demand splitting, stronger development capability, and robust testing to achieve continuous, rapid delivery.
Android's fragmented versions and market‑specific policies make bug fixes and version upgrades painfully slow, but by treating the app as a loader and delivering patch files that replace the Application class, dex files, resources, and native libraries, developers can achieve near‑instant, user‑transparent updates without disrupting the normal release flow.
This article explains the principles and practical steps for implementing dynamic class loading and hot‑fixes in Android by manipulating DexClassLoader, PathClassLoader, and bytecode, illustrated with the Qzone hot‑fix solution and open‑source Nuwa and HotFix projects.
This article details how Ctrip transformed its travel app by consolidating product versions, redesigning the wireless backend with a Zuul‑based gateway, decoupling the app engineering into independent modules, implementing extensive performance monitoring, and adopting native plugin and hot‑fix solutions to boost stability and user experience.
