How to Prototype an App Launch Video Without Reely (Free & Low‑Cost Workflow, 2026 iOS App Preview Video Generator Guide)

By the end of this tutorial, you’ll have a scrappy but real app launch video prototype: a short iOS app preview‑style reel you can test on the App Store…

Geometric fire escape staircase on a blank wall representing step-by-step app launch video workflow.

By the end of this tutorial, you’ll have a scrappy but real app launch video prototype: a short iOS app preview‑style reel you can test on the App Store, Product Hunt, or social before investing in a dedicated app launch video generator like Reely.

This guide shows you how to build that MVP with:

  • An AI chat assistant (for script and storyboard)
  • Free Reallusion character assets (for human context shots)
  • Free editors like CapCut and DaVinci Resolve (for assembly)

Along the way, you’ll validate messaging, look for product‑of‑excellence signals, and learn exactly when it makes sense to graduate to Reely.

The workflow deliberately imitates an iOS app preview video generator using common tools, so you can prototype your process before adopting a specialized app store app preview video generator.

Prerequisites

Before step 1, make sure you have:

Hardware & OS

  • A Mac capable of running Xcode and DaVinci Resolve Free
  • Optional: Secondary monitor (helps when recording simulator + editor)

Software (all free or low‑cost)

  • Xcode with iOS Simulator (for app footage)
  • OBS Studio (free screen recorder)
  • DaVinci Resolve Free or CapCut Desktop
  • Reallusion Character Creator (free base characters)
  • Any AI chat tool (e.g., ChatGPT, Claude, Gemini)

Account / access

  • Access to your app’s latest build (simulator or device)
  • Optional App Store Connect account (if you plan to upload a preview)

Naming convention for files (we’ll reuse this)

  • beat01_hook.mov – first visual beat, hook
  • beat02_featureA.mov – main feature demo
  • beat03_socialproof.png – stills for testimonials

Common failure at this stage: trying to improvise everything. Decide on tools and naming upfront; it saves hours later.

Step 1: Define the promise and beats with AI chat

This step creates the narrative foundation: a single clear promise and 3–5 beats that match Apple’s App Store preview guidance.

1.1 Ask AI for a single‑sentence promise

Copy‑ready prompt:

"You are a launch copywriter for an iOS app. Write one clear promise sentence for a 25–30 second app preview video. Focus on the main outcome for users, not features. Keep it under 18 words."

Good AI response example:

  • "Turn your scattered tasks into a focused daily plan in under 60 seconds."

Bad AI response example:

  • "Our innovative app leverages cutting‑edge technology to streamline productivity for users across multiple platforms and devices." (Too vague, buzzword‑heavy, not visual.)

If the response is generic, ask:

"Make this more concrete and visual. Mention the moment the user first feels the benefit."

1.2 Generate 3–5 storyboard beats

Apple recommends up to 30s, visually compelling first few seconds, and a cohesive story.

Copy‑ready prompt:

"Based on this promise: [paste promise], outline 5 numbered storyboard beats for a 25–30 second iOS app preview video. Each beat must describe: 1) what’s on screen (simulator or UI), 2) the user action, 3) the on‑screen caption (under 8 words)."

Good AI beat example:

  1. On screen: iOS simulator home screen. User taps your app icon. Caption: "Open. Focus. Start today."

Bad AI beat example:

  • "Show how the app is easy to use." (No concrete visuals or actions.)

Common failure: allowing beats that can’t be visualized as simulator footage. Reject any beat you can’t literally screen‑record.

1.3 Create caption and VO variants

You’ll need short copy that works muted and (optionally) with voiceover.

Copy‑ready prompts:

Captions:

"Write 8 short caption options for this app preview, all under 6 words, punchy, and benefit‑led."

VO script:

"Write a 60–70 word voiceover script for this 25–30 second app preview. The first sentence must hook attention in under 4 seconds when played over muted autoplay."

