App Ops Desk · Issue #3
Metadata freeze day
Binary ops and store metadata are different jobs. Mixing them on release day is how solo founders lose hours to screenshot crops, subtitle debates, and review-note rewrites while processing spins.
One action this week: Pick a metadata freeze moment at least a day before your intended submit.
After freeze, only binary/blocker fixes are allowed unless the store page is factually wrong.
What counts as metadata
- Name, subtitle, promotional text
- Description, keywords
- Screenshots / previews / app preview video
- Support URL, marketing URL, privacy policy URL
- Review notes, demo account, attachment
- What’s New text
Failure mode: infinite polish loop
Symptom: Build is ready, but you’re still “quickly” re-exporting screenshots at 11pm.
Perfect store pages don’t ship. Frozen-good pages plus a clean binary do. Solo founders often use metadata thrash to avoid the scariness of submit. Name it and stop.
Run a freeze day
- Morning: export final screenshots from the release candidate UI, not a random debug build.
- Midday: lock subtitle + What’s New against the actual build contents.
- Afternoon: write reviewer notes for anything non-obvious (hidden settings, entitlements, account needs).
- End of day: freeze. Put files in a dated folder: store/1.5.0/.
- Next day: binary preflight + upload. Metadata only changes for factual errors.
Review notes that reduce bounce
Build: 1.5.0 (214) Account: demo@… / temporary password How to reach the feature under review: 1) ... 2) ... Note any region, hardware, or permission requirements. Contact: you@email (hours)
Reviewers are not your beta community. They need a short path to the thing you’re claiming.
What’s New without lying
- Lead with user-visible changes
- Don’t advertise work that isn’t in this build
- Keep crash-fix notes human, not engineering dump
Copy/paste metadata freeze checklist
- Screenshots taken from RC UI on required device sizes
- Subtitle/keywords match current positioning (not last quarter’s experiment)
- Privacy policy URL loads and matches current data practices
- Support URL works on mobile
- Review notes include build number + path to feature
- What’s New matches this binary
- Assets stored under versioned folder
- Freeze declared; only factual edits allowed after