storebound/media/teaser/README.md
CRT 0092a67fc7 Teaser remake: inbox hook, real scan and re-scan, screenshot wall, Data safety, three desktop scenes, Submit card
New cut on the approved storyboard (33.75 s, every cut on the 128 BPM beat): rejection mails in a generic inbox,
storebound scan typed on black with its real output (tests/fixtures/scan/teaser), the re-scan of the fixed copy
(new fixture teaser-fixed) flipping five reds to green, 200 store screenshots, 764 Data safety answers, the desktop
app's Portfolio, release timeline (rollout to 20%) and Checks tab, then the Submit card and the logo.
60 fps capture blended to 30 fps for motion blur, whip / mask / zoom transitions, sound design on every cut,
a 1280x720 web version. tests/teaser.test.ts checks the scan text, beat grid, caption length and holds.
2026-10-11 23:54:19 +08:00

4.4 KiB

storebound teaser (about 34 s social video)

A scripted motion piece, not a screen recording. Every frame is a pure function of time, rendered from an HTML/CSS/JS timeline in headless Chrome and encoded with ffmpeg. The music and the sound design are original and synthesized from scratch in the same browser (Web Audio OfflineAudioContext): no samples, no downloaded audio, nothing to license.

s scene
0.00-3.28 hook: a generic, made-up inbox; three rejection mails stack up, then "Rejected. Again."
3.28-11.25 hard cut to black: storebound scan is typed; the real output: SDKs with file:line, five findings with guideline and fix, the camera on each
11.25-14.06 the re-scan after the fixes: the five reds flip green, 0 blockers
14.06-16.88 the store screenshot wall (the demo game's real renders), 200 store screenshots
16.88-19.69 the declarations proposal from the scan, Data safety answers ticking, 764 answers
19.69-28.13 the desktop app (real frames, fixture data): Portfolio across studios · release timeline, rollout filling to 20% · Checks, rejection risks turning green
28.13-30.94 "It never presses Submit. You do." over a Submit button
30.94-33.75 logo, storebound.dev, Open source · macOS · Windows · Linux
file what
script.js the timeline: 128 BPM, scenes in beats (every cut on the beat), captions, the inbox, the scan lines, the desktop camera, the sound cues
desktop.ts the desktop scenes' frames: apps/desktop's Vite dev server in fixture mode (VITE_FIXTURES=1, example.com-style data), captured headlessly in dark at 1280x800 @2x with the dev markers hidden, plus boxes.json (cursor and callout targets) -> out/desktop/
index.html + teaser.js the picture; window.teaser.seek(t) sets every element for time t
music.js music (F minor: tense intro, silence for the typed command, the groove from Enter, a calm bar under Submit, the logo hit) and sound design: mail blips, key clicks, a whoosh into every whip / mask / zoom, a hit on every cut, ticks on findings, rising chimes on fixes
render.ts frames at 60 fps blended to 30 fps (motion blur) -> ffmpeg (H.264 high, yuv420p), sound -> loudnorm (-14 LUFS, -1.5 dBTP), mux, posters, the 1280x720 web version
icons/ the mouse cursor and the UI icons: Phosphor files copied unchanged by bun tools/site-icons.ts (no hand-written SVG; CI checks it)
poster.jpg end card still (1920x1080, small)

The scan text is the real storebound scan output of tests/fixtures/scan/teaser (five classic App Review rejections) and, after the fixes, of tests/fixtures/scan/teaser-fixed; tests/teaser.test.ts runs both scans and checks every line the video shows, the beat grid, the caption lengths (at most 7 words) and holds (at least 1.2 s), and that every scene holds at least 2.5 s. Each fix line shows a verbatim piece of the real fix. The mail list is fictional: no real names or addresses, no mail-app branding. The desktop scenes are real frames of the app on its fixture data; the "after" Checks frame is the same tab with the fixture's scan answering no findings.

Render

Needs Bun, ffmpeg and Playwright (repo devDependency; Playwright's Chromium or an installed Google Chrome).

# optional, for the real screenshot wall: the demo renders (otherwise crops of docs/img/showcase.jpg are used)
cd examples/demo-game && bun serve.ts & bun ../../cli/index.ts shots capture && bun ../../cli/index.ts shots fonts && bun ../../cli/index.ts shots render
# from the repo root
bun media/teaser/render.ts                       # both formats, sound, posters, web version: about 15 min
bun media/teaser/render.ts --desktop             # capture the desktop app frames again (after a UI change)
bun media/teaser/render.ts --only v              # vertical only (h = horizontal; the web version is made from h)
bun media/teaser/render.ts --stills 2,12.5,30    # PNG stills in out/stills for a quick layout check
bun media/teaser/render.ts --serve --port 8750   # live preview: /index.html?w=1080&h=1920&play=1 (or &t=12.5)

Outputs (gitignored) in media/teaser/out/: teaser-1080x1920.mp4 (X / TikTok / Reels), teaser-1920x1080.mp4 (X / YouTube), teaser-web.mp4 (1280x720, about 3.5 MB, for the site) with poster-web.jpg, -silent variants, poster-*.jpg, music.wav.

The vertical layout keeps captions inside the centre 80% and the bottom ~22% free of key text for app overlays.