Skip to content

feat(ohos): add a HarmonyOS shell - #213

Closed
Lfan-ke wants to merge 1 commit into
openecos-projects:mainfrom
Lfan-ke:feat/ohos-wrapper
Closed

Lfan-ke wants to merge 1 commit into
openecos-projects:mainfrom
Lfan-ke:feat/ohos-wrapper

Conversation

@Lfan-ke

@Lfan-ke Lfan-ke commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

A HarmonyOS NEXT ability that loads the ECOS Studio web build in an ArkWeb Web component. No rendering code is ported — the app is the same web bundle, so there is one renderer to maintain rather than one per platform. Pairs with #212, which adds the browser target.

Index.ets reads appUrl from AppStorage and falls back to the production URL, so a development build can be aimed at a local server without a code change.

What is not verified

I have no HarmonyOS toolchain, so this has not been built or run — the JSON5 manifests parse and the ArkTS follows the documented ArkWeb API, and that is the extent of it. Treat it as a starting skeleton for someone with DevEco Studio rather than a tested target.

CI cannot cover it either: GitHub Actions has no HarmonyOS runner and the SDK is not redistributable. Happy to close this if you would rather not carry an unbuilt directory.

A HarmonyOS NEXT ability that loads the ECOS Studio web build in an ArkWeb Web
component. No rendering code is ported: the app is the same web bundle, so there
is one renderer to maintain rather than one per platform.

CI does not build it — GitHub Actions has no HarmonyOS runner and the SDK is not
redistributable.

Signed-off-by: Leo Cheng <chengkelfan@qq.com>
@Emin017

Emin017 commented Sep 9, 2026

Copy link
Copy Markdown
Member

@Lfan-ke Thanks for the contribution!

Just to confirm: is the current PR expected to work on HarmonyOS as-is, or does it still need additional setup / changes before it can run?

We also don’t have HarmonyOS devices or the DevEco Studio toolchain on our side. Could you share any guidance on how we (or others) could test this PR on HarmonyOS? For example:

  • Recommended DevEco Studio / SDK version
  • Any specific build/run steps
  • Whether a physical device is required, or if the emulator is sufficient
  • Any known limitations or gotchas

Appreciate the note that this is currently an untested skeleton — that helps set expectations.

If there’s no practical way for us to verify it, we’ll probably have to hold off on merging this feature PR for now.

@Lfan-ke Lfan-ke closed this Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants