Build your personal knowledge base with Trilium Notes
@triliumnext/mobile
Capacitor shell that wraps the @triliumnext/standalone PWA build as a native mobile app. This package does not ship its own web assets — webDir in capacitor.config.json points directly at ../standalone/dist.
Prerequisites
- Android SDK + an emulator or attached device (set up
ANDROID_HOME/ANDROID_SDK_ROOT). - JDK 17+.
- The monorepo installed:
npm install -g pnpm && pnpm installat the repo root.
First-time setup
# 1. Build the standalone web app into apps/standalone/dist
pnpm --filter @triliumnext/mobile build
# 2. Generate the native Android project (one-off — commits as apps/mobile/android/)
pnpm --filter @triliumnext/mobile exec cap add android
Everyday loop
pnpm --filter @triliumnext/mobile build # rebuild standalone dist
pnpm --filter @triliumnext/mobile sync # copy dist into android/
pnpm --filter @triliumnext/mobile run:android # launch on emulator/device
# or
pnpm --filter @triliumnext/mobile open:android # open Android Studio
How web requests reach the local server (Android vs iOS)
There is no network backend — the whole server runs in-process as WASM in a web worker. The app is a single WebView, so its one tab always wins the database lock, and a tab that owns the worker calls it directly: window.standaloneApi.localFetch, which the client's ajax() (apps/client/src/services/server.ts) prefers over issuing a request at all. Most of the client's API/sync calls (/api, /sync, /bootstrap, /search) therefore never leave the page, on either platform.
What still leaves it — images and fonts the engine loads, uploads, the LLM stream — reaches the worker differently per platform, because the two WebViews resolve *Scheme: "https" differently:
- Android —
androidScheme: "https"works: the app loads athttps://localhost(a real secure origin), so the service worker (apps/standalone/src/sw.ts) intercepts those requests and forwards them to the worker. - iOS — the app loads at
capacitor://localhostand uses fetch / XHR / image interceptors (apps/standalone/src/main.ts, gated onlocation.protocol === "capacitor:") instead, because a service worker cannot register oncapacitor://(navigator.serviceWorker.register()throws — the scheme is not HTTP/HTTPS).
Why iOS is on capacitor:// and not https: Capacitor ignores iosScheme: "https". WKWebView reserves the http/https schemes, so CAPInstanceDescriptor.normalize() (WKWebView.handlesURLScheme("https") == true) rejects it and resets the scheme to the default capacitor. That's why iosScheme is intentionally not set here — it would be a no-op that falsely implies iOS runs on an https origin.
⚠️ Do not remove the iOS interceptor path as "dead code." It is the only working request path on iOS. And do not re-add
iosScheme: "https"— it does nothing on iOS and is misleading.