Release Quality Gates

Run these gates before you submit to a store or publish a direct installer. The goal is not bureaucracy. The goal is to catch release-only failures before users do.

Mandatory Gates

Gate	Evidence	Fails when
Release build installs	Clean device or VM install screenshot/log	Dev-only config, missing runtime, bad package identity
Signed artifact verified	Signature inspection output or Store signing confirmation	Unsigned binary, wrong cert, expired cert, wrong bundle identity
Versioning is monotonic	Version code/build number comparison	Store rejects older or duplicate version
Privacy inventory complete	Data-flow table and SDK list	Data safety/privacy labels are guesses
Listing assets complete	Asset checklist and screenshots from release build	Store blocks submission or listing misleads users
Update path tested	Previous public version updates to candidate	Updater metadata, signature, restart, or migration fails
Telemetry ready	Crash/ANR/logging dashboard link or equivalent	You cannot tell whether rollout is hurting users
Rollback plan written	One-paragraph halt/fix path	Bad release leaves no controlled response

Platform Gates

Android Play

AAB uploaded to internal testing.
Play App Signing/upload key path documented.
Target SDK meets current Play requirement.
Data safety and privacy policy reviewed against actual SDKs.
Pre-launch report reviewed.
Android vitals baseline known after rollout.

Microsoft Store/MSIX

Package identity matches Partner Center app.
Windows App Certification Kit run before submission.
Store listing has required screenshots and package images.
Certification notes include test credentials or special setup.
Publishing option chosen: immediate, scheduled, or manual hold.

Direct Windows Download

Installer and contained executables signed and timestamped.
Clean Windows VM download test uses the real public URL.
SmartScreen and Defender behavior recorded.
Uninstall and reinstall tested.
Updater or manual replacement plan tested.

Apple

Apple Developer Program membership verified.
Bundle ID and app record exist.
TestFlight build installed by a tester.
Privacy details and screenshots completed.
Release option chosen: manual, automatic, or phased.

Tauri/Electron

OS signing configured per target platform.
Updater keys/secrets stored outside repo.
Update metadata served over TLS.
Update from previous public version tested.
Rollback or emergency update process documented.

PWA Wrapper

Manifest, icons, service worker, and offline behavior tested.
Wrapper package identity documented.
Digital Asset Links verified for Android TWA.
Store metadata matches the web app.
Wrapper resubmission triggers are documented.

Simple Release Gate Record

# Release Gate Record

- App:
- Version:
- Channel:
- Artifact path:
- Signing evidence:
- Clean install result:
- Update result:
- Privacy review:
- Listing assets:
- Rollout plan:
- Rollback plan:
- Decision: ship / hold

Tip: Save this next to the app’s release notes. It becomes the fastest way to debug review failures and regressions later.