SignalX on Lynx#

Write one SignalX component tree, render it to real native views on iOS and Android — no webview, no diffing, the same signals you already use on the web.

@sigx/lynx brings the SignalX component model to Lynx, ByteDance's cross-platform native rendering engine. Your components run on a background thread; fine-grained signal updates stream to the main thread as a compact op queue, so only the native views that read a changed signal update.

Why Lynx#

• Real native views — components render to UIView / Android View, not DOM in a webview.
• Fine-grained updates — no virtual-DOM diff; a changed signal patches exactly the views that read it.
• One toolchain — the same CLI, Vite-style DX and devtools as SignalX on the web.
• A module family — 32 lockstep-versioned @sigx/lynx-* packages: navigation, gestures, motion, a DaisyUI component library and every native API you need.

The package family#

@sigx/lynx is a collection: the framework barrel plus sub-packages that each ship their own docs. Browse the module catalog or jump straight to a favorite — Navigation, DaisyUI, Gestures, Motion.

Next steps#

Head to Installation, then build your first app.