Technical Architecture Upgrade of Mobile QQ: Decoupling, Refactoring, and NT Architecture Evolution

The article is the final chapter of the "QQ 25‑Year Technical Tour" series. It reviews the massive technical debt accumulated over more than 20 years of Mobile QQ development and explains why a comprehensive architecture upgrade was necessary.

Historical baggage : The original monolithic architecture mixed core and business code, leading to unclear boundaries, heavy code coupling, low development efficiency, and high risk for quality and stability.

Decoupling & refactoring : Starting in 2020, the team launched an "industrial practice" project to gradually split the codebase into independent business modules. The new design separates modules by business domain, enforces one‑way layer dependencies, and isolates interfaces and routing. Benefits include tighter module cohesion, clearer APIs, reduced dependency count, and improved testability.

NT architecture upgrade : To solve version fragmentation and low code reuse across platforms, a cross‑platform C++ kernel was built for IM core, common components, and resource management. The NT architecture replaces the previous siloed implementations on desktop, iOS, and Android, enabling unified development and easier maintenance.

Key challenges addressed:

Massive codebase (~10 million lines) and outdated third‑party components.

Complex testing and documentation gaps.

Ensuring a smooth migration without disrupting daily releases.

Handling huge local user data (some DB files >10 GB) on mobile devices with limited storage and power constraints.

Solution highlights :

Stage‑wise decoupling (2020‑2021) achieving ~300 k lines of core code refactored, ~30 base modules and ~40 components decoupled.

Implementation of anti‑degradation mechanisms to block risky changes.

Design of a unified client database with resumable import, user‑level tiering, throttled import to avoid overheating, and comprehensive monitoring.

Full‑link IM rewrite: unified message format, removal of legacy identifiers, consolidation of ~200 message types, and migration of rich‑media resources.

Performance optimizations using MVI single‑direction data flow, pre‑loading, asynchronous rendering, and lazy loading of >200 business components.

Results : Compilation time reduced by 50 %, conflict files decreased by 60 %, conflict occurrences dropped by 30 %, and overall development efficiency markedly improved. The NT architecture now supports multi‑platform reuse, lowers maintenance cost, and provides a stable foundation for future innovations.

Conclusion : Through systematic refactoring, modularization, and cross‑platform architecture redesign, Mobile QQ transformed from a monolithic, hard‑to‑maintain system into a modular, high‑performance, and scalable product, positioning it for continued evolution.