Zhuoyue Browser

Zhuoyue Browser (卓阅浏览器) is a HarmonyOS NEXT browser built on ArkWeb, with native iOS and Android shells sharing scripts and contracts through core/. HarmonyOS is not rewritten in Flutter.

ohos/      HarmonyOS ArkTS/ArkWeb client (DevEco project)
ios/       SwiftUI + WKWebView shell
macos/     SwiftUI + WKWebView shell (Memory Saver focus)
android/   Kotlin + Compose + WebView shell
web/       Public marketing site
core/      Injected scripts, rule compiler, model contracts
docs/      Architecture, signing, CI
tools/     Shared quality gates (reader-mode)

Features

• ArkWeb browsing with multiple tabs and an incognito (无痕) per-tab mode.
• Omni-bar for address/search navigation, back/forward, stop/reload, share, desktop user agent, and bookmark toggling — all surfaced in an action sheet.
• ArkWeb AdsBlockManager with a bundled EasyList starter rule set, per-site blocking control, category counters (ads, trackers, pop-ups, cookie banners), and weekly blocked totals.
• Cosmetic cleanup, reader mode (with adjustable line height), and JavaScript-based dark mode.
• Downloads routed through ArkWeb's WebDownloadManager to the system download directory.
• Settings persisted through Preferences: default search engine, ad/tracker blocking and rule strength, appearance (system/light/dark), privacy options (clear browsing data, clear cookies on tab close), and an about section.
• Bookmark, history, and search suggestions surfaced in the address sheet.

Build

The HarmonyOS project lives in ohos/ and targets SDK 6.0.0 (API 20) with compatibility for 5.0.3 (API 15). Open that folder in DevEco Studio.

ohos/build-profile.json5 is not in version control — DevEco writes the signing certificate paths and key passwords of whichever machine opened the project into it. Start from the template:

cp ohos/build-profile.json5.example ohos/build-profile.json5

Then open ohos/ in DevEco Studio once and let it fill in the signing profile (File → Project Structure → Signing Configs → Automatically generate signature). With Hvigor available on PATH:

cd ohos && hvigorw assembleHap
./run_release.sh                 # Harmony / iOS / Android device install
./run_release.sh ohos            # HarmonyOS only
./run_release.sh -d <device-id>

Connect a HarmonyOS device or simulator before installing the HAP for manual UI verification.

Scope boundary

AI page assistance, sync, extension distribution, VPN/DNS filtering, and a full remote EasyList update service are intentionally outside this V1 implementation. The bundled rule file (ohos/entry/src/main/resources/rawfile/ads/easylist.txt) is a small, auditable starter set; production distribution should replace it with a verified subscription and an update signature policy.

See DESIGN.md for the design system that governs the UI, core/ for the portable contracts, and docs/multiplatform.md for the native-shell plan.

Mobile build orchestration, signed artifact retention, and the manual store boundary are documented in docs/mobile-ci-cd.md.