Reject AI outputs that:

  • Use generic claims (“revolutionize”, “seamless experience”) without specifics
  • Don’t match what users actually do in your app

Step 2: Capture clean iOS Simulator footage with OBS

This step creates your core product footage using free tools and reproducible settings.

2.1 Install and open OBS Studio

  1. Download OBS Studio from the official site and install it.
  2. Launch OBS.
  3. In the main window, find the Scenes box (bottom left).

Common failure: recording the entire desktop instead of just the simulator window. We’ll fix that next.

2.2 Create a dedicated "iOS Simulator" scene

  1. In Scenes, click + and select Add Scene.
  2. Name it iOS_Simulator_1080x1920.
  3. Click OK.

2.3 Add a window capture source

  1. In Sources, click +.
  2. Choose Window Capture.
  3. Name it Simulator_Window.
  4. In the Window dropdown, select iOS Simulator.
  5. Click OK.
  6. Resize and position the window in the preview so the device is centered.

If the simulator doesn’t appear:

  • Make sure it’s open and not minimized.
  • Switch its device type to an iPhone model with a vertical layout.

2.4 Configure OBS recording settings (resolution, FPS, format)

  1. Go to Settings → Video.
  2. Set Base (Canvas) Resolution to 1080x1920 (vertical 1080p).
  3. Set Output (Scaled) Resolution to 1080x1920.
  4. Set Common FPS Values to 60 (smooth device motion).
  5. Go to Settings → Output → Recording.
  6. Set Recording Format to mp4 or mkv (mp4 is easiest for editors).
  7. Set Encoder to:
    • x264 for software encoding or
    • Hardware encoder (e.g., Apple VT H.264) if available.
  8. Set Recording Quality to High Quality, Medium File Size.
  9. Click OK.

Recommended codec target: H.264 60fps in an .mp4 container.

Common failure: mismatched aspect ratio (horizontal 1920x1080 instead of vertical). Always check the Video resolution before recording.

2.5 Record per‑beat clips with a clear naming convention

For each storyboard beat:

  1. Prepare the simulator in the exact state needed (e.g., app on home screen).
  2. In OBS, confirm you’re on the iOS_Simulator_1080x1920 scene.
  3. Click Start Recording.
  4. Perform the user actions slowly and clearly.
  5. Wait 1 extra second after the final action.
  6. Click Stop Recording.
  7. Locate the file (default OBS recordings folder).
  8. Rename the file to match the beat, e.g., beat01_hook.mp4.

Aim for 5–8 seconds per beat. Shorter clips make editing easier.

Step 3: Create human context shots with Reallusion’s free Character Creator

This step adds "user in context" moments using free 3D character bases.

3.1 Install and open Character Creator

  1. Download Character Creator (free version) from Reallusion.
  2. Install and launch the app.
  3. When prompted, choose a free base character from the library.

Reallusion’s free bases include 150+ facial morphs and are licensed for commercial use.

3.2 Pose and frame a "phone user" still

  1. In the Content panel, select a basic outfit for the character.
  2. Apply a preset pose that looks like someone holding a phone or device.
  3. Adjust the camera so the character is framed from the waist up, looking at the device.

Common failure: overly complex scenes. Keep background minimal so the character can sit behind your app UI or captions.

3.3 Export a high‑res still image

  1. Open Render → Render Settings.
  2. Set Image Size to 1080x1920 (vertical).
  3. Set Output Format to PNG.
  4. Set DPI to 300 if available (helps with crisp text overlays).
  5. Choose an output folder.
  6. Click Render.
  7. Save as beat00_context_user.png.

This image can be used as the opening frame or closing "user reaction" shot.

