How to Make an App Demo Video on Mac: App Store, Product Hunt, and Social

Before you open any recording software, write down your app's value prop in three steps. Not three features — three steps of a user journey. The format is: 'User starts at X → user does Y → user gets Z.' For a habit tracker: 'User opens a blank week → taps to log today's run → sees a 14-day streak.' For a note-taking app: 'User opens to blank page → types a messy thought dump → taps structure → sees organized outline.'

This three-step structure is your entire demo video. Everything else is detail. The demo that shows these three steps clearly, in under 60 seconds, with the payoff (step three) landing in the first third of the video, will outperform a comprehensive feature tour every time.

Draw or write the storyboard on paper or in a notes app. Three boxes: starting state, action, result. For each box, note exactly what is on screen and what the user does. This becomes your shot list.

The state of your app at recording time is the state in your demo video. Set it up completely before you open Limelight. Log in. Populate it with realistic data — names, amounts, dates that look like a real user's data, not 'Test User' and '$0.00.' Navigate to the exact starting screen from your storyboard.

Close every other app. Turn on Do Not Disturb (Control Center → Focus → Do Not Disturb). If you are recording a mobile app in a simulator, hide the simulator chrome if possible — the big gray simulator bezel distracts from the app. On a Mac app, resize the window to fill a clean portion of the screen at a size where the UI is legible without being cramped.

If your demo involves a user-initiated action with a loading state (submit a form, fetch data, generate something with AI), run through it once before recording to see how long it takes. If it takes more than three seconds, you will want to speed it up in editing. If it takes more than ten seconds, consider whether it can be cached or pre-run for the demo.

Most demo videos record chronologically — they show the user opening the app, logging in, finding the feature, and eventually showing the result. This buries the payoff. The viewer leaves before the good part.

Record your demo in storyboard order, but structure the storyboard so the aha moment — the result, the generated output, the satisfying UI response — appears within the first ten seconds of screen time. The 'before' context can be one second (a blank state or an unsatisfying state), the core action can take two to three seconds, and the result should land by second ten.

If your aha moment requires twenty seconds of setup to reach, consider whether the demo can start at step two of the user journey instead of step one. Viewers do not need to watch the login screen. Start them at the moment the app gets interesting.

Open Limelight and start recording from your prepared app state. Click through your storyboard flow deliberately. Auto-zoom follows every click and holds briefly on each element — the button you clicked, the field you typed into, the result that appeared. Pause a beat after each click before moving to the next action. This gives auto-zoom time to land and gives the viewer time to register what happened.

Type any inputs your demo requires at a natural but deliberate pace — slightly slower than you would type for yourself. Limelight's keystroke display shows each key, which is useful for shortcut-heavy apps or for making form inputs readable without audio. Use on-screen text to label your demo sections if the flow needs context ('Before' and 'After' labels work well for transformation-based apps).

Use the freehand annotation or region spotlight tools to circle or highlight the result if it appears in a part of the screen that might not be immediately obvious. A region spotlight drawn around the key outcome — the generated output, the saved record, the satisfying metric — helps the viewer know exactly where to look.

Record one complete take of your storyboard flow. If you make a mistake mid-recording, keep going and cut it in the editor rather than starting over — a continuous take is often easier to edit than multiple short clips.

In the Limelight editor, trim the opening to the first frame of real action — no dead air before your first click. Trim the end to the last beat of the result appearing, plus one second of hold so the viewer can read the outcome.

Speed up any loading or processing states. If your app takes five seconds to generate or load something, compress it to one second. The viewer understands something is happening — they just do not need to watch it in real time. Most demo videos that run over 60 seconds are fixable by speeding up loading states.

Watch the full clip once before exporting. Check that every auto-zoom landed on the right element, that on-screen text labels appear at the right moments, and that the pacing feels deliberate without feeling slow. The goal is a clip where the viewer can read every UI element without pausing.

Limelight exports to both aspect ratios from the same recording session. Export at 16:9 for: your landing page hero video, the Product Hunt gallery video slot, the App Store preview video (which uses 16:9 for iPad and desktop), YouTube, and any embedded docs or blog posts.

Export at 9:16 for: Twitter and X video posts (plays full-screen on mobile), Instagram Reels and Stories, TikTok, LinkedIn mobile video. Native vertical video gets dramatically more reach on every platform than landscape video or link posts. Schedule the 9:16 exports for social on launch day.

For the App Store specifically: Apple accepts 15-30 second preview videos at H.264 or HEVC. Export your 30-second cut as mp4 from Limelight and use it directly, or convert to HEVC with Handbrake if file size is a concern.

App Store: upload the 16:9 mp4 as an app preview in App Store Connect. Place it as the first media asset — it autoplays in search results before the screenshots. Keep it under 30 seconds.

Product Hunt: upload the 16:9 mp4 to the gallery when you set up your listing. It plays at the top of your product page. The first three seconds show in the thumbnail preview, so make sure frame one shows something visually interesting — not a blank screen.

Landing page: embed the mp4 directly as an HTML video element with autoplay and muted attributes. An autoplaying silent demo on a landing page hero converts better than a static screenshot for most software products.

Social: schedule the 9:16 exports as native video posts on Twitter, Instagram Reels, and LinkedIn for launch day. Post them natively — do not link to YouTube or Loom — native video has far better algorithmic reach on every platform.