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 70-second, 12-shot promo. It assigns 58.27 seconds to code or template rendering, 8.57 seconds to recordings or screenshots and 3.17 seconds to still-image motion. These rounded categories summarize the underlying picture; embedded assets can overlap and should not be added as extra runtime. Treat the classification as a proposed reconstruction route rather than proof of the original software.
Separate the frame from the content inside it
The proposed code project covers shots 1–7 and 9–12. Shot 10 explicitly needs a real UI recording. Make two lists before building: editable elements such as type, layout and transitions; source assets such as product recordings, logos and photographs. Record your own product in a clean state, including the interaction that makes the feature understandable. Do not ask a video model to invent an accurate working interface.
Rebuild image movement separately
Shot 8 is assigned to a roughly 3.2-second still-image move. A practical reconstruction starts from one suitable image and a defined start crop, end crop and duration. Preview whether the movement reveals useful information or merely magnifies pixels. Keep this step separate from the interface animation so changing a photograph does not force a rebuild of the whole promo.
Attach sound effects to actions
The report lists a click at 7.80 seconds on the Generate button and another at 25.80 seconds when sending a prompt. Use those as examples of event-based sound design. In your version, place the click when your button action happens; do not retain 7.80 seconds if the layout or pacing changes. The report also contains a low-confidence signal-detected effect near the end, so review the audio before treating every detected event as intentional.
Build a short proof before the full promo
Choose one interface shot with a real recording. 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, 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-compositing plan, shot 8 local rebuild and sound-effect table. Use your own product assets when applying the workflow.
Open the case and download its report →