90‑Minute Feature Launch Kit: Contractor‑Ready Assets to Ship a Store‑Ready Microfeature

Start by limiting scope: a microfeature is a single UI flow or capability that’s discoverable from your home screen and testable end‑to‑end in staging. Examples: a ‘Share to X’ button, a single onboarding screen, or an in‑app referral card. The goal is a discrete change with a clear acceptance test.

Create a one‑page brief (5 minutes): feature description, user benefit (one sentence), exact navigation path, required test accounts or API keys, rollout flags, and the target locale(s). This brief is the single file contractors will use to deliver everything else.

Produce exactly these assets: 3–5 app screenshots (device‑framed), one 15–25s preview video, a locale‑aware JSON‑LD snippet for your marketing page, and a short acceptance test suite in plain text. Each asset targets a purpose: screenshots + video for ASO and conversion, JSON‑LD for search / rich snippets on your web landing page, and acceptance tests to speed reviewer or contractor verification.

Keep assets minimal but review‑safe: screenshots must be real in‑app frames (avoid fake UI that reviewers treat as non‑screenshot), videos should show real device interaction and include no objectionable terms, and acceptance tests should include the exact steps and test accounts reviewers need to validate the flow.

Screenshots — contractor brief: include device target, pixel size to deliver, locale text, and the exact in‑app navigation (e.g., Home > Actions > Share card). Point to App Store Connect’s screenshot spec to avoid scaling issues and ask for both 6.5" and 6.7" sizes if you support multiple display classes.

Preview video & story outline: request a single mixed screen recording trimmed to 15–25s, encoded to the store’s codec and corner‑radius rules. Provide a short shotlist (3 shots): entry screen, core interaction, confirmation. Reference the App Store and Play Console upload rules so contractors export in a compliant format.

Write acceptance tests as short, executable steps a reviewer or contractor can follow without developer support. Use this structure: Preconditions (environment, account), Steps (numbered), Expected Result (single sentence per step), and Edge Cases (2 items). That format collapses questions and speeds approval.

Add an App Review notes section for Apple and a Play Console testing note for Google explaining any nonstandard behaviour (feature flags, required login with test account, or server toggles). Apple explicitly asks for review information and can reject for incomplete review notes; include everything necessary to exercise the microfeature.

Package everything in a single ZIP and a short checklist email. The ZIP should contain: one README (the brief), screenshot originals + framed exports, the preview video (store‑ready and source), JSON‑LD snippet with feature metadata, acceptance.txt (tests), and a build link or TestFlight/closed‑track Play URL. This single package reduces back‑and‑forth and lets reviewers and internal stakeholders find assets quickly.

Run the 90‑minute sprint like this: 0–10m scope and brief, 10–30m wire and record screenshots/video (or annotate existing ones), 30–60m produce exports + JSON‑LD, 60–80m write acceptance tests and review notes, 80–90m package and send. If you use contractors, share the brief and deadline at 0m and reserve the final 10 minutes for QA.