GUI Applications

GUI apps are where About, Help, debug dump, installer, and auto-update show up as visible product features. Parent: Software Product Essentials.

For the full Band A/B/C auxiliary matrices, use the delivery-class templates (GUI alone is not enough detail):

Must-ship surfaces

  • Help — docs entry, shortcuts, report issue

  • About (menu: Help → About, or app menu on macOS) with version, build id, channel — About and build info

  • Debug dump button on that dialog — How-to

  • Settings with paths to logs/config or a “Open logs folder” action

  • Update affordance — check now / restart to update — Automatic updates

  • Installer with uninstall (desktop) — Distribution

Desktop OS emphasis

  • Windows: MSI/MSIX or winget-friendly installer; code-sign; auto-update or Store/winget before 1.0 — Windows auto-updates, Winget

  • macOS / Linux: prefer Store/Sparkle/Homebrew or distro/Flatpak/AppImage; quit → replace → relaunch (never overwrite a running ELF) — Unix/macOS auto-updates

UX notes

  • Do not hide version solely in logs

  • First-run may mention crash reporting opt-in; do not bury it forever

  • High-DPI, accessibility, and keyboard paths are product quality—not separate from “essentials,” but tracked in your UI standards

Mobile

Stores own distribution and updates; you still need in-app version display, Help, log export for support, permission rationales, and crash reporting (opt-in where required by policy). Full list: Mobile template.

Checklist

  • Help reachable (docs + report issue)

  • About shows version + build id + channel

  • Dump button produces redacted zip

  • Update path live on every supported desktop OS

  • Signed installer + uninstall (desktop)

  • Open logs / config from UI

  • Changelog linked from About or Help

  • Class template rows triaged (desktop and/or mobile)