App Ops Desk · Issue #27
Support readiness is a ship gate
The release is not done when Connect says Ready for Sale. It is done when you can answer the first twenty angry emails without reverse-engineering your own build.
One action this week: Write a half-page known-issues note for the version you are about to ship — even if it only says “none known; last good was X.”
Before submit
- Known issues list (internal)
- Canned reply for top risk (login, paywall, sync)
- Link to last known good / workaround
- How to collect build number from users
- If applicable: remote kill switch / feature flag off path
User-facing build identity
Make build number visible in Settings (or About). Support without build numbers is astrology.
Failure modes
- Shipping then going offline for a weekend (see Issue #20)
- No way for users to tell you which build they are on
- Support email is an unmonitored noreply@
Bottom line
If you cannot support the build, you are not ready to ship the build.
Resources hub → Full library and jump-by-symptom links. Join the App Ops Desk waitlist Weekly release ops for people who ship alone.