3.4 Render a short looping reaction clip (2–3s)

  1. In Character Creator, move the timeline playhead to frame 0.
  2. Apply a simple facial animation (e.g., slight smile, nod).
  3. Set the timeline end to 2 seconds.
  4. Go to Render → Render Video.
  5. Set Frame Rate to 30 fps.
  6. Set Resolution to 1080x1920.
  7. Set Output Format to MP4.
  8. Click Render.
  9. Save as beat05_reaction_loop.mp4.

Common failure: rendering at 16:9 horizontal. Always double‑check resolution is vertical before exporting.

Step 4: Assemble the MVP in DaVinci Resolve Free (or CapCut)

This is where you turn raw clips into a coherent app launch video.

4.1 Create a new vertical project (DaVinci Resolve)

  1. Open DaVinci Resolve.
  2. On the start screen, click New Project.
  3. Name it App_Preview_MVP.
  4. Click Create.
  5. Go to File → Project Settings.
  6. Under Master Settings:
    • Set Timeline Resolution to 1080x1920.
    • Set Timeline Frame Rate to 60.
  7. Click Save.

Common failure: leaving default 1920x1080 horizontal. If your timeline is wrong, re‑set it before importing media.

4.2 Import and place clips on the timeline

  1. Go to the Media Pool.
  2. Right‑click → Import Media.
  3. Select all beatXX_*.mp4 and beat00_context_user.png files.
  4. Click Open.
  5. Drag beat00_context_user.png to the timeline as the first clip.
  6. Set its duration to ~2 seconds.
  7. Drag beat01_hook.mp4 next, followed by beat02_featureA.mp4, etc.
  8. Add beat05_reaction_loop.mp4 as the final clip.

4.3 Trim dead air and match Apple’s 30s guidance

Apple allows up to 30 seconds and recommends strong first seconds.

  1. Use the Blade tool to cut pauses where nothing happens.
  2. Delete dead segments and ripple close gaps.
  3. Check total duration (bottom right of timeline). Aim for 00:00:20–00:00:28.

Common failure: leaving long idle moments between taps. Keep every second purposeful.

4.4 Add captions and simple motion

  1. In the Edit page, open the Effects Library.
  2. Under Titles, drag a Text item above each clip.
  3. Type the caption you chose earlier (under 6 words).
  4. Align the caption timing with the key app interaction.

Example placements:

  • On opening context still: "Meet your new focus ritual."
  • On first app tap: "Open. Focus. Start today."

If you’re in CapCut instead:

  1. Create a new project.
  2. Set canvas to 9:16.
  3. Import clips via + Add Media.
  4. Drag them to the timeline.
  5. Use Text → Default for captions.

4.5 Export for App Store and social

DaVinci Resolve export:

  1. Go to the Deliver page.
  2. Choose Custom Export.
  3. Set Format to MP4.
  4. Set Codec to H.264.
  5. Set Resolution to 1080x1920.
  6. Set Frame Rate to 60.
  7. Set Quality to Automatic, Best.
  8. Choose output filename app-preview-mvp-1080x1920.mp4.
  9. Click Add to Render Queue → Render All.

CapCut export:

  1. Click Export.
  2. Choose Resolution 1080x1920.
  3. Set FPS 60.
  4. Choose MP4.
  5. Export as app-preview-mvp-1080x1920.mp4.

Common failure: exporting at 720p or low FPS. Stick to 1080x1920, 60fps, H.264 for crisp App Store previews and social shorts.

Step 5: Validate messaging and product‑of‑excellence signals

Now you treat the video as a measurable conversion asset, not just a pretty reel.

5.1 Check basic craft and clarity

Watch your MVP and ask:

  • Can someone understand the core promise muted in 5 seconds?
  • Does every beat show clear user action + outcome?
  • Is the UI legible at 1080x1920 on a phone screen?

Product‑of‑excellence signals:

  • Smooth, non‑jittery device motion (60fps helps)
  • No awkward dead air or frozen frames
  • Consistent typography style across captions

5.2 Test conversion impact where possible

AppTweak reports average U.S. conversion rates:

  • 8.56% on the App Store
  • 16.15% on Google Play

