HarmonyOS Code Workshop

Problem

When building ArkTS apps under HarmonyOS 7 (API 26 Beta1) and DevEco Studio 26.0.0 Beta1, developers often run into compile-time friction caused by TypeScript/ArkTS syntax gaps, deprecated APIs mixed with newer ones, inconsistent state and routing patterns such as @State, @Prop, and Navigation, and missing constraints for folding-screen, tablet, and multi-device adaptation. This skill focuses on those practical issues rather than generic snippets.

How It Works

• ArkTS constraints: generates code around let / const, explicit types, arrow functions, interface-based object literals, and avoidance of any, destructuring, and other unsupported patterns.
• Deprecated API detection: flags patterns like router.pushUrl, global animateTo(), console.log, and legacy camera.Camera, then suggests Navigation, UIContext, hilog, and CameraManager alternatives.
• Pre-output self-check: validates syntax, API usage, component rules, generics, and performance concerns, including a single @Entry, LazyForEach data sources, StorageLink defaults, and explicit return types.
• Version annotations: adds an API version comment at the top of code blocks, defaulting to API 23+ unless the user specifies another target.

Boundaries

The material is written for HarmonyOS 7 (API 26 Beta1) and DevEco Studio 26.0.0 Beta1. Other API versions may have interface differences. For release, privacy, signing, and filing concerns, verify compliance against AGC review requirements.