Updated
Case evidence: Read the source breakdown report · View case frames and shot timings
Based on a published tool report. Production classifications are analytical judgments; suggested steps are not the original project or a verified recreation.
Read the report as a production map
The v10 report describes a 1:10 (70-second) horizontal promo with 9 shots, about 7.8 seconds each on average. It classifies the whole picture as code or template rendering, with an overall reliability of 89%, and lists 4 open questions. Treat the classification as a proposed reconstruction route rather than proof of the original software, and read the open questions before you commit to a plan.
Separate the frame from the content inside it
The report's visual review describes a flat UI tilted under a CSS-style 3D perspective, a vector cursor moving in straight lines at constant speed, and layouts, fonts and colours that match across shots: the same code-drawn UI, not a screen recording. It proposes one Remotion/HTML project for shots #1–#9. Make two lists before building: editable elements such as type, layout, cursor moves and transitions; source assets such as the logo (shots #2 and #9) and the pictures shown inside the interface. If your own product needs to show real behaviour, record it yourself rather than asking a video model to invent an accurate working interface.
Review the uncertain shots before rebuilding
Two shots carry open questions. In shot #5 (38.9–41.2 s), three cards count up to “done”; whether the pictures embedded in them are real material or generated is unconfirmed, and the review reads them as stills that look AI-generated. Shot #6 (41.2–44.5 s) is labeled code rendering at only 55% confidence: one measurement fitted the whole frame to a single still-image move, but the review saw the cursor and a progress bar moving inside the page. For your version, decide what each card or thumbnail must show, source that image, then animate it in code.
Attach sound effects to actions
The report finds no voice-over, background music at about 112 BPM (source unconfirmed; closest to library music at 52%) and a single sound effect: a pop at 60.6 seconds, for which the table names no matching picture event. Scene changes sit near the music's section points at about 19.5, 38.5 and 55.5 seconds. Use these as examples of event-based timing: in your version, place an effect where your visual event happens instead of copying 60.6 seconds, and listen to the separated effect track before treating a detected sound as intentional design.
Build a short proof before the full promo
Choose one interface shot, such as shot #1 (0–8.8 s: a tagline, then the app UI sliding in and the cursor choosing a mode). Verify readable text at the intended viewing size, a clear focal point and enough time to understand the action. Then test one transition into the next shot and one sound cue. Only after that should you extend the composition across the timeline. The report supplies a plan and per-shot element timings, not the original editable project, and it does not certify the source or license of the soundtrack.
A reusable analysis template
Shot / reference time / communication goal Editable layout and motion Real recording or image required Start and end states / duration Caption track / action-linked sound cue Asset ready? / preview result / next fix
Practice with a real report
Open the v10 report to compare the code-build plan, the per-shot motion timelines, the sound table and the open questions on shots #5 and #6. Use your own product assets when applying the workflow.
Open the case and download its report →