鸿蒙生态应用开发白皮书V2.0 (华为公司)（Z-Library）

# 鸿蒙生态应用开发白皮书V2.0 — Reading Guide ## 【One-Line Pitch】 A comprehensive official guide to HarmonyOS app development, covering the full developer journey from core design philosophy (multi-device deployment, atomic services, native intelligence) to hands-on tooling (DevEco Studio, ArkUI, testing, and distribution). Essential reading for mobile/frontend developers, IoT engineers, and technical decision-makers evaluating HarmonyOS as a development platform. --- ## 【Book Arc】 - **Opening (~0%–8%)**: Sets the stage for the IoT era's opportunities and challenges, introduces the three core technology principles — "develop once, deploy everywhere," "composable and flowable," and "unified ecosystem with native intelligence" — and explains why lightweight program entities (mini-apps, atomic services) are reshaping app distribution. - **Early (~8%–23%)**: Dives into multi-device development capabilities: UI adaptation via virtual pixels (vp) and screen size abstractions (xs/sm/md/lg), interaction event normalization, device capability abstraction (SysCap), and the two HAP packaging/distribution models. Introduces atomic services (元服务) with their "tap-to-use, no-install" characteristics. - **Early–Middle (~23%–38%)**: Maps the complete developer enablement ecosystem: empowerment suite (docs, Codelabs, UX resources), DevEco Studio IDE, SDK, testing standards and tools, operations analytics (crash, APM, cloud monitoring), and the OS open capability set — distributed soft bus, distributed file/database/hardware, security, ArkCompiler runtime, communication, graphics, and App Services (accounts, push, payments, ads). - **Middle (~38%–54%)**: Covers the development paradigm: HarmonyOS Design, ArkUI framework with two development approaches (declarative ArkTS and Web-like JS), state management decorators (@StorageLink/@StorageProp), layouts, animations, event handling, voice interaction ("visible and speakable"), and the Stage model for app architecture. - **Middle–Late (~54%–77%)**: Explains the build and tooling ecosystem: module compilation targets (HAR, HSP, HAP), C API for native development, ArkCompiler toolchain (ABC bytecode, bundle vs. esmodule modes), DevEco Studio features (code editing with AI-assisted completion, distributed debugging, Profiler with scenario-based tuning templates), command-line tools, and cloud-dev integration. - **Late (~77%–100%)**: Covers testing in depth — unit testing (Hypium), UI testing (uitest-api), performance testing (SmartPerf), stability testing (wukong random event injection), and special testing (app health checks, cloud-based test platform) — followed by unified app listing and multi-device distribution through AppGallery Connect. --- ## 【Key Takeaways】 - **"Develop once, deploy everywhere" is the foundational principle** (Opening): HarmonyOS abstracts screen size (vp units, xs/sm/md/lg categories), normalizes input events across touch/keyboard/rotary, and abstracts device capabilities via SysCap, letting one codebase target wearables, phones, tablets, and smart screens. This directly addresses the cost of multi-device adaptation. - **Atomic services (元服务) are the lightweight distribution vehicle** (Early): No-install, "tap-to-use, use-and-go" program entities that can be pushed proactively via system-level smart entry points (e.g., Service Center, Xiaoyi suggestions). They support universal cards for glanceable information and free-flow migration across devices — a shift from "people find apps" to "services find people." - **The distributed capability stack is the differentiator** (Early): Distributed soft bus (unified communication across WLAN/Bluetooth/NFC/USB), distributed file system (POSIX-compatible), distributed database (global unified data view), and distributed hardware (forming "super terminals") enable cross-device scenarios like migrating an unfinished email from phone to tablet. - **ArkUI offers two development paradigms** (Middle): The declarative ArkTS approach is more concise and efficient, while the Web-like paradigm (HML/CSS/JS) is friendlier to frontend developers. State management via AppStorage with @StorageLink (two-way binding) and @StorageProp (one-way binding) decorators drives UI updates. - **ArkCompiler optimizes TypeScript execution** (Early–Middle): Unlike engines that convert TS→JS first, ArkCompiler analyzes type information at compile time, generates inline caches, and supports AOT compilation to machine code. TaskPool API provides priority scheduling and auto-scaling worker threads, addressing Actor model startup/memory overhead. - **Module-based architecture scales from small to large apps** (Middle–Late): Developers decompose business logic into modules, compiled into HAR (intermediate), HSP (shared package, deduplicated across HAPs), or HAP (deployable unit). Multiple HAPs can be combined into an App Pack for unified listing, enabling both single-purpose and complex app distribution. - **Testing is a first-class citizen with layered tooling** (Late): Unit testing (Hypium), UI testing (uitest-api with Driver/On/Component classes), performance profiling (SmartPerf with CPU/memory/IO analysis), and stability testing (wukong random event injection) are complemented by cloud-based special testing for performance, power, stability, compatibility, UX, and security. - **DevEco Studio is the end-to-end IDE** (Middle–Late): Features include multi-device preview, distributed debugging (breakpoints jumping across devices), scenario-based Profiler templates (Time/Allocations/CPU/Energy/Launch Insight), AI-assisted code completion, low-code development, and cloud-dev integration for building backend services alongside the app. --- ## 【Reading Tips】 - **Skim the opening chapters (0–8%)** for the strategic rationale and ecosystem vision; the three core principles give you a mental model for everything that follows. - **Deep-read the ArkUI and ArkCompiler sections (38–70%)** if you're a hands-on developer — these contain the actual syntax, decorators, and compilation details you'll need. Pay special attention to the declarative vs. Web-like paradigm choice and the HAR/HSP/HAP module distinctions. - **Use the tooling chapters (54–90%) as a reference**, not a cover-to-cover read. The Profiler templates table and testing tool overview are worth bookmarking for when you hit performance or stability issues. - **Watch for the "excerpts do not cover" gaps**: The sample lacks detailed content on Chapter 7 (free flow/distributed runtime), Chapter 8 (operations analysis), and Chapter 9 (full-scenario case studies) — these are listed in the table of contents but not elaborated in the provided material. - **If you're a frontend/Web developer**, the Web-like paradigm section (HML/CSS/JS) is your entry point; if you're a systems/performance engineer, focus on the C API, ArkCompiler, and distributed services chapters. --- ## 【Coverage Limits】 This guide synthesizes the provided excerpts (approximately 0–90% of the book). Detailed content on free-flow/distributed runtime environments (Chapter 7), comprehensive operations analysis (Chapter 8), and full-scenario case studies (Chapter 9) is not covered in the source material. --- ##