AI Video Tools Don’t Know What Your App Looks Like: Make a 30-Second Demo From Your Real UI
You shipped on Friday. The launch post is drafted, the Product Hunt page is half done, and the one thing missing is a video. So you tried an AI video tool, typed in a description of your app, and got back someone smiling at a laptop in a sunlit kitchen, with a screen showing a dashboard you’ve never built.
That isn’t the tool being bad at its job. It just has never seen your product. This page is about the video that actually sells software: 30 seconds of your real interface, doing one real thing, slowly enough that a stranger can follow it.
Why generic AI video says nothing about your product
A founder building a healthtech app described exactly this on Reddit: “Every AI video tool gave me generic junk because they have no idea what my actual app looks like” (r/SaaS). They ended up building an interactive demo with Claude Code instead: their real components running on fake data, with a narrated tour on top.
The reason is simple. A video model makes pixels that match a prompt. Your product’s value lives in specific screens: the moment the report fills in, the empty inbox, the one button that replaces twenty minutes of copy-paste. If the model invents those screens, the video is about a different product. And if someone signs up because of a screen that doesn’t exist, the first thing they find out is that the video lied.
Two other things from that thread are worth keeping:
- One commenter split demos by what the viewer wants at that point. A short video is for the first 20 seconds of attention: what problem does this solve? An interactive sandbox is for later, when they’re asking whether it works for their case. The 30-second video only has to do the first job.
- Another commenter tried the founder’s interactive demo and “bounced after a few seconds”, asking for a progress bar and a way to skip the narration. People give a demo very little patience. Plan for that.
The structure of a 30-second demo that works
1. The first 3 seconds: the result or the pain, never the logo
Most launch videos open on a logo animation, then a tagline, then the UI. By the time the UI shows up, the scroll is over.
Open on one of two things instead:
- The result. The finished thing your app produces, full screen. The generated invoice, the clean diff, the chart that used to take an afternoon.
- The pain. The mess before your app: 14 browser tabs, a spreadsheet with 2,000 rows, the “per-seat pricing” email. Real, recognisable, a little embarrassing.
Put one short line of text on top that says what’s happening: “Every Friday I copied 40 invoices by hand.” or “This took me 3 hours. Now it’s one click.” The text should still make sense with the sound off.
2. Only one task
Your app does twelve things. The demo shows one, start to finish: the task that’s the reason someone would pay. If you can’t pick one, that’s a positioning problem, and 15 minutes on positioning will help the demo more than any editing.
One task means one path through the UI. No “and it also does…” montage at the end. Make a separate 30-second video for the second-best task, and test them against each other later.
3. Hold every screen long enough to read
Here’s the trap that well-funded teams fall into too. A YC-backed team posted their launch video for an AI email app on Reddit and asked for feedback. The top comment: “Really good, but almost too fast to read.” Another viewer said that by the end they remembered the product name and “email”, “but nothing in between. My eyes were all over the place… mostly hunting the text, which was of different colors, sizes, fonts, and backgrounds.” Several others said the same thing. It was edited by hand from raw footage, and the people commenting liked the production. They just couldn’t follow it (r/SaaS).
You know your UI, so every cut feels slow to you. A stranger is seeing it for the first time, on a phone, half paying attention. A rough check that works: read each caption out loud at a calm pace while the clip plays. If the shot changes before you finish, hold it longer. And when you’re showing a click, zoom in on where the click lands and keep the cursor moving slowly enough to follow.
4. Captions on the screen, one style, one place
On X and LinkedIn, video starts playing muted in the feed. If the story only works with your voiceover, most people get a silent screen recording.
- Write the captions into the video itself, not just as a subtitle file.
- Use one font, one size, one colour, one position, for the whole video. Mixing them is exactly what the email-app viewer described: eyes hunting around the frame.
- Keep each caption to one short line. If it doesn’t fit, it’s two captions.
- Never put a caption over the part of the UI you’re showing.
5. End on one sentence that tells them what to do
“Try it free at yourapp.com.” “Paste a repo URL and see your first report.” One action, one URL, on screen for at least two seconds. Not three options, not your social handles.
A shot list you can copy
Here’s an example for a made-up app that chases late invoices for freelancers. Swap in your own.
| Time | On screen | Caption |
|---|---|---|
| 0–3s | Inbox full of “just following up” emails the user wrote by hand | “I spent Fridays chasing unpaid invoices.” |
| 3–8s | The app’s invoice list, three marked overdue | “Now the app finds the late ones.” |
| 8–15s | Zoom on one overdue invoice, click “Send reminder” | “One click sends a polite reminder.” |
| 15–22s | The reminder email as the client sees it | “It’s written in your tone, not a template’s.” |
| 22–27s | The invoice flips to “Paid” | “Paid in 2 days instead of 3 weeks.” (only if that’s true for you) |
| 27–30s | URL on screen | “Try it free: latepay.app” |
Six shots in 30 seconds, and each one gets about five seconds. That’s what “slow enough to follow” looks like in practice.
Making it from your real interface
You don’t need a studio. You need your real product, set up so it looks good on a small screen.
Before recording:
- Seed realistic demo data. No lorem ipsum, no “test test”, no real customer data. Use names, amounts and dates that look like your actual users’.
- Clean the screen. Hide the bookmarks bar, turn off notifications, close Slack. Use a fresh browser profile for recording.
- Make the text bigger. Browser zoom at 125–150% or a smaller window, so the UI text is still readable when the video is shrunk to a phone feed.
- Write the script first, even as five bullet points. One founder on Reddit who lost an afternoon to a “20-minute” demo got replies saying the biggest time-saver was a tight script beforehand, and recording in short chunks instead of one long take, so a mistake only means redoing ten seconds (r/SaaS).
Three ways to put it together:
- Screen recording plus a recorder with auto-zoom. The same thread lists Screen Studio, Tella, Recordly and others. They zoom in on clicks for you, which takes care of most of the “can’t see what’s happening” problem.
- Screenshots plus code. A developer on r/indiehackers made App Store preview videos with Remotion and an AI assistant writing the React components (r/indiehackers). A commenter pointed out the part that matters later: when the UI changes, “you just swap the screenshot and re-render.” If your onboarding changes every two weeks, that’s a real advantage.
- Screenshots plus a tool that animates them, which is what the last section of this page is about.
Whatever you use, the rule is the same: every pixel of the UI in the video should be something a new user will actually see after signing up.
Length and format, platform by platform
The 30-second cut is your base. Here’s how to adjust it for where it’s going. These are working rules from practice, not platform data.
| Platform | Who’s watching | What to change |
|---|---|---|
| X | Mostly other builders and early adopters | Muted autoplay, so captions are mandatory. 20–45 seconds. Landscape or square is fine. Pin it to your profile on launch day. |
| Buyers, if you sell B2B | Also muted. Square or vertical takes up more of the feed. Post it from your personal profile with two or three plain sentences about the problem. | |
| YouTube Shorts | People searching for a way to do something | Vertical 9:16. The title and the first line work like a search result: name the task (“How to chase late invoices automatically”), not your brand. |
| TikTok | People who’ll never search for your category | Vertical, sound on, and it has to feel native. A how-to format beats a polished ad here. |
On TikTok, one person who has run a lot of experiments promoting a SaaS wrote that tutorial-style videos get fewer views but, in their experience, “10x more conversions” than entertaining ones. Their examples: a screen recording, or recording your screen with your finger showing where to tap (r/SaaS). That’s their experience, not a benchmark, but it matches the structure above: one task, shown clearly.
On your own landing page, a longer walkthrough (60–90 seconds) is fine, because the people there have already chosen to look. The 30-second version is for the feed, where nobody has.
What to do next
This week: pick the one task people would pay for, write six lines of captions using the table above, record your real UI in short chunks, and cut it to 30 seconds. Before you post, show it to someone who’s never seen your app, with the sound off, and ask them what it does. If they can’t say, slow it down.
If you’d rather not spend the afternoon in an editor, AutoWhisper can make the first version. Give it your website URL and it captures your real pages and builds a product demo from them, with the text on your screens kept exactly as it is. If the part that matters is behind a login, upload screenshots of your interface instead. It can also make an animated explainer for the same product, which costs less than a full video. A full video is 52 credits, and new accounts start with 65 free. Create an account and paste your homepage in first.
If you live in Claude Code or Cursor, you can do all of this from there: tell your assistant “Connect me to AutoWhisper — follow the instructions at https://autowhisper.xyz/skill”, then click approve. More on that in Which Path Are You On. And once the video exists, the next problem is getting anyone to see it: that’s Built It, Nobody Came.