Apple Human Interface Guidelines for Mac. Use when building macOS apps with SwiftUI or AppKit, implementing menu bars, toolbars, window management, or keyboard shortcuts. Triggers on tasks involving Mac UI, desktop apps, or Mac Catalyst.
Apple Human Interface Guidelines for Mac. Use when building macOS apps with SwiftUI or AppKit, implementing menu bars, toolbars, window management, or keyboard shortcuts. Triggers on tasks involving Mac UI, desktop apps, or Mac Catalyst.
Mac apps serve power users who expect deep keyboard control, persistent menu bars, resizable multi-window layouts, and tight system integration. These guidelines codify Apple's HIG into actionable rules with SwiftUI and AppKit examples.
1. Menu Bar (CRITICAL)
Every Mac app must have a menu bar. It is the primary discovery mechanism for commands. Users who cannot find a feature will look in the menu bar before anywhere else.
Rule 1.1 — Provide Standard Menus
Every app must include at minimum: App, File, Edit, View, Window, Help. Omit File only if the app is not document-based. Add app-specific menus between Edit and View or between View and Window.
// AppKit — Building menus programmaticallylet editMenu =NSMenu(title: "Edit")
let undoItem =NSMenuItem(title: "Undo", action: #selector(UndoManager.undo), keyEquivalent: "z")
let redoItem =NSMenuItem(title: "Redo", action: #selector(UndoManager.redo), keyEquivalent: "Z")
editMenu.addItem(undoItem)
editMenu.addItem(redoItem)
editMenu.addItem(.separator())
Rule 1.2 — Keyboard Shortcuts for All Menu Items
Every menu item that performs an action must have a keyboard shortcut. Use standard shortcuts for standard actions (Cmd+C, Cmd+V, Cmd+Z, etc.). Custom shortcuts should use Cmd plus a letter. Reserve Cmd+Shift, Cmd+Option, and Cmd+Ctrl combos for secondary actions.
Standard Shortcut Reference:
Action
Shortcut
New
Cmd+N
Open
Cmd+O
Close
Cmd+W
Save
Cmd+S
Save As
Cmd+Shift+S
Print
Cmd+P
Undo
Cmd+Z
Redo
Cmd+Shift+Z
Cut
Cmd+X
Copy
Cmd+C
Paste
Cmd+V
Select All
Cmd+A
Find
Cmd+F
Find Next
Cmd+G
Preferences/Settings
Cmd+,
Hide App
Cmd+H
Quit
Cmd+Q
Minimize
Cmd+M
Fullscreen
Cmd+Ctrl+F
Rule 1.3 — Dynamic Menu Updates
Menu items must reflect current state. Disable items that are not applicable. Update titles to match context (e.g., "Undo Typing" not just "Undo"). Toggle checkmarks for on/off states.
Provide right-click context menus on all interactive elements. Context menus should contain the most relevant subset of menu bar actions for the clicked element, plus element-specific actions.
The App menu (leftmost, bold app name) must contain: About, Preferences/Settings (Cmd+,), Services submenu, Hide App (Cmd+H), Hide Others (Cmd+Option+H), Show All, Quit (Cmd+Q). Never rename or remove these standard items.
Mac users expect full control over window size, position, and lifecycle. An app that fights window management feels fundamentally broken on the Mac.
Rule 2.1 — Resizable with Sensible Minimums
All main windows must be freely resizable. Set a minimum size that keeps the UI usable. Never set a maximum size unless the content truly cannot scale (rare).
Opt into native fullscreen by setting the appropriate window collection behavior. The green traffic-light button must either enter fullscreen or show the tile picker.
SwiftUI windows get fullscreen support automatically.
Rule 2.3 — Multiple Windows
Unless your app is a single-purpose utility, support multiple windows. Document-based apps must allow multiple documents open simultaneously. Use WindowGroup or DocumentGroup in SwiftUI.
For document-based apps, the title bar must show the document name. Support proxy icon dragging. Show edited state (dot in close button). Support title bar renaming on click.
Never hide or reposition the close (red), minimize (yellow), or zoom (green) buttons. They must remain in the top-left corner. If using a custom title bar, the buttons must still be visible and functional.
// AppKit — Custom title bar that preserves traffic lights
window.titlebarAppearsTransparent =true
window.styleMask.insert(.fullSizeContentView)
// Traffic lights remain functional and visible
3. Toolbars (HIGH)
Toolbars are the secondary command surface after the menu bar. They provide quick access to frequent actions and should be customizable.
Rule 3.1 — Unified Title Bar and Toolbar
Use the unified title bar + toolbar style for a modern appearance. The toolbar sits in the title bar area, saving vertical space.
Use a segmented control or picker in the toolbar for switching between content views (e.g., List/Grid/Column). This is a toolbar pattern, not a tab bar.
Toolbar items should have both an icon (SF Symbol) and a text label. In compact mode, show icons only. Prefer labeled icons for discoverability. Use Label to supply both.
4. Sidebars (HIGH)
Sidebars are the primary navigation surface for Mac apps. They appear on the leading edge and provide persistent access to top-level sections and content libraries.
Rule 4.1 — Leading Edge, Collapsible
Place the sidebar on the left (leading) edge. Make it collapsible via the toolbar button or Cmd+Ctrl+S. Persist collapsed state.
Use the source list style (.listStyle(.sidebar)) for content-library navigation. Source lists have a translucent background that shows the desktop or window behind them with vibrancy effects.
Sidebar items that can be reordered (bookmarks, favorites, custom sections) must support drag-to-reorder. Implement onMove or NSOutlineView drag delegates.
Mac users rely on keyboard shortcuts more than any other platform. An app without comprehensive keyboard support is a broken Mac app.
Rule 5.1 — Cmd Shortcuts for Everything
Every action reachable by mouse must have a keyboard equivalent. Primary actions use Cmd+letter. Secondary actions use Cmd+Shift or Cmd+Option. Tertiary actions use Cmd+Ctrl.
Keyboard Shortcut Conventions:
Modifier Pattern
Usage
Cmd+letter
Primary actions (New, Open, Save, etc.)
Cmd+Shift+letter
Variant of primary (Save As, Find Previous)
Cmd+Option+letter
Alternative mode (Paste and Match Style)
Cmd+Ctrl+letter
Window/view controls (Fullscreen, Sidebar)
Ctrl+letter
Emacs-style text navigation (acceptable)
Fn+key
System functions (F11 Show Desktop, etc.)
Rule 5.2 — Full Keyboard Navigation
Support Tab to move between controls. Support arrow keys within lists, grids, and tables. Support Shift+Tab for reverse navigation. Use focusable() and @FocusState in SwiftUI.
Esc must dismiss popovers, sheets, dialogs, and cancel in-progress operations. In text fields, Esc reverts to the previous value. In modal dialogs, Esc is equivalent to clicking Cancel.
The Delete key (Backspace) must remove selected items in lists, tables, and collections. Cmd+Delete for more destructive removal (move to Trash). Always support Cmd+Z to undo deletion.
Rule 5.6 — Space for Quick Look
When items support previewing, Space bar should invoke Quick Look. Use the QLPreviewPanel API in AppKit or .quickLookPreview() in SwiftUI.
In lists and grids, Up/Down arrow keys move selection. Left/Right collapse/expand disclosure groups or navigate columns. Cmd+Up goes to the beginning, Cmd+Down goes to the end.
6. Pointer and Mouse (HIGH)
Mac is a pointer-driven platform. Every interactive element must respond to hover, click, right-click, and drag.
Rule 6.1 — Hover States
All interactive elements must have a visible hover state. Buttons highlight, rows show a selection indicator, links change cursor. Use .onHover in SwiftUI.
Every interactive element must respond to right-click with a contextual menu. The context menu should contain the most relevant actions for the clicked item.
Rule 6.3 — Drag and Drop
Support drag and drop for content manipulation: reordering items, moving between containers, importing files from Finder, and exporting content.
// Accepting file drops from Finder
.dropDestination(for: URL.self) { urls, location in
importFiles(urls)
returntrue
}
Rule 6.4 — Scroll Behavior
Support both trackpad (smooth/inertial) and mouse wheel (discrete) scrolling. Use elastic/bounce scrolling at content boundaries. Support horizontal scrolling where appropriate.
Rule 6.5 — Cursor Changes
Change the cursor to indicate affordances: pointer for clickable elements, I-beam for text, crosshair for drawing, resize handles at window/splitter edges, grab hand for draggable content.
Support Cmd+Click for non-contiguous selection and Shift+Click for range selection in lists, tables, and grids. This is a deeply ingrained Mac interaction pattern.
Mac users are protective of their attention. Only interrupt when truly necessary.
Rule 7.1 — Use Notification Center Appropriately
Send notifications only for events that happen outside the app or require user action. Never notify for routine operations. Notifications must be actionable.
For recurring alerts, provide a "Do not show this again" checkbox. Respect the user's choice and persist it.
// AppKit — Alert with suppressionlet alert =NSAlert()
alert.messageText ="Remove from library?"
alert.informativeText ="The file will be moved to the Trash."
alert.alertStyle = .warning
alert.addButton(withTitle: "Remove")
alert.addButton(withTitle: "Cancel")
alert.showsSuppressionButton =true
alert.suppressionButton?.title ="Do not ask again"let response = alert.runModal()
if alert.suppressionButton?.state == .on {
UserDefaults.standard.set(true, forKey: "suppressRemoveAlert")
}
Rule 7.3 — Don't Interrupt Unnecessarily
Never show alerts for successful operations. Use inline status indicators, toolbar badges, or subtle animations instead. Reserve modal alerts for destructive or irreversible actions.
Rule 7.4 — Dock Badge
Show a badge on the Dock icon for notification counts. Clear it promptly when the user addresses the notifications.
Register for the Services menu to receive text, URLs, or files from other apps. This is a uniquely Mac integration point that power users rely on.
Rule 8.6 — Shortcuts and AppleScript
Support the Shortcuts app by providing App Intents. For advanced automation, add AppleScript/JXA scripting support via an .sdef scripting dictionary.
// App Intents for ShortcutsstructCreateDocumentIntent: AppIntent {
staticvar title: LocalizedStringResource="Create Document"staticvar description =IntentDescription("Creates a new document with the given title.")
@Parameter(title: "Title")
var title: Stringfuncperform() asyncthrows -> someIntentResult {
let doc =DocumentManager.shared.create(title: title)
return .result(value: doc.title)
}
}
9. Visual Design (HIGH)
Mac apps should look and feel like they belong on the platform. Use system-provided materials, fonts, and colors.
Rule 9.1 — Use System Fonts
Use SF Pro (the system font) at standard dynamic type sizes. Use SF Mono for code. Never hardcode font sizes; use semantic styles.
// SwiftUI — Semantic font stylesText("Title").font(.title)
Text("Headline").font(.headline)
Text("Body text").font(.body)
Text("Caption").font(.caption)
Text("let x = 42").font(.system(.body, design: .monospaced))
Rule 9.2 — Vibrancy and Materials
Use system materials for sidebar and toolbar backgrounds. Vibrancy lets the desktop or underlying content show through, anchoring the app to the Mac visual language.
Use the system accent color for selection, emphasis, and interactive elements. Never override it with a fixed brand color for standard controls. Use .accentColor or .tint only on custom views when appropriate.
Every view must support both Light and Dark appearances. Use semantic colors (Color.primary, Color.secondary, .background) rather than hardcoded colors. Test in both modes.
// SwiftUI — Semantic colorsText("Title").foregroundStyle(.primary)
Text("Subtitle").foregroundStyle(.secondary)
RoundedRectangle(cornerRadius: 8)
.fill(Color(nsColor: .controlBackgroundColor))
// Asset catalog: define colors for Both Appearances// Never use Color.white or Color.black for UI surfaces
Rule 9.5 — Translucency
Respect the "Reduce transparency" accessibility setting. When transparency is reduced, replace translucent materials with solid backgrounds.
// SwiftUI@Environment(\.accessibilityReduceTransparency) var reduceTransparency
var body: someView {
if reduceTransparency {
Color(nsColor: .windowBackgroundColor)
} else {
VisualEffectView(material: .sidebar, blendingMode: .behindWindow)
}
}
Rule 9.6 — Consistent Spacing and Layout
Use 20pt standard margins, 8pt spacing between related controls, 20pt spacing between groups. Align controls to a grid. Use SwiftUI's built-in spacing or AppKit's Auto Layout with system spacing constraints.
Keyboard Shortcut Quick Reference
Navigation
Shortcut
Action
Cmd+N
New window/document
Cmd+O
Open
Cmd+W
Close window/tab
Cmd+Q
Quit app
Cmd+,
Settings/Preferences
Cmd+Tab
Switch apps
Cmd+`
Switch windows within app
Cmd+T
New tab
Editing
Shortcut
Action
Cmd+Z
Undo
Cmd+Shift+Z
Redo
Cmd+X / C / V
Cut / Copy / Paste
Cmd+A
Select All
Cmd+D
Duplicate
Cmd+F
Find
Cmd+G
Find Next
Cmd+Shift+G
Find Previous
Cmd+E
Use Selection for Find
View
Shortcut
Action
Cmd+Ctrl+F
Toggle fullscreen
Cmd+Ctrl+S
Toggle sidebar
Cmd+0
Show/hide toolbar
Cmd++ / Cmd+-
Zoom in/out
Cmd+0
Actual size
Evaluation Checklist
Before shipping a Mac app, verify:
Menu Bar
App has a complete menu bar with standard menus
All actions have keyboard shortcuts
Menu items dynamically update (enable/disable, title changes)
Context menus on all interactive elements
App menu has About, Settings, Hide, Quit
Windows
Windows are freely resizable with sensible minimums
Fullscreen and Split View work
Multiple windows supported (if appropriate)
Window position and size persist across launches
Traffic light buttons visible and functional
Document title and edited state shown (if document-based)
Toolbars
Toolbar present with common actions
Toolbar is user-customizable
Search field available in toolbar
Sidebars
Sidebar for navigation (if app has multiple sections)
Sidebar is collapsible
Source list style with vibrancy
Keyboard
Full keyboard navigation (Tab, arrows, Enter, Esc)
Cmd+Z undo for all destructive actions
Space for Quick Look previews
Delete key removes selected items
No keyboard traps (user can always Tab out)
Pointer
Hover states on interactive elements
Right-click context menus everywhere
Drag and drop for content manipulation
Cmd+Click for multi-selection
Appropriate cursor changes
Notifications
Notifications only for important events
Alerts have suppression option for recurring ones
No modal alerts for routine operations
System Integration
High-quality Dock icon
Content indexed in Spotlight (if applicable)
Share menu works
App Intents for Shortcuts
Visual Design
System fonts at semantic sizes
Dark Mode fully supported
System accent color respected
Translucency respects accessibility setting
Consistent spacing on 8pt grid
Anti-Patterns
Do not do these things in a Mac app:
No menu bar — Every Mac app needs a menu bar. Period. A Mac app without menus is like a car without a steering wheel.
Hamburger menus — Never use a hamburger menu on Mac. The menu bar exists for this purpose. Hamburger menus signal a lazy iOS port.
Tab bars at the bottom — Mac apps use sidebars and toolbars, not iOS-style tab bars. If you need tabs, use actual document tabs in the tab bar (like Safari or Finder).
Large touch-sized targets — Mac controls should be compact (22-28pt height). Users have precise pointer input. Giant buttons waste space and look out of place.
Floating action buttons — FABs are a Material Design pattern. On Mac, place primary actions in the toolbar, menu bar, or as inline buttons.
Sheet for every action — Don't use modal sheets for simple operations. Use popovers, inline editing, or direct manipulation. Sheets should be reserved for multi-step workflows or important decisions.
Custom window chrome — Don't replace the standard title bar, traffic lights, or window controls with custom implementations. Users expect these to work consistently across all apps.
Ignoring keyboard — If a power user must reach for the mouse to perform common actions, your keyboard support is insufficient.
Single-window only — Unless your app is genuinely single-purpose (calculator, timer), support multiple windows. Users expect to Cmd+N for new windows.
Fixed window size — Non-resizable windows feel broken on Mac. Users have displays ranging from 13" laptops to 32" externals and expect to use that space.
No Cmd+Z undo — Every destructive or modifying action must be undoable. Users build muscle memory around Cmd+Z as their safety net.
Notification spam — Mac apps that send excessive notifications get their permissions revoked. Only notify for events that genuinely need attention.
Ignoring Dark Mode — A Mac app that looks wrong in Dark Mode appears abandoned. Always test both appearances.
Hardcoded colors — Use semantic system colors, not hardcoded hex values. Your colors should adapt to Light/Dark mode and accessibility settings automatically.
No drag and drop — Mac is a drag-and-drop platform. If users can see content, they expect to drag it somewhere.