Repository navigation
Native HarmonyOS NEXT (HAP) version #3027
Description
Check for existing issues
- Completed
Describe the feature
Feature request: Native HarmonyOS NEXT (HAP) version
Hi,
I would like to ask whether there is an official plan to port Acode to native HarmonyOS NEXT (HAP).
Acode is MIT licensed, so I understand that community forks and porting are allowed.
I’m considering starting a community port. My current plan:
- First version: only editor, SFTP, plugin system and web preview (remove the proot Linux terminal for the first release, since proot / ptrace is heavily restricted under HarmonyOS sandbox).
- Use ArkWeb to load the web-based editor core.
- Rewrite file access, permission, lifecycle APIs with HarmonyOS Kits.
Questions:
- Is there any ongoing unofficial / official port branch I should join?
- Are there any hidden pitfalls or architecture boundaries I need to know before starting?
- Would the project welcome a community-maintained HarmonyOS fork, and accept related docs / wiki contributions?
Thanks.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
Reacted by Ajit Kumar
Activity
deadlyjack commentedon Nov 11, 2026
Hi @initKay, thanks for sharing your plan! We’d be happy to see a community-maintained HarmonyOS NEXT port. Starting with the editor and leaving the terminal for later sounds like a sensible first step.
We recently started porting Acode to iOS. As part of that work, we’ve replaced Cordova with our own cross-platform framework, which should make it easier to add HarmonyOS support. You can take a look at the migration repo to see how the Android and iOS implementations fit together.
I’d suggest waiting until the migration lands in the main Acode repo before starting your fork. In the meantime, if you spot anything in the new framework that might be tricky to implement on HarmonyOS, feel free to bring it up here. It’d be great to hear what you find!