← All use cases

Build a Mac app shell

Have ZeroTwo create a Mac-native SwiftUI shell with a sidebar, a detail pane, an inspector, commands, and Settings.

With the Build macOS Apps plugin, ZeroTwo turns an app idea into a `NavigationSplitView` app that feels native to the desktop, keeps sidebar selection steady, adds menus, toolbars, and keyboard shortcuts, and places preferences in their own `Settings` scene.

Advanced
1h

Related links

Skills & Plugins

  • Build macOS Apps
    Builds sidebar, detail, and inspector layouts, wires menus and settings, and checks the app from the shell (desktop app; needs a Mac with Xcode).

Start from the Mac scene model

Have ZeroTwo choose the scene structure first, then build a main window with a stable sidebar selection, a detail pane, and an inspector, so the app feels made for desktop. The Build macOS Apps plugin brings those patterns and a shell-first build loop. It needs the ZeroTwo desktop app on a Mac with Xcode installed; see Plugins.

Build a sidebar, detail pane, and inspector

Use NavigationSplitView for persistent navigation. Keep sidebar rows light and native, and put rich content in the detail pane or inspector.

NavigationSplitView {
  List(selection: $selection) { /* rows */ }.listStyle(.sidebar)
} detail: {
  ItemDetailView(selection: selection)
    .inspector(isPresented: $showInspector) { ItemInspectorView(selection: selection) }
}

For unusual split sizing or responder-chain needs, add only the smallest AppKit bridge.

Put commands, toolbars, and shortcuts in the desktop layer

Surface key actions in the menu bar, toolbar, and shortcuts via scene-level commands, all sharing one route. Use FocusedValue or selection state so commands act on the current item, and avoid registering a shortcut twice.

Keep preferences in Settings

Put app-wide preferences in a dedicated Settings scene backed by @AppStorage, not a screen inside the main window.

Prompt the app concept, then validate the shell

Name the concept, content objects, and primary actions, and ask for the shell first. Then run a small build and summarize scenes, commands, state ownership, and AppKit bridges.

Practical tips

Keep the sidebar native

One icon and one or two short lines per row; richer content goes in the detail pane.

Avoid hiding settings in the main stack

Global preferences belong in Settings, reachable from the app menu.

Save AppKit for narrow desktop gaps

For panels, first responders, or a custom NSView, wrap AppKit around SwiftUI-owned state.

Related use cases