kuito.
Commencer

Embed Hermes on the device

La traduction de cette page manque ou n'est plus à jour : elle s'affiche en anglais. Lire en anglais

Kuito executes app JavaScript inside the iOS or Android process. The desktop development server compiles and sends updates; it does not run the app's event handlers on behalf of the phone.

02 / SCHEDULING & RENDERING One app, two execution threads The shared C++ queue batches property mutations before handing them to the native UI thread. HERMES THREADApp logic + async Signals · effects · eventsPromise jobs · timers · fetch One serialized VM owner C++ queue Deduplicateproperties Keep create /remove order NATIVE UI THREADPlatform renderer UIKit / Android ViewsApply ordered mutation batch Layout · animations · touch input Native events queue back to Hermes

Runtime ownership

native/shared/KuitoRuntime.cpp owns the shared embedding and host functions. The iOS wrapper schedules evaluations on its serial runtime queue; Android's JNI wrapper uses its Hermes thread. View batches are handed to the platform main thread.

A second Hermes runtime on the UI thread handles motion and compiler-placed callbacks. Values crossing between runtimes use Kuito's explicit contracts; a JavaScript object is not shared implicitly between them.

Development and release

Mode What loads How it changes
Development Runtime kernels and app source Live Patch in the persistent runtime
Release Optimized Hermes bytecode and bundled assets New native build or compatible signed bytecode update

The build pins Hermes and its compiler together. Do not compile bytecode with an arbitrary local Hermes version: the bytecode format must match the embedded runtime. Native code changes always require a native build.

Find an embedding failure

If the shell starts but no screen appears, inspect the startup state and platform log before debugging app layout. Check runtime creation, kernel evaluation, app evaluation and the first committed frame separately. DevTools attaches to each development runtime; crash reports diagnose release failures.

For embedding changes, verify startup, events, promises, timers, native calls, runtime shutdown and compatible Live Patch on both platforms. A host test alone cannot establish JNI/Objective-C lifecycle or device behavior.