Delivery Classes

Delivery class answers: where does the end user run this, and how do updates and Help arrive? It complements artifact type (library, GUI, CLI, …).

Parent

Software Product Essentials

Shared vocabulary

Auxiliary features catalog

Classes

Class Typical shells Template

Desktop

Native GUI, Electron/Tauri, tray apps, packaged CLI+GUI hybrids on Win/macOS/Linux

Desktop apps

Web

Browser SPA/MPA, SSR apps, PWAs, admin consoles, SaaS frontends

Web apps

Mobile

iOS / Android (native, Flutter, RN, …); tablets when store-distributed

Mobile apps

How to use the templates

  1. Identify every shell you ship (e.g. Windows GUI + optional web dashboard).

  2. For each shell, open the matching class page and copy its auxiliary feature matrix into the project plan or issue tracker.

  3. Mark each row Done / Deferred (with reason) / N/A.

  4. Wire Band A items before calling 1.0.

  5. Reuse shared deep dives (About, updates, packaging, diagnostics) rather than reinventing per repo.

Multi-shell products

Example: a desktop client + marketing site + account portal.

  • Desktop template → installed client

  • Web template → portal and marketing (lighter Band A for marketing; full for the logged-in app)

  • Shared one version truth across API and clients when protocols break

Related artifact types

  • GUI apps — About/dump/installer emphasis (desktop + mobile GUI)

  • CLI / TUI — often ship beside a desktop class

  • Services — backend for web/mobile; health/version still apply

  • UI-heavy web applications — browser performance/architecture (portal)