Pangram verdict · v3.3
We believe that this document is a mix of AI-generated, and human-written content
AI likelihood · overall
MixedArticle text · 970 words · 3 segments analyzed
macOS · Linux · Windows · iOS · AndroidToolkit for building native desktop appsWrite your app in native markup and TypeScript — or Zig. The toolkit's own engine renders it into real OS windows — no browser, no WebView, no JS runtime.$ npm install -g @native-sdk/cli<6 MBEvery app on this page — engine, widgets, renderer — as one static release binary.~100 msFrom launch to the first frame on the glass — 71–131 ms warm across these apps on macOS arm64.0Embedded browsers, script engines, or interpreters inside those binaries.Measured in this repository: zig build -Doptimize=ReleaseFast on macOS arm64; launch is process spawn to first presented frame.PrinciplesBeautiful by default. Customizable by design.Native SDK exists because expressive UI and native performance should not be competing goals. Developers often choose web-based runtimes because they offer freedom, speed and control over the product experience. But that freedom often comes with a heavy runtime. Native SDK keeps the expressive authoring model and replaces the runtime with native rendering.The same toolkit. The same player. Two identities.Every difference between examples/soundboard and examples/deck is design tokens and a chrome pass — same widgets, same engine. One is an airy app window that follows the site theme; the other is a dense 512×264 enamel-and-glass hardware unit with one finish by design.Beautiful by defaultGreat software should not start from a blank slate.Customizable by designYour app should have its own identity, not ours.Native from the startEvery interface is rendered without a browser or WebView.Predictable stateState changes should be explicit, inspectable and easy to reason about.Simple authoringInterfaces should be easy to read, easy to write and easy to generate.AI is part of the workflowNative SDK is designed for a world where humans and AI agents build software together.Predictable by designEvents. Messages. State. Interface.Events produce messages, messages update state, and state renders the interface — simple to debug, simple to maintain, and simple for AI to generate.
This is examples/ui-inbox from the repository: the whole UI is one declarative view, and one update function is the only place state changes. Mistakes in a view are compile errors with line and column, and in dev you edit the view while the app runs, keeping state.Built from the source above and captured running on macOS. The pixels come from Native SDK’s engine; the window and scroll physics come from the OS.Built for modern appsSeven real apps, in the repoDashboards, editors, tools, internal apps, creative software — every screenshot is rendered by Native SDK’s deterministic engine from the example apps in examples/, the same state captured once per color scheme. Flip the site theme and the apps flip with it — deck alone stays dark, by design.A split-pane editor whose preview is native widgets.Headings, tables, task lists, links, and blockquotes on the right are ordinary widgets rendered live from the editor on the left — keystroke for keystroke, with no WebView and no HTML.Native from the startFeels native because it isNative SDK owns its renderer — no embedded browser, no heavy runtime pretending to be native. One engine draws every widget into real OS windows, and the parts users touch stay with the operating system: scrolling carries OS momentum, menus are real menus, and the tray is the real tray.Native UI Guide →OS scroll physicsmomentum and rubber-band overscroll on macOSContext menusdeclare one menu in markup or Zig; the OS presents it natively, with an automatic anchored fallbackMenu bar & trayapp menus and menu-bar extras driven by the modelDialogs & file dropnative open/save panels and drop events as messagesIME compositionreal text input on macOS, Linux, and WindowsHiDPI renderingcrisp scale-factor-aware pixels on every displayany agent, any running app$ native automate wait$ native automate snapshotrole=button name="Add task" …$ native automate widget-click canvas 3$ native automate assert 'gpu_nonblank=true'$ native automate screenshotAI is part of the workflowBuilt to be written by AI agentsDeclarative markup and one typed update function make a surface agents author reliably — and the repository ships an agent skill that teaches all of it. Every app embeds an automation server, so any agent can see and drive the running window: snapshots, assertions, input, screenshots.
An eval harness hands a clean agent a scaffolded workspace and grades the result — builds, markup checks, live snapshots, and an LLM judge.Automation →One binaryThe whole app is one small fileMarkup compiles into the executable, so release builds carry no parser, no interpreter, and no scripting engine — just your logic and the engine, linking the system’s own frameworks. Effects run HTTP fetches, process spawns, file I/O, and timers off the loop; results come back into update as plain messages. And when part of your product is the web, WebView panes coexist with the canvas in the same window.Packaging →examples — release builds$ zig build -Doptimize=ReleaseFast$ ls -lh */zig-out/bin3.6M calculator4.2M deck3.6M feed3.5M markdown-viewer3.5M notes5.7M soundboard3.7M system-monitorCross-platformOne SDK, desktop and mobileOne codebase compiles for macOS, Linux, Windows, iOS, and Android. Desktop is the mature surface; mobile is experimental — verified on the simulator and emulator, with APIs and tooling still evolving. These statuses describe what ships and is verified today — not a roadmap.macOSNativeMetal presentation, OS scroll physics, native context menus, menus, tray, and dialogs. The primary development platform.LinuxSoftware presentationGTK windows driven by the deterministic software renderer, with pointer, keyboard, scroll, IME composition, and HiDPI.WindowsSoftware presentationWin32 host with IME composition. Cross-compiled and exercised in CI under Wine, including real input injection.iOSExperimentalApps compile into an embed library and present via CAMetalLayer. Verified on the iOS Simulator; device support is in progress.AndroidExperimentalCross-compiles with the full embed ABI and a NativeActivity shim. On-device runs are not yet verified.WebViewsCoexistingSystem WebView apps and panes on macOS, Linux, and Windows; bundled Chromium (CEF) on macOS.Full Support Matrix →Build something nativeScaffold an app, open a real window, and edit the view while it runs.terminal$ native init my_app$ cd my_app && native deva real window opens — edit src/app.native while it runs