0 views collected around this technical thread.
This article details three major optimization directions—component scheduling, component reuse, and component governance—applied to Taobao live streaming, explaining the technical redesign, task scheduler implementation, RecyclerView view‑holder reuse, performance gains, and future improvement plans.
This article details Ctrip's approach to weak network detection, covering background, data collection, processing, dynamic weighting algorithms, result output, deployment effects, and future plans, and provides practical code examples and threshold settings for improving mobile network performance.
This article details Ctrip's end‑to‑end weak‑network identification model, covering background, metric selection, data collection on iOS and Android, processing pipelines with dynamic weighting, weighted median calculations, success‑rate trends, threshold tuning, and deployment results across multiple platforms.
Optimizing a mobile app’s first frame—by defining scope, measuring latency, using profiling tools, and applying strategies such as pre‑loading, lazy initialization, parallel processing, and skeleton screens—boosts brand perception, conversion rates, and resource efficiency, while requiring continuous monitoring, A/B testing, and anti‑degradation safeguards.
This article presents a detailed summary of the AutoHome client team's performance optimization efforts for both the native mobile app and the H5 web frontend, covering background, specific tool and platform enhancements, metric‑driven improvements, process standardization, and future quality‑boosting initiatives.
Effective mobile page performance requires identifying three jank types—screen tearing, frame drops, and long unresponsiveness—monitoring metrics such as response time, animation latency, idle time, and SM, understanding the CPU‑GPU rendering pipeline, and applying optimizations like hardware acceleration, transform‑based animations, reduced layout thrashing, task slicing, and GPU‑friendly techniques.
A comprehensive battery endurance test using Geekbench 4 on six iPhone models (iPhone 8, SE2, XR, 11, 12, 13) shows that iOS 16.4 dramatically reduces runtime for all devices, with iPhone 12 and 13 losing about an hour compared to earlier iOS versions.
Baidu’s comprehensive low‑end device startup optimization—using a scoring‑based observation system, TTI metrics, automated degradation prevention, high‑performance tools such as UniKV and ABTest lock fixes, and an intelligent scheduling framework—cut cold‑start TTI by over 40% on Android and 30%‑plus on iOS.
This article details the background, analysis, and step‑by‑step solutions for reducing package size, improving cold‑start time, and establishing a comprehensive mobile performance testing framework for both Android and iOS versions of the Xueersi Online School app.
Thresh is a Flutter-based cross-platform dynamic solution for frontend developers that integrates the JavaScript Engine Interface (JSI) to streamline communication between JavaScript and Dart, reducing serialization overhead and thread switching, thereby improving startup and rendering performance on mobile devices.
The design separates the original I/O pool into dedicated network, I/O, and polling thread pools, adds comprehensive monitoring of task duration and frequency, enforces unified polling rules, and automatically tunes pool parameters, resulting in a 76 % reduction in UI lag and easier troubleshooting.
The article details Kuaishou's Y-tech AI SDK (YKit) architecture, covering its design for computer vision capabilities, performance optimization strategies for mobile devices, and real-world case studies such as GAN-based effects and intelligent matting, outlining challenges and future directions.
Baidu’s end‑to‑end optimization of commercial landing pages—splitting container initialization, parallelizing billing, preloading critical resources, and employing server‑ and client‑side pre‑rendering—cuts load times below the 1‑second threshold that Baidu’s data shows is essential to prevent a 5% conversion drop, though implementation demands significant development effort.
This article details the design and deployment of JD Mall's mobile app stutter monitoring system, introducing the stutter rate metric, describing data collection, analysis, and reporting modules, presenting iOS and Android implementation code, and summarizing the performance improvements achieved across the platform.
This article introduces the background, core features, network and page performance modules, error monitoring, reporting, and optimization practices of a mobile App Performance Management (APM) system, highlighting its impact on monitoring, diagnostics, and performance improvement for large‑scale applications.
The article explains how Baidu App’s smoothness monitoring distinguishes jitter and stutter, sets 30 ms and 70 ms thresholds for jank detection, and adopts the per‑second and stage‑converted jank rate metrics—derived from jank time—to provide intuitive, bounded measurements while avoiding FPS limitations.
To address the slow loading and high bandwidth costs of GIFs in short‑content feeds, the team evaluated APNG, WebP, SharpP, and MP4, found MP4 video conversion offers the best compression, universal support and comparable CPU usage, achieving a 62% size reduction, 90% instant‑open rate and a 5.6% exposure boost.
The article introduces Shooter, a mobile performance monitoring platform for Android that provides non‑intrusive, lightweight SDKs to monitor app startup, jank, network, native page, and WebView performance, explains the technical solutions, data collection methods, and showcases console visualizations and real‑world empowerment cases.
The project replaces karaoke effects with ASS‑based lyrics on Android, using a backend to generate ASS files and a JNI renderer that rasterizes and composites bitmap fragments; optimizations like transparent‑fragment filtering, opacity early‑out, NEON SIMD, copy elimination, and double‑buffered decoding cut frame time from 52 ms to under 3 ms, raise frame rate from 7 fps to 15 fps, and shrink memory usage from 180 MB to under 10 MB.
This article shares Trip.com’s experience in redesigning the mobile app launch process through componentization, concurrent initialization, visual monitoring, and automated experiments, culminating in the Rocket framework that reduced startup time by over 40% while keeping modules isolated and crash‑resilient.