Use your prototype to test whether video moves the needle.

Options:

  • App Store Product Page Optimization: create variant pages with and without the preview video and compare uplift.
  • Simple A/B on landing page: show video to half of traffic, measure signups vs a static screenshot.
Chart showing high importance of video and strong ROI of short-form video in 2026 marketing stats.

Video remains a high-ROI format in 2026, with 93% of marketers calling it important and short-form clips performing best.

If your metrics move meaningfully above category baselines, that’s a strong signal your messaging works, even if the video is scrappy.

5.3 Iterate fast on AI‑assisted captions

Because short‑form video has the highest ROI (93% of marketers call video important), small copy tweaks can matter.

Ask AI:

"Give me 10 alternative caption sets for these 5 beats. Each set should feel like a different angle (speed, calm, power, simplicity), but all must be concrete and non‑generic."

Swap caption tracks in your editor and re‑test. Keep any variant that improves watch‑through rate or click‑through.

Common failure: rewriting the whole video instead of small, testable elements. Focus on captions and first 5 seconds first.

Step 6: Best AI app launch video tools 2026 — affordable options for indie developers

Once you’ve proven that video works, you might want more automation than this manual stack.

Here’s a snapshot of best AI app launch video tools 2026 and related affordable options:

  • Reely – AI‑native app launch video generator for mobile devs. Integrates with iOS Simulator and your coding agent; generates 10–20s feature teasers and 30–60s launch promos from code, screenshots, or prompts.
  • Screen Studio – Polished macOS recorder for product demos. Great for smooth Screen Studio iOS app demo recordings with auto zoom and animations, but manual editing is still required.
  • CapCut – Free editor with AI captioning, templates, and background removal. Strong for short social‑first launch clips.
  • DaVinci Resolve Free – Pro‑grade NLE with AI text‑based editing. Ideal if you want precise control but are comfortable with timelines.
  • Generic AI video generators (e.g., Runway, Pika) – Can create abstract motion and overlays, but less optimized for true app flows.
  • OBS Studio – Not a generator, but still the best free tool for simulator recordings.
  • Self‑hosted tools (e.g., ffmpeg scripts + custom overlays) – Highly flexible but require significant setup and design effort.

If you want a deeper comparison of alternatives designed for dev‑focused teams, see this companion piece: Reely AI alternatives for app launch videos: realistic options for dev‑focused teams.

Step 7: Reely vs Screen Studio (iOS app demo comparison)

When you’re ready to move beyond manual scrappiness, the choice often narrows to Reely iOS app demo workflows vs Screen Studio iOS app demo workflows.

Reely

  • Pros
    • Agent‑first: your coding agent can reconstruct app flows in the iOS Simulator and auto‑generate reels.
    • Automatic dead‑air removal and editorial pacing tuned for product demos.
    • Brand‑theme‑from‑app: pulls your app’s visual identity into typography and backgrounds.
    • Outputs both 10–20s feature teasers and 30–60s full launch promos.
    • Native macOS, local rendering — no cloud uploads of your builds.
  • Cons
    • Focused on mobile apps; not a general "film anything" tool.
    • Requires integrating with your agent/workflow to get full value.

Screen Studio

  • Pros
    • Simple macOS recorder for product demos and tutorials.
    • Automatic zoom and smooth animations around cursor/gestures.
    • Great for devs who want hands‑on control but dislike heavy NLEs.
  • Cons
    • No agent integration or "promo from code" capability.
    • Brand consistency and kinetic typography are manual.
    • Dead‑air removal and pacing still depend on you.

Use Screen Studio if you love recording manually and layering polish yourself. Choose Reely if you want your agent and simulator to handle most of the launch‑video production.

Step 8: Auto‑generate app demo reels after build / from code

This step explains when your scrappy prototype should graduate to an AI tool that can generate product demo videos from code.

