The release notes say two things: the "Start" button is now "Begin session", and the result card has been redesigned. Both are on the screen the product demo is built around. From the moment the update ships, the demo shows an app nobody will find when they install.
Every app team knows that kind of release, and it comes more often now. ActiveCampaign's Joann Ng described finishing the perfect demo just in time for a new AI capability to make it obsolete (Navattic). And redoing a demo isn't cheap. A well-made product video costs $1,000 to $3,000 per finished minute and takes weeks, and when the product changes you pay again to revise it (Navattic).
Every kind of demo has a cost on update
A screen recording has to be done again for every change. Screenshots and GIFs have to be captured, edited and placed again. Interactive demos solve the problem for the website: a captured product page can be edited instead of reshot, and Navattic's editor pushes a small UI change to every demo that uses a capture (Navattic). But an interactive demo lives on a landing page. It can't run in a Reels placement, a YouTube pre-roll or an ad network's video slot, so the ads still need video, and the video still goes stale.
Animating the design file
The obvious next step is to animate the design file, since that's where the UI changes first, and Figma is moving that way. At Config in June 2026 it added native animation, 3D transforms and code layers backed by React to its canvas (The Next Web). A team that built a launch video with Figma Motion in beta found hard limits: audio and video couldn't be imported, so screen recordings couldn't sit next to the UI, some effects couldn't be keyframed, and playback dropped frames in a long build (AutoAE). It animates a screen well and leaves the music, the footage and the ad around it to another tool.
Code-based motion tools get further on the edit. Hera generates code that renders as animation, so every element is an editable object, but it's built for motion graphics rather than ads made of a product's real screens with footage and sound (Motn vs Hera).
Building the demo from the design file
The demo stays current only if it's built from the same thing the release changes. In Motn the screens come from where the designers keep them: Figma frames come in as nodes on the canvas, so the demo starts from the frames the app was built from, not from a redrawn mock-up. Claude animates them as code, with the tap, the transition, the scroll and the result appearing, and the text inside the UI stays live text. The product marketer decides which flow the demo shows and in what order, because they know which moment sells the app.
Around the screens goes everything an ad needs: the headline, the captions and the end card as live text, music generated or brought in, and product footage or a screen recording on the same timeline. Each placement gets its own layout, with the phone frame and captions arranged for 9:16, 4:5 or 16:9 rather than scaled down. Each language takes its UI text and captions from the localized frames. The same demo can also be exported as HTML, React or Framer for the website's hero, so the site and the ads show the same product.
Now the release. "Start" becoming "Begin session" is an edit to one piece of live text. The redesigned result card is the updated Figma frame brought in again in place of the old one, with the animation, the timing and the captions kept. Every size and language picks up both changes, and the team checks the result instead of recording the demo again.
When to still use a screen recording
A demo built from frames shows the app as designed, and sometimes the ad needs the app as it runs. If the point is speed, a search that returns in half a second, record it, because an animation of speed proves nothing. If the screen depends on live data or a camera, a map, a scan or a photo filter, record it. And App Store preview videos must be screen captures of the app itself, so a store preview starts from recordings. Recordings and frame-built screens can sit on the same canvas, so one ad can use both.
Start with the demo your team most dreads updating, usually the one built around the main feature. Bring in its Figma frames and rebuild it, and the next time that screen changes, update it and count the hours. If your best ads are still static images, turning them into motion is the next step. More for subscription and utility apps is in Motn for apps.



