Slideshot applies the idea to web apps. Reely applies it to registered SwiftUI feature actions, native system transitions, and iPhone-focused output.
Mac app · Agent skill · No recording session
Slideshot shares Reely’s entire idea — an AI agent drives your app and hands back a finished MP4, no manual editing — but Slideshot records web apps in a browser. Reely does the same for native iOS in the Simulator. If you’re demoing a website or web app, Slideshot; if you’re demoing a native iOS/SwiftUI app, Reely. Both remove the recording-and-editing workflow.
What each workflow asks from you — and what comes out the other side.
| Capability | Reely | Slideshot |
|---|---|---|
| What you get | Auto-generated iOS demo reel | Auto-generated web demo video |
| Platform | iOS apps (screenshots, recordings, or SwiftUI in the Simulator) | Web apps (browser) |
| How it’s made | AI agent drives the app | AI agent drives the app |
| Polish | Automatic | Automatic |
| Text overlays | Authored step callouts, automatically timed | Intro cards and keyboard-shortcut overlays |
| Agent / MCP | MCP-native (Claude / Cursor / Codex) | MCP-native (Claude / Cursor / Codex) |
| Pricing | Free with a watermark; $9.99/mo or $89.99/yr removes it | Pay per attempt (~$0.90/recording) |
The practical differences you will feel every time you need a new demo.
Slideshot and Reely agree on the big bet: the agent that drives your app should also make the demo, without requiring a timeline pass. The split is primarily platform. Slideshot drives a browser, including authenticated product areas. Reely drives registered actions in an iOS Simulator build, so real SwiftUI navigation and system transitions play from app state a browser cannot reach.
You can’t point a browser automation tool at an iOS app. Reely builds an iOS harness, launches your feature in the Simulator, and drives the real navigation and state objects inside `withAnimation` so genuine native transitions play. It captures device-native portrait video and anchors the trim on a sync frame. That’s a fundamentally different pipeline from web recording.
Slideshot charges per recording (around $0.90 each, with bundles), so every attempt costs money and experimenting adds up. Reely uses an all-access subscription at $9.99 monthly or $89.99 annually, so it does not meter individual recording attempts. Many shipping-both-platforms teams could reasonably use Slideshot for the web app and Reely for the iOS app.
Free with every feature; exports carry a Reely watermark. $9.99/month or $89.99/year removes it.
Pay per use — about $0.90 per recording (10 for ~$9). No subscription. Note the unit: Slideshot charges per attempt, while an active Reely subscription does not meter recording or rendering attempts.
No — Slideshot drives a browser, so it records web apps. For native iOS/SwiftUI, Reely drives the Simulator instead.
It shares the same idea — an agent drives the app and returns a finished video — applied to native iOS. The capture pipeline (Simulator harness, native animations, sync-frame trim) is built specifically for iOS.
If you ship both a web app and an iOS app, that’s reasonable: Slideshot for the web demo, Reely for the iOS demo.
Describe the flow. Get a directed, branded, captioned video of your real iOS feature.
Free for Mac, every feature. Plans from $9.99/month remove the watermark.