macos-app-design

Guide for designing and implementing native-feeling, "good Mac citizen" apps: fast, elegant, accessible, and deeply integrated with macOS workflows. Do: Don't: Identify your app type first: For complete design system details, Icon Composer workflow, SF Symbols guidance, evaluation rubrics, and Definition of Done checklist: See: references/macos-design-guide.md - Prefer system components and conventions over bespoke UI—fastest path to "feels right on Mac" - If you customize bars, backgrounds, borders, or control chrome : stop and justify it - Use for navigation/controls layer (toolbars, sidebars, bars) - Let system components provide built-in behaviors - Apply to content layer (tables, lists, document content) - Stack "glass on glass" - Document-based : Files as primary units (open/save/duplicate) - Library + editor : Sidebar lists items, detail in main area - Utility : Single window, optional menu bar - Menu-bar app : Lives in menu bar, minimal UI - Pro tool : Dense, power-user workflows - App archetype identified - Information architecture (sidebar structure, navigation, window model) - Command map (menus + keyboard shortcuts for every major feature) - State + data model (persistence, undo/redo, concurrency) - Accessibility plan (VoiceOver, keyboard, contrast, reduce motion)