UX Encyclopedia

Desktop Software & Professional Tools

Desktop = precision pointer, physical keyboard, big/multiple displays, long sessions, multitasking. Design for throughput and mastery.

Try it — two roads to the same command. Insert a horizontal rule in this mock editor twice: once by hunting the menus, once with the command palette (click into the editor, then Ctrl/Cmd+K). The counters keep score for each path.

Q3 planning notes

Budget review moved to Thursday. Draft the summary before standup.

Owners confirm headcount by Friday.

Menu path: —  ·  Palette: —

Try the menus first. Ctrl/Cmd+K only works while the demo editor has focus — on purpose: this very site’s search also claims ⌘K, which is the convention proving how standard it has become.

What changes vs. mobile/web

  • Keyboard is a first-class input: every frequent action gets a shortcut; standard chords respected (Ctrl/Cmd+C/V/Z/S/F, Ctrl/Cmd+N/W/T); full keyboard navigability (Tab order, arrow keys in lists, Enter/Esc in dialogs). Power users live on the keyboard — this is Nielsen heuristic #7 (accelerators) at full strength.
  • Hover exists: tooltips (with shortcut hints), hover previews, cursor changes as signifiers (pointer/text/grab/resize).
  • Fitts's law, desktop edition: screen edges/corners are fast targets (menu bar, taskbar); context menus appear AT the pointer (zero distance) — right-click menus on every object are a desktop expectation.
  • Windows are the user's: support resizing gracefully (min sizes, responsive panels), remember window/pane layouts, behave well across monitors and DPI changes.

Structuring pro apps

  • Command redundancy: important commands reachable ≥3 ways — menu (discoverable, complete), toolbar/context (fast), shortcut (expert). Menus are the app's searchable index of capability; macOS Help-menu search of menu items is the pattern to emulate.
  • Command palette (Ctrl/Cmd+K or Ctrl/Cmd+Shift+P — conventions set by VS Code, Figma, Linear, Slack, not any OS spec): one fuzzy-search box over commands, files, and navigation. It merges discoverability and speed, and doubles as a teaching tool — show each command's shortcut beside its palette entry so palette use trains shortcut use. Ship one in any tool with more than a few dozen commands; keep entries verb-first and synonym-matched.
  • Panels & density: dockable/collapsible panels; compact density options for data-heavy work (Fluent 2 ships density variants); resizable, sortable, keyboard-navigable tables.
  • Direct manipulation (Shneiderman 1983): visible objects, continuous feedback, rapid reversible incremental actions — drag to reorder, handles to resize, in-place editing.
  • Undo depth: multi-level undo/redo is non-negotiable in creation tools; make destructive operations undoable rather than confirmed (confirmation fatigue is real; undo preserves flow — Nielsen heuristic 3).
  • Progressive expertise: defaults for novices, preferences/customizable toolbars/scripting-automation for experts (Cooper's beginner→intermediate →expert "perpetual intermediates" argument: optimize for intermediates).

Multi-window & tiling

  • Both OSes now push window management: Windows 11 Snap layouts (and FancyZones via PowerToys), macOS gained native window tiling in Sequoia (2024). Consequence: your app will be run at half-, third-, and quarter-screen widths — desktop apps need responsive layouts too (collapsing panels, adaptive toolbars), not a fixed minimum canvas.
  • Support multiple windows of the same document/project where the domain suggests (compare two files, detach an inspector to a second monitor); remember per-window state and restore full window arrangements on relaunch. Respect full-screen mode and virtual desktops/Spaces.

Electron/web-stack vs. native: what users actually judge

The rendering technology is invisible; the tells are behavioral. Users (especially pros) notice: startup time and memory footprint, native-feel scrolling and text editing, IME/international input, drag-and-drop with the OS, correct menu bar on macOS vs. in-window menus on Windows, standard shortcuts per platform, and whether screen readers work (accessibility-API integration is a common web-stack gap). VS Code, Slack, and Figma demonstrate web-stack apps can meet the bar — each invests heavily in performance and per-platform conventions. If you ship cross-platform, budget explicitly for that polish; "one UI everywhere" reads as caring about neither platform. (Observation/convention, not a vendor spec.)

Long-session ergonomics

State persistence across launches (crash = reopen where you were); autosave + version history; respect OS conventions per platform (macOS menu bar & typography — including the Liquid Glass appearance from macOS Tahoe 26 onward — vs. Windows Fluent patterns vs. Linux desktop conventions); dark mode & reduced motion follow OS settings; multiple document interfaces: tabs and/or windows, user's choice.

Sources

  • Apple HIG — macOS (Menus, Windows, Keyboard) (developer.apple.com/design); Apple Newsroom (June 2025) — Liquid Glass across platforms incl. macOS Tahoe 26; macOS Sequoia release notes — window tiling.
  • Microsoft Fluent 2 & Windows app design guidance (fluent2.microsoft.design; learn.microsoft.com/windows/apps/design) — incl. Snap layouts.
  • Shneiderman, B. (1983). "Direct manipulation: A step beyond programming languages." IEEE Computer, 16(8); Designing the User Interface (6th ed. 2016).
  • Cooper, A. et al. (2014). About Face (4th ed.) — sovereign-posture applications, perpetual intermediates.
  • Nielsen, J. — heuristics 3 & 7 applications (nngroup.com).
  • Command palette: product convention (VS Code, Figma, Linear docs/blogs); no formal standard exists.
↑↓ to navigate · Enter to open · Esc to close