8.1 Understand "promo from code" workflows

Tools like Reely aim to:

  • Read your app’s structure and flows via simulator + agent.
  • Rebuild key user journeys automatically.
  • Capture clean device footage without you driving the simulator.
  • Pipe that footage into a motion system that handles device choreography, typography, music, and pacing.

This is the promise behind phrases like:

  • AI tools generate product demo videos from code
  • AI tool generate product demo video from code
  • Tool auto generate app demo reels after build

8.2 Connect builds to generation tools in practice

Typical setup for an agent‑first tool:

  1. After CI builds your app, it exposes a fresh simulator build.
  2. Your coding agent gets a "demo flows" spec (e.g., login + core feature).
  3. The agent uses an MCP/tool to launch the simulator and perform those flows.
  4. The tool records each flow, auto‑cuts dead air, and assembles beats.
  5. You get editable scenes with synced captions and motion presets.

This is exactly where manual workflows break down as you ship faster: every new feature requires:

  • New OBS scene setup
  • New simulator recording
  • Manual trimming and captioning

If that effort starts to hurt your shipping velocity, it’s time to adopt an agent‑first generator.

Step 9: Privacy and local options — AI video creator offline / runs locally

If you care about keeping builds offline, you need tools that run locally.

9.1 Local‑first stack

  • OBS Studio – Local screen capture; no cloud.
  • DaVinci Resolve Free – Runs locally on your computer; exports stay on disk.
  • Reely – Native macOS app that renders locally and works with iOS Simulator. No cloud upload for your builds.

These satisfy the need for an AI video creator offline with local processing of code and an AI video generator that runs locally on your computer.

9.2 Trade‑offs

  • Cloud tools often have flashier templates and collaboration.
  • Local tools give you privacy, repeatability, and control.
  • For sensitive or unreleased apps, staying local is usually the safer choice.

When to graduate from this MVP workflow to Reely

Use this free/low‑cost prototype stack until:

  • You’re shipping features faster than you can record and edit.
  • You need consistent brand theming across dozens of reels.
  • You want your coding agent to own "build feature" → "build demo reel".

At that point, Reely’s "promo from code in minutes" promise aligns with your needs:

  • Same source of truth as your code
  • Local macOS rendering
  • Motion studio systems without timelines

Your agent built the app. Let it build the demo reel too.

FAQ / Troubleshooting

Q1: My OBS simulator recording looks blurry. What did I do wrong?

You likely recorded at a lower resolution or FPS. Check Settings → Video and confirm both Base and Output resolutions are 1080x1920, and FPS is 60. Also ensure your Recording Quality is not set to "Low Quality".

Q2: DaVinci Resolve keeps forcing a horizontal timeline. How do I fix it?

Before importing any media, go to File → Project Settings → Master Settings and set Timeline Resolution to 1080x1920. If clips are already imported, create a new project with correct settings and re‑import.

Q3: My captions cover important UI elements. Any quick fix?

Use top or bottom safe areas:

  • Move captions to the top or bottom third of the frame.
  • Reduce font size slightly.
  • Shorten text to 3–4 words so it fits one line.

Always preview on a phone to confirm readability.

Q4: How can I test App Store preview performance without a big ASO stack?

Start simple:

  • Use Apple’s Product Page Optimization to create one variant with video and one without.
  • Track install conversion rates over a few weeks.
  • If video lifts your conversion above the 8.56% App Store U.S. average for your category, double down.

Q5: Do I need voiceover for an App Store app preview video?

No. Apple previews autoplay muted, so visual clarity and captions matter more. You can add VO for other surfaces (YouTube Shorts, X, LinkedIn), but prioritize visuals and captions first.

Once you’ve proven that a simple MVP launch video moves real numbers, graduating to Reely or another dedicated app launch video generator stops being a luxury and starts being an obvious productivity upgrade.

Your code is the source. Let your tools turn it into motion.

← All posts