Skip to content
HuxerUIHuxerUIHuxerUI

macOS

macOS applications use a native CMake/Xcode toolchain and AppKit adapter.

Terminal window
huxerui setup macos
huxerui run macos

The adapter owns NSWindow/NSView lifecycle, AppKit input and NSTextInputClient, accessibility, clipboard, files, HTTP, scheduling, and render-scene presentation. Logical HuxerUI geometry remains in DIPs and is converted at the host boundary.

WindowChromeMode::System retains native chrome. Custom chrome can compose application UI around platform window controls where supported; do not assume Windows caption geometry. Register NSView-backed platform views with <huxerui/macos/platform_registry.h> and publish external textures through <huxerui/macos/external_texture.h>.

Build and runtime validation require macOS and Xcode command-line tools. The website’s cross-platform contract checks do not substitute for AppKit accessibility, IME, NSView composition, signing, or device-scale validation.

System capability boundaries

Section titled “System capability boundaries”

Local notifications use User Notifications for authorization, showing, scheduling, cancellation and primary activation. Default presentation is supported; template requests return Unavailable. Notification clicks enter OnActivation even when launching the process.

See Local notifications for shared usage and platform configuration, and System API for exact contracts.