nw-ux-desktop-patterns

# Desktop Application UI Patterns Actionable desktop interface patterns for requirements gathering and design review. Use when target platform is native or cross-platform desktop application. ## Native vs Cross-Platform **Native advantages**: Platform conventions feel familiar | better system integration (file dialogs, notifications, drag-and-drop) | consistent OS look and feel | better accessibility through native APIs. **Cross-platform tradeoffs**: Shared codebase reduces cost | visual consistency may conflict with platform expectations | custom rendering may miss OS accessibility features. **Guidance**: If users primarily on one platform, prioritize native conventions. If cross-platform required, follow each platform's conventions for core interactions (menus, shortcuts, window management) while sharing domain-specific UI. ## Core Desktop UI Elements ### Menu Bar Primary access point for all commands. Organize by convention: File, Edit, View, then domain-specific, ending with Window and Help. Every item should have keyboard shortcut for frequent actions. Group with separators; submenus sparingly (one level deep preferred). ### Toolbar Quick access to most common commands (subset of menu bar). Should be configurable: show, hide, rearrange. Every button must have tooltip. Include both icon and text label for primary actions. ### Status Bar Displays contextual info: document stats, cursor position, connection status, mode indicators. Low-profile: supports awareness w...