0 views collected around this technical thread.
The Daily Must‑Grab mini‑program order system evolved from a DX XML‑based UI to a React‑like Rax framework and finally to a native Ao Chuang solution, delivering cross‑platform support, smaller bundles, faster launches, better async handling, and extensible plug‑in architecture while leveraging Taobao’s transaction core.
Kotlin Native compiles Kotlin code to native binaries via an IR‑to‑LLVM pipeline, provides C/C++‑compatible memory layout, garbage‑collected runtime, and rich interop with C, C++, Objective‑C/Swift, while facing tooling and value‑type challenges that are being addressed through ongoing performance and language enhancements.
This article walks through Android Binder IPC on Android 14 and Linux 6.1, detailing client‑side service registration and lookup, the kernel driver’s handling of parcels, reference management, and how ServiceManager maps names to IBinder objects, culminating in a diagram of the full native‑to‑kernel transaction flow.
This article details a Kafka consumer issue where the offset unexpectedly becomes a large timestamp due to a native C++ method altering JVM memory, explains the debugging steps, reproduces the bug with Java code, and highlights the risks of unsafe native interactions.
The severe jank observed in Android 14 debug builds stems from the DEBUG_JAVA_DEBUGGABLE flag triggering DeoptimizeBootImage, which forces boot‑image methods onto the slow switch interpreter; a temporary hook clearing the flag and a permanent fix using UpdateEntrypointsForDebuggable restore performance, with Google planning an official fix in Android 15.
The article details a high‑performance, high‑stability Android code‑coverage technique that creates a surrogate ClassLoader, copies the target PathClassLoader’s private classTable pointer, and invokes findLoadedClass on this loader to query a class’s load state without triggering Android’s native optimization that would otherwise automatically load the class.
The article explains how to boost Android app performance by programmatically raising CPU frequency using Qualcomm’s BoostFramework, setting thread‑core affinity with native sched_setaffinity calls, and increasing execution priority via Process.setThreadPriority, providing Kotlin and C examples that demonstrate measurable speed gains.
This article describes a cross‑platform solution that enables a single set of Web component code to be shared across Native, React Native, and mini‑program environments by leveraging Web Components, environment‑aware builds, and bridge communication, thereby reducing development effort and accelerating release cycles.
This article explains how the Android Runtime (ART) implements the Java synchronized keyword at the native level, detailing the roles and interactions of Monitor, LockWord, and native Object classes, as well as the thin‑lock to fat‑lock upgrade process and monitor entry/exit mechanisms.
This article explains how to employ the Java Virtual Machine Tool Interface (JVMTI) in native Android code to record memory allocation and deallocation events, filter relevant classes, store logs efficiently with mmap, and integrate the agent from the Java layer for comprehensive memory‑leak analysis.
Thor is a unified Android container framework that combines Java and native hooking into a lightweight, dynamically loadable module, ensuring backward compatibility, hot‑plug plugin deployment, fault‑tolerant operation, and cloud‑controlled toggling, while real‑world plugins for threads, I/O, privacy, and memory deliver measurable performance and stability gains.
The article explains Android’s user‑space locking hierarchy—from Java intrinsic and JUC locks to C++ std::mutex and pthread mutexes—detailing their internal structures, state transitions, and reliance on futex system calls for kernel‑level blocking, helping developers optimize synchronization across Java and native layers.
This article explains how web front‑end engineers can build native mobile apps by comparing pure native development, cross‑platform frameworks like React Native and Flutter, and hybrid approaches that combine native code, Flutter, and WebView, while providing project structure, code examples, compilation steps, and best‑practice tips.
This article explores the practical integration of Flutter views within React Native and native mobile pages, detailing architectural choices, lifecycle management, event handling, and code implementations to enable seamless cross‑stack UI composition in a large‑scale travel app.
The article introduces JavaTweakHook, a lightweight Android hook framework that avoids Xposed by directly manipulating ART structures, compares it with existing solutions, details the hook process—including method creation, ArtMethod copying, assembly trampolines, and native‑Java integration—and provides compilation, usage, and limitation notes.
This article presents Sliver, an Android‑focused method‑trace framework that combines low‑overhead stack sampling, thread‑suspend techniques, and lock‑information capture to reliably detect and diagnose ANR and jank issues in production environments while maintaining minimal performance impact.
This article explains from a frontend perspective how JavaScript and native code communicate in hybrid apps, covering injection and interception bridge methods, their implementation details, SDK initialization, message flow, and native event listening with code examples and compatibility considerations.
This article describes the design, mmap‑based implementation, architecture, and performance evaluation of a lightweight, low‑overhead mobile logging SDK for Android/iOS, highlighting its compression, encryption, policy‑driven upload, and significant CPU and GC improvements over traditional Java log libraries.
Android inherits Linux file descriptors, which are indexed by non‑negative integers and limited per process, and this article explains their kernel structures, common leak sources such as HandlerThread eventfd, unclosed streams, and SQLite cursor windows, plus practical commands and monitoring techniques to detect and fix FD leaks.
The QQ Music/Karaoke team migrated their Android app from 32‑bit to Arm64‑v8a by reconfiguring Gradle builds, recompiling or replacing over 120 native libraries, extending the dynamic‑resource loader for ABI selection, implementing ABI‑aware update channels, and fixing issues such as library path limits, I/O reliability, camera latency, and WebView cache corruption, completing the transition in early 2021.