App Preview Video
This folder is both an installable skill and the runnable Remotion template. Read README.md for tested setup and commands. Read the scene-plan interface when creating a plan and Apple requirements for App Store mode. For fresh capture, use the capture guide.
Intake and evidence
Accept recordings folder, mode (launch or app-store), app name, brand assets, language and creative brief. Default to English, portrait, 30 seconds for launch or 25 seconds for App Store. Follow the app's own design by default; do not silently apply the fictional example's colours, font or visual style. Never invent current app capabilities.
Run npm run doctor, then inspect footage with npm run inspect -- --recordings DIR --out NEW_DIR. Read the inspection JSON and reference frames, and review full clips for actions, sensitive data, test UI, loading, and truthful sequence. Stills alone are not content verification. If full playback is unavailable, record that limit and keep manual review pending.
Collect capture version, device, date and simulated conditions. Keep real app assets outside the public package. Ask for missing footage when a requested moment is absent. Do not replace it with generated UI, reverse time to imply a different result, or relabel simulator footage as physical-device capture.
Brand discovery before rendering
First inspect supplied assets and the relevant app project, screenshots or recordings for the real logo/app icon, colours, typography, surfaces, corner shapes and motion style. Use assets already supplied or verifiably present; do not ask the user to re-upload them. If several logo versions are plausible, ask which is current. If no logo is available, ask for its file/path and wait before rendering; continue footage inspection while waiting. A user can explicitly choose a text-only/no-logo treatment. Never invent or silently omit a logo.
Use the app's design tokens when available and visually compare them with current footage. If the typeface is unavailable locally, explain the fallback rather than claiming an exact match. Record the design sources and decisions in the private scene plan or accompanying report. Put the real logo in the plan's logo field; set colours and optional design tokens using the scene-plan reference. Keep real brand assets outside this distributable repository.
Show a representative opening-frame preview and caption style before a full render. Invite corrections; do not introduce an extra approval gate if the user has already specified the design and asked you to render. Use the restrained design.layout: "app" launch treatment when it fits the app, or adapt the composition to the supplied design. Do not substitute a generic dark frame, all-caps wordmark or decorative shapes for the app's identity.
Capture provenance belongs in provenance and capture and is always retained in the report. For launch videos, leave disclosure empty by default unless an on-screen disclosure is requested or necessary to avoid a misleading claim. Do not automatically burn simulator/device/location metadata into the marketing video. This does not remove meaningful login/paid-access disclosures, the fictional-demo label, or App Store capture requirements. Never present simulated location as an actual completed walk or relabel simulator footage as device footage.
Edit and render
Create a scene plan with actual source trim points, brief readable captions, and an evidence description per scene. Use one coherent journey with a useful action in the opening seconds. Preserve legibility and input proportions. Use examples/launch.json or examples/app-store.json as a structural starting point, replacing every fictional claim and source reference.
Launch mode permits a frame, headline, CTA and branded background. App Store mode shows the app with restrained captions and access disclosures; no fake device interaction or fabricated UI. The bundled demo is explicitly fictional, never an Apple submission asset. This v1 requires device provenance before calling a real app edit submission-oriented; technical checks alone never establish content compliance or acceptance.
Run npm run render -- --recordings DIR --plan PLAN.json --out NEW_DIR. Output folders must be new to preserve evidence. The tool normalizes trimmed media, renders through Remotion, encodes MP4, creates a poster and writes provenance, hashes, timing and technical checks. Sources remain unchanged. Music is optional, user-supplied, licensed, and at least as long as the edit. Source audio defaults to muted.
Review and delivery
Review the entire finished MP4 with audio and muted at phone size. Check all cuts, disclosures, captions, claimed actions and audio. If problems are found, revise the scene plan and render into another folder; preserve first render and describe the real correction.
Report separately: technical validation, manual playback/content review, source provenance and Apple acceptance. Never turn pending into passed based on a few screenshots. Provide the MP4, poster, editable project/scene plan, report and remaining limitations. No upload, submission, cloud rendering, paid assets or publishing is implied.