Launch Films for Physical Products vs Software Products

Why software launches need a different structure from physical ones, how to show something that has no physical form, and what each category can borrow from the other.

A physical product launch and a software launch look like the same brief and are structurally different. One has an object that can be revealed, admired and desired. The other has an interface, a workflow and an outcome, none of which are visually interesting in themselves. Applying the physical product structure to software produces a film full of screen recordings that nobody watches.

The physical launch has a natural dramatic shape because there is something to withhold. The film can build toward a reveal, hold the object at its best angle, and let the audience want it. The craft questions are about light, material, angle and timing, and the emotional response is partly aesthetic. This is why physical product films can succeed with very little explanation.

Software has no equivalent moment, and pretending otherwise is the common error. A dramatic reveal of a dashboard is not a reveal, because nobody desires a dashboard. What a software audience wants is not the product but the outcome: the report that used to take three days now takes an hour, the errors that stopped happening, the thing they no longer have to do. The film's job is to make that outcome concrete.

The structure that works for software therefore starts with the problem rather than the product, and it stays with the problem longer than feels comfortable. Show the situation before, specifically enough that the viewer recognises it, then show what changes. The interface appears as evidence of how the change happens rather than as the subject. A film that spends forty of its sixty seconds on the problem and the outcome, and twenty on the product, outperforms the reverse.

Screen material needs deliberate treatment because raw recordings are unwatchable. Real interfaces are dense, small and full of irrelevant detail. The workable approach is to simplify: crop to the region that matters, scale it up, remove or blur what is not being discussed, and animate the sequence at a pace a viewer can follow rather than at the speed a user would click. This is design work rather than capture.

The cognitive constraint applies directly here. Beege and Ploetzner (2025), studying learning from interactive video, examined how navigation and cognitive load influence what viewers take from video material, and Ludwig et al. (2026) found that instructional design and cognitive load affect knowledge acquisition. A screen sequence showing six features simultaneously exceeds what a viewer can process, and the information is lost rather than diluted. One idea per beat, held long enough to register.

Both categories share a preannouncement problem and can learn from each other. Wang et al. (2022) found that the specificity of what is disclosed in a new product preannouncement interacts with audience characteristics in shaping word of mouth, and Chen et al. (2025) found that preannouncement content materially changes the engagement it produces. Software launches typically disclose too much too early, publishing feature lists before anyone cares; physical launches typically disclose too little, mistaking mystery for interest.

Where software can borrow from physical launches is in the treatment of a hero moment. Even without an object, a film can build to a single frame that carries the product's identity: the result appearing, the number changing, the queue clearing. Designing that moment deliberately, and landing it with the music, produces the small physical response that a feature walkthrough never generates.

Where physical launches can borrow from software is in demonstrating outcome rather than attribute. A physical product film that shows the object beautifully and never shows what it does for anyone is a common and weak construction. Poushneh (2021) found that perceived proximity to a virtual product influenced purchase intention, and proximity is created by showing the thing in use as much as by showing it in isolation.

The production method differs accordingly. A physical launch justifies investment in 3D and in the accurate representation of the object, since the object is the point. A software launch justifies investment in motion graphics, in the simplification of screen material, and in the depiction of the situation around the software, which is frequently where generated environments earn their place. Both need the same discipline about accuracy: a software film showing an interface the product does not have is the exact equivalent of a product film showing a colour that will not ship.

References

Beege, M., & Ploetzner, R. (2025). Learning from interactive video: The influence of self-explanations, navigation, and cognitive load. Instructional Science, 53(1), 99–119. https://doi.org/10.1007/s11251-024-09693-5

Ludwig, S., Rausch, A., & Taub, M. (2026). Effects of instructional design, instructional preferences, and cognitive load on problem solving and knowledge acquisition in a computer-based office simulation. Learning and Instruction, 101, Article 102255. https://doi.org/10.1016/j.learninstruc.2025.102255

Wang, X., Liu, Y., Wang, S., & Chen, H. (2022). Keep it vague? New product preannouncement, regulatory focus, and word-of-mouth. Journal of Retailing and Consumer Services, 65, Article 102847. https://doi.org/10.1016/j.jretconser.2021.102847

Chen, M., Zhang, X., & Wang, F. (2025). How to introduce? The effects of new product preannouncement content on consumer engagements in enterprise social media. Journal of Retailing and Consumer Services, 84, Article 104213. https://doi.org/10.1016/j.jretconser.2024.104213

Poushneh, A. (2021). How close do we feel to virtual product to make a purchase decision? Impact of perceived proximity to virtual product and temporal purchase intention. Journal of Retailing and Consumer Services, 63, Article 102717. https://doi.org/10.1016/j.jretconser.2021.102717