This guide walks you through the complete HarmonyOS mobile development workflow—from understanding the platform’s layered architecture and core ArkTS/ArkUI concepts, to setting up DevEco Studio, creating a Hello World app, managing UI, state, routing, data, and finally packaging and publishing the app.
This article explains ArkUI's component lifecycle hooks, the low‑level FrameNode API, LazyForEach rendering strategy with key generation, the full rendering pipeline, custom measure/layout methods, event bubbling, differences between property and explicit animations, and the purpose of XComponent for native rendering.
OpenHarmony 6.0, unveiled at the 2025 OpenAtom OpenHarmony conference in Changsha, introduces major upgrades across UI components, ArkTS language, media handling, graphics, security protocols, and performance testing, while reporting over 17 million HarmonyOS devices and a rapidly growing contributor community.
This article walks through implementing sophisticated like-button animations using HarmonyOS ArkUI, compares the approach with Android's animation framework, explains key ArkUI APIs like animateTo, and provides detailed Kotlin and TypeScript code for property, Bézier path, and lifecycle management of dynamic UI effects.
This article walks through implementing sophisticated like-button animations for a news client on HarmonyOS using ArkUI, compares the approach with Android's animation framework, explains key ArkUI APIs like animateTo, and provides detailed Kotlin and TypeScript code for property and Bezier curve animations.
Omni-UI is an open‑source ArkUI component library for OpenHarmony that provides over 25 ready‑to‑use UI components, theme switching, and simple integration via ohpm, aiming to boost developer productivity by more than 30% in mobile real‑estate applications.
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 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 Taro adapts standard CSS to HarmonyOS's ArkUI by converting units, handling layout differences with the Yoga engine, and implementing an efficient runtime style system that maintains cross‑platform compatibility and high performance for React‑based applications.
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 explains how the Taro framework bridges React applications to Huawei's HarmonyOS by converting React components into Taro's virtual nodes and then mapping them to ArkUI native components, detailing the runtime architecture, hostConfig methods, and three-step conversion process.
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.
JD Finance’s journey to launch its HarmonyOS NEXT version details the background, strategic necessity, architectural design, component selection, cross‑platform Roma integration, performance tuning, new OS features, and post‑release plans, offering a comprehensive case study for mobile developers tackling native OS migrations.
This article explains how to create and bind native UI components in HarmonyOS by leveraging ArkUI's C/C++ API, covering project setup, library linking, module interface acquisition, node creation, attribute setting, and integration with ArkTS through NodeContent and ContentSlot.
The article dissects HarmonyOS ArkUI’s reactive architecture, showing how the open‑source AceEngine wraps state in ObservedProperty objects, tracks dependencies, updates dirty elements, extends the TypeScript compiler with custom UI syntax, bundles via Rollup, and provides a CDP‑based debugger, achieving fine‑grained updates comparable to Vue but with lower memory overhead and faster response on HarmonyOS devices.
This tutorial walks you through creating a basic HarmonyOS notepad application using the native ArkTS language and ArkUI components, covering project setup, directory structure, UI layout, routing, and implementing add‑and‑delete functionality with complete code examples.
This article shares a comprehensive overview of HarmonyOS Next's key features, compares its development approach with Android and iOS, and details practical experiences, tools, and lessons learned while building the first version of the Zhaozhuan app, including WebView integration and future plans.
This article explores how generative AI is integrated into the AutoDev tool to add ArkTS language support, automatically generate ArkUI pages, and migrate existing Android, iOS, and mini‑program code to HarmonyOS, while discussing technical challenges and future improvements.
The guide provides a complete introduction to HarmonyOS, explaining its distributed architecture and one‑time development model, detailing the DevEco toolchain, ArkTS language and ArkUI frameworks, walking through environment setup and a step‑by‑step first app, and covering advanced topics such as state management, componentization, testing, and publishing.
This article introduces Huawei's upcoming HarmonyOS Next, explains the ArkUI framework with its declarative ArkTS and Web‑like development models, compares the two paradigms, and details how the Taro framework can bridge Web development practices to ArkTS for cross‑platform app creation.
This tutorial walks through creating a complete HarmonyOS demo project without backend integration, covering project setup, constant files, login and registration pages, navigation tabs, home page components, search, list, refresh, and custom input components, all illustrated with code snippets and screenshots.
