0 views collected around this technical thread.
This article explains the challenges of converting designers' Lottie animation descriptions into reusable front‑end code, compares frame‑by‑frame, keyframe, and CSS variable approaches, and provides practical examples for generating CSS, CSS‑variables, and React Native Animated implementations.
This article details Ctrip's migration of its large‑scale React Native (RN) codebase to HarmonyOS using the custom CRN framework, covering technology selection, version upgrades, native component re‑implementation, component C‑ization, performance optimizations such as pre‑loading, TurboModule worker threads, instruction pruning, and future roadmap.
The article explains how the open‑source ohos_react_native project brings React Native 0.72.5 to OpenHarmony, detailing its support for the New Architecture, Fabric rendering, C‑API performance gains, TurboModule variants, and the current migration status of related packages.
This article explains how to analyze React Native bundle contents, customize Metro's module ID generation to achieve stable code splitting, and integrate the resulting base and feature packages with a hot‑update workflow that preloads the base bundle, loads feature bundles on demand, and handles loading failures on iOS.
This article documents the design, iterative evolution, and performance optimizations of a cross‑platform self‑rendering engine that started with QuickJS and Flutter, progressed through a C++‑based render tree, and now adopts a React Native‑style self‑draw approach using Skia, detailing architecture, code, and results.
This article details the process of introducing React Native 0.72.10 into an existing mobile application, covering the rationale for selection, project structure adjustments, iOS and Android integration challenges, script modifications, dependency management, and solutions to common issues such as path configuration, Gradle compatibility, and library conflicts.
In 2023 NetEase Cloud Music’s membership team overhauled its payment link by optimizing React‑Native checkout pages, pre‑fetching iOS IAP data, updating Android third‑party SDKs, and adding failure‑reminder SMS, boosting FCP and LCP scores, purchase UV, conversion, and overall payment success rates.
The article reviews cross‑platform architecture concepts, examines the trade‑offs between code reuse and user experience, discusses screen‑size differentiation, outlines criteria for selecting a technology stack, and proposes progressive development and systematic standards to ensure sustainable, high‑quality multi‑device applications.
This article explains the concept and importance of cross‑platform architecture, outlines the three layers of hardware, OS, and application, compares hybrid, framework‑native, self‑rendering, and DSL‑based approaches, and provides practical implementation examples and selection criteria for developers.
To counter the 40‑100 % size increase of Hermes bytecode bundles after upgrading to React Native 0.70, the team switched to xz compression (cutting zip size 20‑26 %), enabled hermesc ‑O optimization (shrinking bundles 10‑22 % while requiring a two‑step source‑map merge), and used the ‑base‑bytecode option with bsdiff to reduce incremental OTA patches by up to 85 %, collectively improving download and update efficiency.
This article examines the evolution, architecture, performance and trade‑offs of major cross‑platform mobile frameworks—including Cordova, React Native, Flutter, and the newly released uni‑app x—by comparing their logic and rendering layers, communication overhead, package size, memory usage and real‑world testing results.
The article details how the Tango framework creates a standardized, AST‑driven low‑code system for React Native by integrating cloud‑phone‑based real‑device preview, visual building tools, and unified runtime/component/data management to cut development costs, improve code reuse, and streamline cross‑platform mobile app creation.
This article compares Flutter and React Native across design, performance, development efficiency, and ecosystem factors, outlines the team’s selection criteria, and concludes with a recommendation to adopt Flutter for its visual customization, consistency, rapid development, and strong community support.
This article describes Snowball's evolution from a single React Native bundle to a multi‑bundle, code‑splitting architecture that reduces bundle size by 70%, shortens load time by 65%, and enables flexible, incremental updates through Metro‑based split‑packages and LRU engine caching.
2023’s mobile app development landscape is shaped by emerging trends such as the metaverse, blockchain integration, advanced AR, AI-driven voice and chatbots, and innovations in frameworks like Swift, Jetpack Compose, Kotlin Multiplatform, React Native, and Flutter, all influencing the future of iOS and Android solutions.
This article analyzes the long‑standing React Native text‑truncation issue, explains Android’s text‑measurement architecture—including Spanned, TextPaint, Layout and TextLine—examines two common truncation cases, provides concrete fixes, and proposes a runtime monitoring solution to detect and log such problems.
Xima’s React Native platform now powers dozens of services and tens of millions of daily page views, achieving sub‑second startup through RAM‑bundle and Hermes upgrades, bundle splitting, container caching, lazy loading, optimized list and image handling, while the upcoming JSI‑based Fabric, Turbo Modules and CodeGen architecture promises further latency reductions and smoother user experiences.
This article examines the business background and challenges of multi‑platform front‑end development, evaluates mainstream cross‑platform technologies, selects Taro as the optimal solution, and details its integration with existing React Native and Web stacks, component and API adaptation, CSS handling, performance testing, cost analysis, and future outlook.
This article describes the design and implementation of a DIY product card system that decouples UI and logic, enabling product teams to configure and render customizable, cross‑platform card templates via a low‑code platform, reducing development effort and improving click‑through rates.
The article walks through a real‑world React‑Native white‑screen crash, explains how the Metro bundler transforms source code into a jsbundle, extracts two distinctive code‑feature patterns (e.default = v and return (0, l.default)(b,[{)), and demonstrates how these patterns can be used to locate the original component files responsible for the error.