- Home
- Skills
- Openharmonyinsight
- Openharmony Skills
- Android To Harmonyos Migration Workflow
android-to-harmonyos-migration-workflow_skill
- Python
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openharmonyinsight/openharmony-skills --skill android-to-harmonyos-migration-workflow- SKILL.md25.4 KB
Overview
This skill defines an iterative multi-agent workflow to migrate Android projects to HarmonyOS. It coordinates Analyzer, Planner, Translator, Validator (using ohos-app-build-debug), Tester, Feature Comparator, and UI Comparator agents to convert, validate, test, and compare modules until parity is achieved. The workflow includes scripts, API mappings, component patterns, and automated verification tools to speed and standardize migration.
How this skill works
The Analyzer agent scans the Android codebase and outputs a structure and dependency report. The Planner creates a modular migration plan and prioritizes modules. The Translator converts Java/Kotlin and Android components to ArkTS and HarmonyOS components. The Validator compiles and packages using the ohos-app-build-debug skill, then the Tester runs functional tests. After all modules complete, Feature Comparator and UI Comparator run global comparisons and feed missing items back to the Planner for another iteration.
When to use it
- Migrating an existing Android app to HarmonyOS with repeatable quality checks
- When you need automated, per-module conversion and validation (Java/Kotlin to ArkTS)
- If you require compiled verification and on-device launch checks using ohos-app-build-debug
- When visual parity between Android and HarmonyOS UI must be measured and corrected
- For iterative migration where missing features are discovered and re-planned
Best practices
- Start with Analyzer to get accurate module sizing and dependencies before planning
- Follow Planner priorities: data layer → business logic → UI layer, ~5000 LOC per module
- Run Validator with ohos-app-build-debug for automated build, install, launch, and screenshot validation
- Keep API_MAPPING and COMPONENT_MAPPING updated to reflect platform differences
- Run global Feature and UI comparisons only after all modules complete, then iterate on missing items
Example use cases
- Migrate a medium Android app by converting Activity→Page and RecyclerView→LazyForEach module-by-module
- Validate converted code by compiling with ohos-app-build-debug, packaging HAPs, and verifying startup screen on device
- Detect business logic gaps with Feature Comparator and create remediation modules in Planner
- Automatically compare screenshots and layout structure between Android and HarmonyOS using Hypium scripts
- Use the workflow for continuous migration cycles until feature and UI parity are achieved
FAQ
It builds the HarmonyOS project, generates HAP packages, installs or simulates install, launches the app, and captures screenshots to confirm the first screen and build integrity.
When are Feature and UI comparisons executed?
Both comparators run after all planned modules are migrated. Their outputs (missing features and UI differences) are returned to Planner to schedule follow-up migration iterations.