1 views collected around this technical thread.
This article introduces Taro's open‑source Harmony C‑API solution, detailing its architecture, rich component and CSS support, performance optimizations, and step‑by‑step installation guide that enable developers to build native‑grade Harmony OS applications using familiar web technologies.
The article introduces Taro's open-source C-API version for HarmonyOS, detailing its architecture, rich component and CSS support, high-performance rendering, hybrid native integration, and step‑by‑step installation guide, positioning it as a leading frontend solution for cross‑platform development.
The article introduces Taro on Harmony's C‑API version, detailing its evolution, open‑source release, three‑layer architecture, rich component and CSS support, high‑performance rendering, installation steps, and future roadmap, positioning it as a leading framework for developing native‑like HarmonyOS applications.
This article details JD's Taro framework adaptation for HarmonyOS, tracing its evolution from ArkTS-based to C-API-driven single- and multi-threaded architectures, highlighting performance gains, feature support, and future enhancements for native-like HarmonyOS app development.
The Taro‑on‑Harmony solution lets developers write a single React‑based codebase that compiles to native HarmonyOS apps with C‑API‑driven rendering, offering both single‑thread and multi‑thread architectures, full component and CSS support, high‑performance UI, and upcoming tooling, as demonstrated by JD.com’s S‑level certified shopping app.
This article details JD's self‑built HarmonyOS image library (DImage), covering its background, research on existing solutions, C++‑based cross‑platform architecture, core modules, performance‑focused pipeline, monitoring and recovery mechanisms, and future optimization directions, all aimed at high‑performance image handling for the JD app on HarmonyOS.
This article explores how Taro leverages C++ and the Harmony C‑API to build a high‑performance, cross‑language event system that unifies event handling across C++, ArkTS, and JavaScript, detailing architecture, event center implementation, node event processing, and future enhancements.
This article introduces JD’s self‑developed HarmonyOS image library, explaining the background, research on existing solutions, the decision to build a C++‑based cross‑platform library, its modular architecture, performance optimizations, quality assurance mechanisms, and future development plans.
During the Double‑11 promotion, our team applied a series of Taro mini‑program performance optimizations—including Skyline rendering engine migration, lazy loading of feed resources, image size reduction, and parallel API requests—to significantly reduce cold‑start, hot‑start, and rendering times, improving overall user experience.
This article explains how Taro converts standard W3C CSS into HarmonyOS ArkUI styles, addressing unit and layout differences, using a Rust‑based LightningCSS plugin and the Yoga layout engine, and detailing the full style initialization, matching, application, and update workflow for cross‑platform React development.
This article explains how Taro leverages C++ and the HarmonyOS C‑API to build a high‑performance, multi‑language event system that bridges ArkTS, JavaScript and native components, detailing architecture considerations, implementation details, and future directions for improving cross‑language event handling.
This article details JD's custom HarmonyOS image library built with C++ and Taro, covering its background, technical design, core modules, performance monitoring, optimization techniques, quality assurance mechanisms, and future development plans to achieve high‑performance cross‑platform image loading for mobile applications.
This article explains how Taro leverages C‑API to move runtime logic to C++ and builds a cross‑language event system that unifies ArkTS, JavaScript and C++ on Harmony OS, improving rendering performance, lifecycle management, and developer productivity.
This article explains how the Taro framework bridges React and HarmonyOS ArkUI by describing Taro's runtime architecture, the custom renderer implementation, and the step‑by‑step conversion of React components into ArkUI nodes, including code examples and key technical challenges.
This article details how the Taro framework bridges the gap between W3C CSS and HarmonyOS's ArkUI by converting units, handling layout differences with Yoga, processing static and runtime styles, and managing style updates to achieve high‑performance cross‑platform applications.
This article explains how Taro resolves the incompatibilities between standard CSS and HarmonyOS ArkUI CAPI styles by converting CSS at compile time, using a Rust‑based LightningCSS plugin, and employing the Yoga layout engine to achieve high‑performance, cross‑platform UI rendering.
This article explains how the Taro framework adapts React applications to run efficiently on HarmonyOS by converting React components into Taro virtual nodes, then into ArkUI nodes through a three‑step rendering pipeline, detailing runtime principles, hostConfig methods, and C++ implementation examples.
This article examines how the Taro framework adapts React code to run on Huawei's HarmonyOS by implementing a custom renderer that converts React components into Taro virtual nodes, then maps them to ArkUI structures through a three‑step process involving Taro Elements, RenderNodes, and native ArkUI nodes.
The article introduces AIGCDesign, an open‑source cross‑platform AI component solution that combines traditional frontend libraries with large‑language‑model capabilities, outlines its design goals, technical architecture, lifecycle hooks, configuration examples, multi‑framework support, and real‑world business integration cases.
This article explains how JD adopted the Taro cross‑platform framework to build HarmonyOS native applications, detailing the background, technical方案, key features, performance results, and future optimization plans for delivering high‑performance mobile experiences.