Server-driven UI for Android and iOS. Build your app from your own native components, then describe its screens and logic as data that the SDK loads and renders.
Nativeblocks runs frames: screens made of your Jetpack Compose and SwiftUI components (blocks), wired to your own logic (actions). The components stay native and stay yours.
Docs and guides: nativeblocks.io
┌────────────────────────┐ ┌────────────────────────┐
│ Android (Compose) │ │ iOS (SwiftUI) │
│ runtime · foundation │ │ runtime · foundation │
│ compiler · devkit │ │ compiler · devkit │
└───────────┬────────────┘ └───────────┬────────────┘
│ UniFFI │
└─────────────┬──────────────┘
┌───────────┴───────────┐
│ Rust core (runtime) │
└───────────────────────┘
One Rust core handles fetching, caching, and running frame logic, so all platforms behave the same. Each platform wraps it in native libraries:
| Library | What it does |
|---|---|
runtime |
Loads frames and renders them. The entry point: NativeblocksManager. |
foundation |
Ready-made basic blocks and types. |
compiler |
Turns your annotated components and actions into Nativeblocks blocks. |
devkit |
Live preview and debugging tools. Use it in debug builds only. |
Questions and discussion happen on Slack.
Bug reports with a minimal reproduction are welcome. Read CONTRIBUTING.md before opening a pull request.