Skip to guide
DocumentationProject guides
Project guides

Build a Mac app

Use native conventions and plan for signing early.

Reviewed 6 October 2026 · 2 min read

Import example project ↗Two named conversations, shared files, revisions and a preview.

Before you start

Swift/SwiftUI suits native Mac interfaces; Electron and other frameworks can share cross-platform code. Native checks need a Mac.

Development signing, Developer ID distribution and notarization are distinct. A built .app is not automatically ready for public distribution.

Step by step

  1. Confirm macOS targets, CPU architecture and Xcode/toolchain version.
  2. Create a small app and test menu, window lifecycle and keyboard behavior.
  3. Add files, notifications or screen control with the corresponding permission flows.
  4. Build and run the packaged app in a clean location.
  5. Follow the appropriate signing/distribution process and verify the downloaded result.

Try this

Example request

Build a Mac menu-bar timer with an accessible settings window. Support keyboard use and reopening after launch. Explain the signing requirements and test the packaged app on the connected Mac.

Check the result

  • Quit, relaunch and restoration behave intentionally.
  • Permission prompts explain the feature.
  • Architecture and minimum OS are identified.

If something goes wrong

For Accessibility failures, check the installed helper identity and exact privacy entry. A rebuilt or differently signed binary may not inherit earlier access.

Signing-key access can require the user’s local Mac session. Report that boundary rather than claiming publication succeeded.

Keep going

Permissions and setupPackage and publishTest real user behavior
Your screen may differ by platform and version. Check availability or get help.