Declarative markup with typed updates
Interfaces are written in native markup and updated through a typed message handler, which keeps state changes explicit instead of hidden in ad hoc event logic.
Native SDK
Native SDK is a toolkit for building native desktop apps with declarative markup, message-based state, and a native renderer—without a browser or WebView.
Native SDK builds native desktop apps without a browser runtime
Native SDK is a toolkit for building native desktop applications with declarative markup, a message-based state model, and a native renderer. It is intended for developers who want interfaces to run in real OS windows without bundling a browser or WebView.
The system centers on explicit messages and state updates, so interface changes are easier to follow and debug. The site also documents desktop-first platform support, with experimental mobile coverage on iOS and Android.
Core features
Native renderer and OS windows
The toolkit renders directly into real operating-system windows, with no browser or WebView required for native-rendered apps.
Predictable message-based state model
Events produce messages, messages update state, and state renders the interface, which gives the app a single place where behavior changes are applied.
Platform-specific native behavior
The runtime preserves native behavior such as scroll physics, menus, dialogs, file drop events, IME composition, and HiDPI rendering where the platform supports it.
Automation and debugging tooling
Native SDK includes an automation server for snapshots, assertions, synthetic input, screenshots, and record/replay, plus the `native doctor` command for environment checks.
Packaging and release builds
The documentation presents packaging as part of the toolkit, with platform-specific outputs and static release binaries described for the desktop workflow.
Typical use cases
Desktop product UI
Build a native desktop application that needs standard windows, menus, dialogs, and responsive interaction without embedding a browser engine.
Tools and internal applications
Create operational interfaces such as dashboards, editors, and utilities where predictable state changes and a compact runtime matter.
AI-assisted app generation
Use the declarative markup and typed update model as a surface that agents can author, inspect, and automate reliably.
Cross-platform host-aware apps
Ship to macOS, Linux, and Windows with platform-specific behavior, while also evaluating experimental mobile support on iOS and Android when needed.
Automated testing and inspection
Use the built-in automation server to capture snapshots, drive input, and assert on running app state during development or CI-style workflows.
Pros and Cons
Pros
- No browser or WebView is required for native-rendered apps.
- State changes are explicit and easier to inspect than implicit UI behavior.
- The runtime keeps several native platform behaviors, including menus, dialogs, and scroll physics.
- Platform support is documented in a tiered way, which makes limitations visible instead of implied.
- Built-in tooling covers environment checks and automation workflows.
Cons
- Mobile support is described as experimental rather than fully mature.
- Unsupported operations return runtime errors, so some capabilities are intentionally host-limited.
- The platform support page notes that some desktop/web-engine combinations and mobile details still have caveats.
FAQ
What does Native SDK build?
It is a toolkit for building native desktop applications, with experimental support for mobile canvas apps on iOS and Android.
Does Native SDK require a browser or WebView?
Native-rendered apps do not require a browser or WebView. The docs describe a native renderer that draws directly into OS windows.
Which platforms are supported?
The source documents macOS, Linux, and Windows as desktop platforms, and iOS and Android as experimental mobile platforms.
What is `native doctor` for?
`native doctor` checks the local development environment for issues such as host platform details, WebView availability where relevant, manifest validity, log directory writability, CEF presence for Chromium configurations, and signing tools.
Does Native SDK include automation support?
Yes. The documentation describes an embedded automation server that supports snapshots, assertions, input, screenshots, and record/replay.
Quick Facts
- Category
- Developer Tool
- Primary platform
- Desktop
- Desktop support
- macOS, Linux, Windows
- Mobile support
- Experimental iOS and Android
- Runtime model
- Declarative markup with message-based state updates
- Notable tooling
- native doctor and built-in automation
Native SDK Alternatives
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repos and verifies changes with compilers, debuggers, sanitizers, and tests.
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads in Firecracker micro-VMs with private networking and SDK, CLI, or MCP control.
hob
hob is an independent workspace for coding agents, with local control over sessions, terminals, history, routing, and follow-up work.
Manta AI
Manta AI is an autonomous web app testing tool that maps app behavior, catches regressions, and generates tests from a URL, no scripts or selectors needed.
SonOf
SonOf connects to your repo and PM tool, audits your codebase, and turns approved work into shipped tickets with senior engineering review.
Ghost
Ghost is a terminal-based AI assistant for chatting, code generation, and CLI tasks. Includes free models, supports Linux, macOS, Windows, and is open source.