Bilal Labs / Videos with Claude Opus 5.5
App Store preview video with one prompt
Lovely is my couples app. Its US App Store preview video, both the iPhone and the iPad version, came out of one prompt to Claude Opus 5.5 in Claude Code. The agent re-captured real app screens in the iOS Simulator, swapped the copy to English, fixed what looked wrong and rendered both files with Remotion.
The prompt
simdi us icin gereken her icerigi verdim, us store gorselelriin ve videosunu hazirlayabilir miins? baska eksik va rmi? [12 images attached: the US demo couple's photos] English: "I've now given you everything needed for the US. Can you prepare the US store screenshots and video? Is anything else missing?"
That is the whole prompt, typos included, in Turkish as I typed it. It is short because the project already had a pipeline: a brief, a Remotion composition for the Turkish preview, and simulator capture scripts, all built earlier with the same model. The prompt turned that pipeline into a new locale. If you start from zero, give the agent a brief like the one in the repo first.
What the agent did
- Read the existing marketing pipeline: demo seed data, simulator capture scripts and the SwiftUI marketing scenes.
- Saved the 12 attached photos as per-locale assets and changed the seed and scene code to load photos by locale.
- Wrote the en-US App Store metadata (name, subtitle, keywords).
- Ran the capture pipeline for en-US. It noticed the iPad status bar still showed a Turkish date, made the script set the simulator language per locale and captured again.
- Copied the English screens into the Remotion project and switched the on-screen copy to English.
- Checked frames and found the map pin crops were empty (US places sit elsewhere on the map), so it added English-specific pin coordinates.
- Rendered the iPhone (886×1920) and iPad (1200×1600) files, checked them with ffprobe and updated the project's CLAUDE.md.
Measured numbers
- Model: claude-opus-5-5 in Claude Code
- Wall-clock time: 40.5 min from prompt to both files (about 33 min of it was simulator capture)
- Model calls: 83
- Tokens: 43,592 output · 170 uncached input · 11,255,497 cache read · 242,290 cache write (1h)
- Cost at API list price: ≈ $5.06 (covers the screenshots and both videos)
- iPhone file: 886×1920, 30 fps, H.264 + AAC, 25.0 s, 17.4 MB
- iPad file: 1200×1600, 30 fps, H.264 + AAC, 25.0 s, 14.9 MB
Notes and pitfalls
- Apple's rules (App Store Connect → App preview specifications): 15–30 seconds, up to 30 fps, 500 MB max, H.264 or ProRes 422 HQ, .mov/.m4v/.mp4. iPhone 6.9" and 6.5" accept 886×1920 portrait; 13" iPad accepts 1200×1600 portrait. The default poster frame is at 5 seconds.
- Audio is optional; if present, Apple lists stereo 256 kbps AAC at 44.1 or 48 kHz.
- Use real screen captures of the app. My first Turkish cut animated static screenshots; I had it replaced with simulator recordings because a slideshow risks rejection.
- The poster frame (5 s) is what most people see. Keep it sharp: in an early cut a dim overlay made it look grey.
- The embedded videos here are compressed web copies. The uploaded files are the originals listed above.
Source
Prompt, source and notes: opus-video-recipes/app-store-preview. Framework choice: HyperFrames vs Remotion vs Manim.
FAQ
Was it really one prompt?
For the US version, yes: one message plus 12 photos, then "looks great, upload it". The pipeline it reused (brief, Remotion composition, capture scripts) was built in earlier sessions, also with Claude Opus 5.5.
Why Remotion and not HyperFrames here?
The content project already had a Remotion setup from an earlier video, so the agent extended it. The other recipes on this page use HyperFrames; the comparison page covers when each fits.
What does it cost?
This run used about 11.3M cache-read tokens and 44K output tokens. At Opus 5.5 list prices ($4 input, $20 output, $0.20 cache read, $8 1h cache write per million) that is about $5, including the screenshots.