The Attar SDK.
A compiler, native UI runtime and packaging toolchain. Already compiling ordinary JavaScript, TypeScript, React, generated CSS and existing component code into native applications.
What is in the SDK
The application graph closes at build time. JavaScript compiles ahead of time; Blink supplies the web UI semantics. The native package includes the engine code the application reaches.
Ahead-of-time compilation
Ordinary JavaScript, TypeScript and TSX inputs, including functions, classes, closures, static modules and async code. React is optional. Language scope
Blink for the interface
DOM, selectors, CSS cascade, layout and painting use Blink. Supported UI libraries can measure elements, handle events and observe changes through the SDK’s web API bindings. Web API scope
Existing frontend dependencies
The pinned React 19 pair, compiled Tailwind 4 CSS and selected Radix / shadcn components are part of the supported workflow. The source example compiles 15 unchanged shadcn component families; the full catalogue and other variants have separate compatibility requirements. Library scope
A standalone native application
The standalone UI host supplies the native window and runs the compiled application without an Electron or Node.js runtime. Attar Electron is a separate planned compatibility layer and is not included in this release.
Native integration through a C ABI
Native programs can meet Attar through a common C interface, with Rust wrappers and Rust/C host adapters. This advanced path requires a matching client-form SDK. How native integration works
Build and packaging tools
The compiler, toolchain and native engine ship together. Declare a UI entry in attar.toml and run attar build to produce a native package. CSS, fonts and local assets become recorded build inputs. Inspect the source projects
Our recommended starting point
When writing Attar code with an agent, we recommend the published Attar skill. It provides a small-app workflow, project configuration, accepted APIs, diagnostics and verification steps.
npx skills add occam-tech/attar-skillsChoose your target
| Target | Scope |
|---|---|
| macOS / Apple silicon | Standalone React examples and app packaging. The compiler package requires macOS 15 or newer and Xcode Command Line Tools. |
| Linux / x86_64 | Compiler packages are available. Equivalent standalone React / shadcn coverage is not verified. |
| Windows | No supported package. |
Know the boundary
- Executable dependencies must resolve at build time.
eval,new Functionand runtime executable loading are outside the model. - Static global CSS imports are supported. Dynamic CSS imports, remote stylesheet imports and CSS modules are refused.
- The shadcn example is a specific set and variant. The full catalogue, other variants and complete keyboard/window behavior are not verified by the example.
- The standalone host exposes a defined set of UI APIs. A dependency that bundles successfully may still need APIs the host does not provide.
- Ad-hoc signing, Developer ID signing and notarization are different checks. An application build does not establish all distribution guarantees.
Find the scope for your application →
What comes next
More UI frameworks
React is the first supported adapter. The native UI engine is independent of it, and support for additional frameworks will follow.
Attar Electron
A planned compatibility layer for Electron and Node APIs. It is not part of this release. Existing porting work and the Etcher research comparison inform that direction; they do not make Electron migration an available release workflow.
The dated implementation inventory remains available as a technical research reference.
About the measurements
The Etcher numbers on the home page describe an earlier recorded comparison on macOS. They come from Attar Electron R&D, which is outside this release. They are evidence for that application and those runs, not a performance guarantee for other applications. Read the methodology.
Engine conformance results are published separately: compliance tests and JavaScript / Test262. Native application behavior and full library compatibility require their own evidence.