Reviewer Packs

App Store reviewers, marketplace reviewers and security teams don't want a slick launch video. They want to see that a flow works, with nothing hidden. A Reviewer Pack gives them exactly that, built from the same take you use everywhere else:

• A conservative cut. No automatic zoom, a calm pointer with a highlight ring, no background or padding, and captions on. Whatever style the take uses for marketing, the pack's video ignores it.
• A proof manifest. manifest.json records what was tested and on what: the app and its version, macOS, the flow, every scene and how many attempts it took, each assertion with its result and time, the source commit when there is one, the SHA-256 of the video, and an honest list of the edits applied.
• Reviewer notes. reviewer-notes.md explains the setup and the steps, lists what was verified, says who acted, and discloses the editing.

DemoTake helps you document how your app works. It doesn't guarantee approval by Apple or any other marketplace.

#Start a reviewer take

Choose File › New Reviewer Take… (⇧⌘N). It opens the New Take sheet with the Reviewer purpose selected: "Conservative: no unnecessary zoom or deceptive cuts, credentials masked, a verified manifest and reviewer notes." Write the goal as the thing to prove, such as "Prove the reviewer can sign in and create an invoice", and plan one scene per step. For a TikTok, Meta, Google or Apple review, also fill in the sheet's Platform review section; see Scenes and takes.

You can also make any existing take into a pack. Right-click it in the library and choose Reviewer Mode. In the editor, choose Open in Reviewer Mode from the menu next to Export, or from the Take menu.

#Assertions: what makes it proof

An assertion is a check that the app really reached a state: an element exists, some text is visible, or a state you confirm by hand. Agents add assertions while they record, using tools like assert_text and assert_element. In Reviewer Mode you can add your own with Add Assertion and choose Visible Text, Element Exists or Manual Check.

Each assertion appears as a marker on the reviewer cut's timeline and in the Assertions list, where you can Mark Passed or Mark Failed, re-check an element or text assertion with Re-check Now, or jump to its time. When every assertion passes, the take shows Proof Verified. If some fail, it shows Checks Failing, and Review Failed Checks takes you to the first one.

#Reviewer Mode

Reviewer Mode is where you check the proof before sending it. The reviewer cut plays on the left; the verdict, manifest and assertions sit on the right.

• Reviewer Notes. Write what a reviewer should know, such as setup, the test account and what to look for. Generate drafts notes from the take's trace and assertions. Notes save as you type.
• Status line. Under the video: assertions passed, regions masked, and whether notes are written.
• Manifest. App, version, macOS, flow and commit. The video hash appears once you export a 16:9 video or a pack; until then the panel says Export 16:9 to bind the video hash.
• Review. Mark Reviewed sets the take to Proof Verified. Request Changes marks it Needs Review.

#Platform review

Under the video, the Platform review section checks the take against a specific app review before you upload. Pick the platform in Review for (TikTok, Meta App Review, Google OAuth or Apple Review), enter the App URL and the Scopes, then click Check. After a change, click Check Again. A Reviewer take set up for a platform in the New Take sheet is checked as soon as you open it.

Each check shows whether it passed, needs a look, failed or couldn't be checked yet, with what to fix. For example, a file that is too big says to export again with Upload-friendly quality and Keep under a size (see Formats and sizes).

Copy Checklist copies a checklist you can paste into the review form: the demo video's file, size and length, the website shown, the steps shown, which scene demonstrates each scope, which sign-in and consent steps a person did, and a note that waiting time was shortened.

You can check any take, not only Reviewer takes. Checking doesn't change the take: the Reviewer Pack export uses the reviewer style on its own copy. For the whole workflow with an agent, see Platform review videos.

#Export the pack

Click Export Reviewer Pack in the Reviewer Mode toolbar, or pick Reviewer Pack in the editor's Export sheet. The arrow next to the button also offers MP4 Video, Screenshots, Copy Reviewer Notes and Share Link….

The pack is one ZIP in the take's exports folder:

checkout-redesign-reviewer.mp4   # the conservative cut, 1920 × 1080
manifest.json                    # the proof manifest
reviewer-notes.md                # notes, steps, what was verified, editing disclosures

If you haven't written notes yet, DemoTake drafts them when it builds the pack. The notes file has your notes, a numbered Steps list (one per scene, with its intent), a Verified checklist of assertions, Who acted (how many steps were done by the agent, by an automation tool or by a person, and which steps a person did, such as signing in), and Editing disclosures. The pack video goes through the same export checks as every other video.

#What the manifest says

The manifest is JSON a reviewer, or a script, can read:

{
  "flow": "Prove the reviewer can sign in and create an invoice",
  "appName": "Aurora",
  "appVersion": "2.4.0",
  "buildNumber": "418",
  "macOSVersion": "Version 15.6 (Build 24G84)",
  "assertionsPassed": 3,
  "assertionsTotal": 3,
  "scenes": [{ "title": "Sign in", "status": "recorded", "attempts": 1 }],
  "actionsBySource": { "agent": 9, "human": 2 },
  "humanSteps": ["Sign in to Aurora"],
  "sourceCommit": "9f2c1ab",
  "videoFile": "checkout-redesign-reviewer.mp4",
  "videoSHA256": "3f9a1c…",
  "editDisclosures": [
    "Waits over 1.5 s shortened to 0.6 s (still visible).",
    "Sensitive regions blurred.",
    "Pointer is a presentation layer synthesized from recorded actions."
  ]
}

The edit disclosures are written for you from what the take actually does: shortened waits, sped-up ranges, trimmed scene edges, cropped scenes, re-recorded scenes ("each scene is a single continuous take"), removed scenes, blurred regions and the synthesized pointer. A trial export adds "Exported with a trial watermark." Agents fetch the same manifest with export_manifest.

#Send it to a reviewer

• Attach the files. Paste the notes into your review submission and attach the video from the ZIP.
• Send a private link. Share with External Reviewer… opens the Share sheet with the latest Reviewer Pack selected, or renders a new one first. A private link with an access code keeps it to the reviewer, and the link page shows the verification details from the manifest. See Share links.

#Next

• Share links
• Redaction
• The Reviewer Mode overview, and the story of a Google OAuth verification video