Product Videos Built From Code, With No Customer Data on Screen

A product film built from code rebuilds the software's screens as a web page, fills them with invented demo data and exports an animated video. Nothing is recorded from a real account, so no customer's name, figures or records ever appear. Every word on screen is treated as a claim, and the business approves the film before it is published.

What is a product film built from code?

It is a short video of software in use, where each screen is redrawn as a web page rather than captured from the live product. The page is animated, with clicks, typing and transitions, and then exported as a video file. Because the source is code, it can be edited, translated or updated without re-recording anything.

Product films are now standard. According to Wyzowl's 2026 survey, 91% of businesses use video as a marketing tool, though that is a small vendor survey. For software companies, a 30 to 90 second film of the product working is often the most persuasive asset on the homepage.

Building from code changes how those films are made. Instead of a screen recording edited after the fact, the film is a page that can be changed like any other.

Why not just record the screen?

Screen recordings show whatever is in the account: real customer names, real figures, real staff. Blurring is easy to miss and easy to undo. Recordings also go out of date the moment the interface changes. Rebuilding screens from code removes the data risk entirely and makes updates a quick edit instead of a reshoot.

Privacy is the main reason. According to Australia's privacy regulator, the Privacy Act applies to uses of AI involving personal information, and customer records shown in a public video are personal information on display. A rebuilt screen never contained the real data, so there is nothing to leak.

Consistency is the second reason. A recorded film shows whatever state the demo account was in that day. A built film shows exactly the state the script calls for, every time.

How are the screens rebuilt?

The interface is measured from real screenshots: colours, spacing, type, components and layout. Those measurements become a small kit of reusable parts. Each film screen is then assembled from the kit and filled with invented demo data, such as fictional companies and people, so the film looks like the product without showing anyone real.

The kit is the important asset. Once built, it lets every future film use the same accurate components, so screens look consistent across films and stay true to the product.

Demo identities should be clearly fictional. A made-up company such as Halcyra, with invented staff and plausible but obviously sample figures, avoids any suggestion that a real customer is on screen.

Why is every word on screen a claim?

Because a viewer reads a product film as proof of what the software does. A button, a label, a chart value or a notification is a statement about the product. If the film shows a feature that is not live, a figure that is not typical or a step a person does as if the software did it, it misleads.

Australian law applies. According to the ACCC, statements that are inaccurate or likely to create a false impression are not allowed, and "it makes no difference whether a business intends to mislead or not". A film is a series of statements, made in pictures.

Three rules keep films honest. First, show only features that are live and approved to talk about. Second, never invent an interface state the product cannot produce. Third, when a step is done by the business's people, do not show it as automatic. The guide to approved claims covers keeping a list of what can be said.

Who approves a product film?

A person at the business approves every word, figure and screen, confirming the interface shown is the product as it ships. Then a person publishes it to the website, video host or social channels. The builder can script, build, export and share a private review copy, but cannot approve or publish.

Each version needs its own approval. A 30-second homepage cut and a 90-second sales cut say different things, so approving one does not approve the other. The guide to approval gates explains why approval is a recorded act, not a feeling of being finished.

Skein builds product films from a client's interface kit with demo data only, and the client approves and publishes every cut; the AI engineering page shows how. That suits a software company whose product is easier to show than to describe. A business without a visual product may get more from a written guide.

Frequently asked questions

What is a coded product video?

A coded product video recreates software screens as a web page, animates them and exports a video. Nothing is recorded from the live product. Because the source is code, the film can be updated, translated or re-cut quickly, and no real customer data ever appears on screen.

How do you make a product demo video without showing customer data?

Rebuild the screens instead of recording them. Measure the interface from screenshots, recreate it as reusable components, fill it with clearly fictional demo companies and people, and animate it. Since the real data was never there, there is nothing to blur or leak.

Can AI make product demo videos?

AI can help script the film, build the screens from a component kit, animate them and export the video. People must check that every feature shown is live, every word and figure is accurate, and then approve and publish the film. The film should never show invented capabilities.

Are product videos legally claims?

In practice, yes. Viewers treat what they see on screen as evidence of what the product does. Under Australian Consumer Law, showing a feature that does not exist or an unrealistic result can mislead, whether or not that was intended. Check every screen against approved facts.

How long should a product demo video be?

Short. Thirty to ninety seconds suits a homepage or social post, showing one clear outcome. Longer walkthroughs suit sales follow-up or help pages. Build separate cuts for each use rather than one long film, and have each cut approved separately before publishing.

Related reading