Auxiliary Features Checklist
Use with Auxiliary features catalog and the class templates under Delivery classes. Essentials (identity, pipeline, packaging): App essentials checklist.
Mark N/A only with a written reason (e.g. “marketing site — no accounts”).
Desktop
Band A
-
Help menu / Help page (docs + report issue)
-
About: version + build id + channel
-
Check for updates (+ policy disable)
-
Safe apply (stage / quit / replace / relaunch)
-
Debug dump (redacted)
-
Open logs / config folders
-
Preferences with reset
-
Crash breadcrumb
-
Signed installer + uninstall
Band B
-
What’s new after update
-
First-run / onboarding
-
Single-instance (or documented multi)
-
Protocol/file handlers cleaned on uninstall
-
Tray/menu bar quit + status (if used)
-
Autostart opt-in (if used)
-
Offline/connectivity UI
-
Keyboard shortcuts reference
-
Accessibility baseline
Web
Band A
-
Build/version visible + API
/version(or equivalent) -
Help/docs entry
-
Error boundary + copy diagnostics
-
Auth session expiry UX (if any)
-
Privacy/cookie consent as required
-
Status/incident link (multi-user SaaS)
-
Connectivity honesty
-
Deploy/rollback pipeline
-
CSP/security headers baseline
-
PWA reload prompt (if service worker)
Band B
-
What’s new
-
Account settings (+ deletion if required)
-
Support contact with build id
-
Feature-flag dump
-
Client debug dump (redacted)
-
Accessibility baseline
-
Performance budgets on critical routes
Mobile
Band A
-
In-app version + build
-
Store update path (+ optional Open store CTA)
-
Help / FAQ + privacy/licenses in-app
-
Crash reporting with consent
-
Diagnostics/log export
-
Permission rationales + deny paths
-
Push consent + settings toggle (if used)
-
Offline/sync indicators (if sync matters)
-
Account deletion flow (if accounts)
Band B
-
What’s new on update
-
Deep/universal links verified
-
Backup/restore documentation
-
Tasteful in-app review prompts
-
Force-upgrade gate for breaking API
-
Accessibility (dynamic type, screen readers)