Rotato vs. Traditional Screen Recorders: Best Mac Capture Workflow for iOS UI Demos
Apple wants App Store preview footage captured off a real device — not the Simulator. Here's where Rotato, screen recorders and Simulator capture each actually belong.
If you're shipping iOS features fast, you have two main paths for UI demo videos on Mac:
- Rotato for 3D device-framed scenes and mockups
- Traditional screen recorders (QuickTime, Screen Studio, Kap, etc.) for direct capture of a device or the Simulator
Choosing the right stack is the difference between a clean App Store preview that passes review and a punchy Product Hunt trailer that actually gets watched.
This guide compares Rotato's device-framed demo style with standard Mac screen recorders so you can design the best capture workflow for App Store previews, Product Hunt launches, and social teasers.
What you're actually optimizing for
Before tools, clarify the job of your video:
- App Store previews (compliance + clarity)
- Product Hunt / launch trailers (narrative + hype)
- TikTok / Instagram / X teasers (scroll-stopping visuals)
- Internal/shareable demos (speed over polish)
Each use case has different constraints and plays to different strengths of Rotato vs. screen recorders.
Quick primer: Apple's rules for iOS App Store previews
Apple is opinionated about app preview videos. If your output is going into App Store Connect, you need to play by these rules.
From Apple's published preview specifications:
- Duration: 15–30 seconds per preview
- Count: Up to 3 previews per language
- Format: H.264 or ProRes 422 (HQ only)
- Frame rate: Max 30 fps
- File size: Up to 500 MB per video
- Content: Only in-app content; no people holding devices
- Resolution: Each preview must be delivered at Apple's exact listed resolution for that device family — 886 × 1920 for a 6.9" iPhone, 1200 × 1600 for a 13" iPad, 1920 × 1080 for Mac and Apple TV
- Audio: Plays muted by default, so readable on-screen text is critical
Apple also recommends:
- Keeping a tight narrative
- Showing different features across each preview
- Avoiding seasonal or time-sensitive references
The rule most posts get wrong: previews are device-captured
This is the one that trips people up, so it's worth stating flatly. Apple's App Previews page says the footage comes off a real device:
Capture app footage from the device using QuickTime Player on macOS simply by connecting your device to a Mac.
App Store Connect's own prerequisites for creating a preview list hardware — an iPhone with a 6.5" display, an iPad with a 13" display, an Apple TV, or an Apple Vision Pro. The iOS Simulator is not on that list.
Note the asymmetry, because it's the source of most of the confusion:
- Screenshots can come from the Simulator. This is a normal, documented workflow, and it's how most teams generate every device size without owning every device.
- Preview videos are supposed to be device-captured. Simulator footage may sail through, but it's off-spec, and "it worked for my friend" is not a review policy.
So App Store previews want a plain, unstyled recording — which rules out heavy 3D framing — and they want it captured on hardware. Those are two separate constraints, and Rotato conflicts with the first while Simulator-based tools conflict with the second.
Option 1: Rotato for device-framed UI demos
Rotato is essentially a 3D device compositor with recording and mirroring built in.
What Rotato is good at
Rotato shines when your goal is to make the app feel designed and premium:
- Device-framed mockups
- 30+ devices and 80+ ready-to-render templates
- Preset scenes tuned for App Store graphics, YouTube, Instagram, X, and Product Hunt
- 3D motion and camera moves
- 12+ animation presets (spins, tilts, pans)
- Great for "floaty" phone-in-space visuals
- High-end export formats
- Up to 4K, 60 fps
- ProRes 4444 with alpha channels for compositing
- Aligns well with design tools
- Ideal if you're already moving between Figma, Sketch, or static mockups and want video output
Rotato is strongest when you want your app demo to look like a motion design piece, not just a raw screen capture.
Where Rotato struggles for App Store previews
Some of Rotato's strengths are actually liabilities when you're targeting App Store previews:
- Apple's rules say: show only app content, avoid people, keep framing native
- Heavy device framing, dramatic camera moves, and zoomed crops go beyond Apple's "safe"/recommended style
- Overly stylized framing may increase the risk of rejection or re-work
Conclusion: Rotato is excellent for launch trailers and social promos, but less suited as the primary capture pipeline for App Store previews.
Option 2: Traditional Mac screen recorders
On the other side, you have tools that record exactly what happens on screen. They cover two jobs that are easy to conflate:
- Recording a connected iPhone through QuickTime Player — the compliant path for an App Store preview
- Recording the iOS Simulator — faster, endlessly repeatable, every device size on demand, and the right source for everything that isn't an App Store preview
Common tools in this bucket
- QuickTime Player (built-in, free)
- Screen Studio (polished recorder + light editor)
- Kap (open-source screen recorder)
- Generic tools like CleanShot X, OBS, etc.
QuickTime + a connected iPhone: the compliance baseline
For the App Store preview itself, the baseline hasn't really changed in years:
- Connect the iPhone to your Mac
- QuickTime Player → File → New Movie Recording → pick the iPhone as the camera source
- Record the flow, trim to 15–30 seconds, scale to Apple's exact preview resolution
It's unglamorous, and rehearsing a flow on hardware is slower than driving it in a Simulator. But it's the footage Apple asks for, it carries a real device's status bar and frame rate, and it removes an entire category of "why was my metadata rejected" guesswork.
Where the Simulator genuinely wins
Xcode's Device Hub makes simulated devices easy to capture from, and that matters — just not for the ASC preview:
- Screenshots for every device family, at the full resolution of the simulated device, without owning the hardware
- Iteration: rehearse and re-record a flow as many times as you like, with seeded data and no notifications, battery, or carrier text to clean up
- Every non-App-Store video: Product Hunt, landing pages, X/TikTok, docs, changelogs, investor updates
Treat Simulator footage as your working material and your marketing footage, and treat the device pass as the last mile for App Store Connect.
Screen Studio: the "smart" recorder
Screen Studio deserves a special callout because it adds editing-like polish while staying screen-first:
- Auto zoom on important interactions
- Smooth cursor movement and timing
- Vertical export for social platforms
- Background and spacing controls
Its positioning: make raw captures feel edited without forcing you into a timeline.
Screen Studio uses a subscription model (monthly or yearly), and offers a 40% educational discount for students.
Kap: the lightweight OSS option
Kap is an open-source screen recorder favored by many indie devs:
- Free, simple, minimal UI
- Good for quick captures of iOS simulator or Mac apps
- Plugins for export formats and integrations
The downside: almost no built-in "polish" — you'll still need a separate editor or motion tool for text, pacing, and sound.
Rotato vs. screen recorders: side-by-side comparison
Here's a high-level comparison for iOS UI demo workflows.
- Primary role — Rotato: 3D device mockups and motion design. Screen recorders: direct simulator / screen capture.
- Best for — Rotato: app promo visuals, social teasers, landing pages. Screen recorders: App Store previews, tutorials, raw demos.
- App Store compliance — Rotato: device shells and camera moves go past what Apple asks for in a preview. Screen recorders: compliant when you record a connected device; Simulator footage is off-spec for previews even though the recorder itself is fine.
- Capture source — Rotato: mirrored device or pre-recorded footage dropped into mockups. Screen recorders: a connected iPhone via QuickTime, or the live iOS Simulator.
- Editing and pacing — Rotato: template-driven, but focused on visuals. Screen recorders: depends on the tool; Screen Studio adds auto zoom and smoothing.
- Export formats — Rotato: up to 4K, 60 fps, ProRes 4444. Screen recorders: varies; usually H.264, App Store-friendly specs after post-processing.
- Learning curve — Rotato: medium (3D scenes, cameras, templates). Screen recorders: low — hit record, trim, export.
- Pricing — Rotato: one-time Mac license. Screen recorders: a mix of free (QuickTime, Kap) and subscription (Screen Studio).
Which workflow is best for different demo types?
You usually need a stack, not a single tool. Here's a practical breakdown.
1. App Store preview videos
Goal: Pass review, boost conversion, minimize rework.
Given Apple's specs and guidance:
- Capture from a physical iPhone connected to your Mac, via QuickTime Player
- Keep framing full-screen native UI (no 3D device shells)
- Match the 15–30 second length requirement
- Export as H.264 or ProRes 422 (HQ) at max 30 fps, scaled to Apple's exact preview resolution
A practical shortcut: design the reel in the Simulator, where you can re-run the flow until the pacing is right, then shoot the same flow once on hardware as your final take. You're rehearsing cheaply and delivering compliantly.
Remember: video previews can materially impact conversion.
SplitMetrics analyzed 3,500+ A/B tests and found that optimized video creatives can significantly lift performance; in a Prequel case study, video experimentation drove a 75% improvement after testing multiple variants.
Rotato can still help here for static App Store images or marketing clips, but the preview core should be a clean, unstyled recording of the device.
2. Product Hunt launch video
Goal: Tell a tight story and stand out in the feed.
Recommended stack:
- Record your actual flows using Screen Studio or another recorder to capture real behavior
- Use Rotato to create 1–2 hero shots with device framing and motion
- Assemble everything in a simple editor (or a specialized app promo generator like Reely) to control pacing, text, and music
On Product Hunt, you're not bound by Apple's strict framing rules, so device shells and 3D motion become a strength.
3. Short social teasers (TikTok, Instagram, X)
Goal: Grab attention in the first 2 seconds and keep it under 15–30 seconds.
For social, your priorities shift:
- Vertical or square formats are often more important than strict native resolution
- Device-framed scenes from Rotato help your app look more productized in a noisy feed
- Combining fast cuts from raw simulator footage with 3D device hero shots works well
A flexible approach:
- Capture flows in the iOS Simulator via Screen Studio (or your favorite recorder)
- Drop the best sequences into Rotato scenes for a few "wow" shots
- Add kinetic text and sound in your editor of choice
4. Internal demos and investor updates
Goal: Speed > polish.
Here, pure screen recording usually wins:
- QuickTime + simulator is often enough
- Screen Studio adds clarity if you're sending to non-technical stakeholders (auto zoom and smoothing)
Rotato is overkill unless you're reusing the assets for public launch.
How automated promo generators fit in (like Reely)
There's a new category emerging: iOS app preview video generators that sit on top of your capture workflow and automate the edit.
Reely (disclosure: this is our product) is in that category.
- It's a native macOS editor that works directly with the iOS Simulator
- An agent/MCP tool lets your coding agent go from "build feature" → "build demo reel" in the same workflow
- It can recreate app flows in the simulator, record them, auto-cut dead air, and assemble:
- 10–20s feature teasers
- 30–60s full launch promos
Because Reely renders locally in 4K, supports multiple aspect ratios, and keeps every scene editable with kinetic typography and device motion, it can sit between:
- Simulator capture (like Screen Studio / QuickTime)
- Design-heavy outputs (like Rotato mockups)
To be precise about where it fits, since this is exactly where the Simulator boundary lands: Reely records the Simulator, so it is not the tool that produces your App Store Connect preview file. What it does produce is everything else from the same flow — the Product Hunt video, the landing page loop, the vertical social cuts, the changelog clip — plus the edit decisions (which beats, what order, how long) that you then re-shoot once on hardware for the ASC preview.
That gives you a workflow like:
- Use Simulator capture (possibly driven by an AI agent) as the single source of marketing footage
- Let a promo generator auto-edit and handle pacing, and let that edit define the story
- Shoot the App Store preview take on a connected device, following the story you already validated
- Use device-framed or 3D scenes sparingly, on the platforms that allow them
For a broader look at the full capture ecosystem, see our companion guide: .
Recommended toolchains for common use cases
To make this concrete, here are opinionated recommendations based on typical indie dev workflows.
If you only care about App Store previews
Use:
- Capture: A connected iPhone recorded through QuickTime Player
- Rehearse: The Simulator, to lock the flow and pacing before you shoot the real take
- Edit: A lightweight editor to trim to 15–30s, add text overlays, and hit Apple's exact resolution and codec
Avoid:
- Heavy device frames or 3D scenes (Rotato) in the core preview
- Shipping Simulator footage as the preview file itself
If you're launching on Product Hunt + App Store
Use:
- Capture: Simulator + Screen Studio (for smooth, clear demos) for everything marketing-facing
- Edit/promo: Reely to cut the narrative and generate the aspect ratios
- Device take: One QuickTime recording of the same flow off a connected iPhone, for the ASC preview
- Visual flare: Rotato for hero scenes in the Product Hunt video and social teasers
One story, one set of edit decisions, and a single hardware pass where Apple requires it.
If your focus is TikTok/Instagram/X teasers
Use:
- Capture: Any good recorder (Screen Studio, Kap, QuickTime) in higher resolution
- Visuals: Rotato for device-framed scenes and motion
- Assembly: Reely or another editor that supports vertical exports, text, and music sync
Here, App Store rules don't apply; prioritize thumb-stopping visuals.
FAQ: Rotato vs. traditional screen recorders for iOS UI demos
1. Is Rotato enough on its own for App Store preview videos?
No. Two things rule it out: Apple's guidelines call for simple, app-only content in plain native framing, and preview footage is meant to be captured off a real device connected to your Mac. Rotato scenes fail both tests. Use it for complementary marketing assets, and keep the preview itself a clean device recording.
2. Can I record an App Store preview video in the iOS Simulator?
Not per Apple's guidance. Apple's App Previews documentation says to capture app footage from the device using QuickTime Player with the device connected to a Mac, and App Store Connect's prerequisites for creating a preview list physical hardware — an iPhone, iPad, Apple TV, or Apple Vision Pro. Simulator is not among them.
Screenshots are the exception: capturing those from simulated devices is a documented, normal workflow. It's the preview video that's expected to come off a real device. Simulator recordings sometimes pass through unnoticed, but you're shipping off-spec metadata and betting your release timeline on it.
3. What's the simplest compliant workflow for iOS App Store previews?
The simplest path is:
- Rehearse the flow in the iOS Simulator until the pacing and beats are right
- Connect an iPhone and record the same flow with QuickTime Player (File → New Movie Recording, iPhone as source)
- Edit down to 15–30 seconds, add on-screen copy, and export to H.264 or ProRes 422 (HQ) at up to 30 fps, scaled to Apple's exact preview resolution for that device family
This aligns directly with Apple's published preview specifications.
4. When should I choose Screen Studio over free tools like QuickTime or Kap?
Choose Screen Studio when:
- You want auto zoom on actions and smoother cursor movement
- You need easy vertical exports for social platforms
- You want your capture to feel lightly edited without learning a full NLE
QuickTime and Kap are fine for raw captures, but Screen Studio saves time if you share demos often.
5. Where does a tool like Reely fit if I already use Rotato and a screen recorder?
Reely sits after capture and before design-heavy mockups:
- It turns Simulator footage (or even just a feature spec) into a structured reel with pacing, cuts, and kinetic text
- You can then layer in Rotato hero shots for launch trailers and social
It works from the Simulator, so it's aimed at your Product Hunt video, landing page, and social cuts rather than the App Store Connect preview file. What it gives you for the preview is the storyboard: once the reel tells the story well, you know exactly which 20 seconds to shoot on device.
6. Can I reuse the same footage for App Store, Product Hunt, and social?
Mostly, with one exception. The best practice is:
- Capture once from the Simulator at high quality, and generate every marketing edit and aspect ratio from it — Product Hunt, landing page, vertical social, docs
- Shoot the App Store preview separately from a connected device, following the same beats
You're reusing the story everywhere and re-shooting only the one deliverable Apple has rules about. That keeps your marketing aligned with your actual app behavior and still keeps App Store Connect happy.
Takeaways
- App Store previews are device-captured. Apple asks for footage recorded off a connected device via QuickTime, in plain native framing. Simulator recordings are fine for screenshots and for every other video you make — just not for the preview file.
- Rotato is a visual amplifier: perfect for social teasers, landing pages, and launch trailers, and the wrong tool for the preview itself.
- Traditional screen recorders (QuickTime, Screen Studio, Kap) cover both ends — the compliant device recording and the fast Simulator iteration.
- For indie devs and small teams, the winning stack is usually: Simulator capture → automated promo generator (like Reely) for the marketing cuts → one device take for App Store Connect → optional Rotato scenes for extra flair.
Your agent built the app. With the right workflow, it should also help build the demo reel — once — and let you reuse that story nearly everywhere.