# Reely docs (https://getreely.co/docs)

> Reely turns an app feature into a finished launch video from inside your coding agent. Start here: install, connect an agent, and make your first video.

Reely makes product videos for iOS apps. You stay in the coding agent you already use — you describe the video in plain English, and Reely records your feature, composites the look, and writes the file.

1. **You say** — “Make a reel of the onboarding flow, branded from our app.”
1. **Your agent** — Rebuilds the screens, directs the shot list, and calls Reely.
1. **Reely** — Records on a real iPhone screen, composites, and hands you the video.

Nothing leaves your Mac: the recording and rendering run locally, and the writing your agent does runs on your own agent subscription.

## Start here

- [Install & connect](https://getreely.co/docs/install) — Download Reely and wire it into your agent with one tap.
- [Your first video](https://getreely.co/docs/first-video) — One sentence to a finished reel, and what happens along the way.
- [What the agent asks](https://getreely.co/docs/agent-questions) — Three questions it must ask — answer them up front and skip the back-and-forth.

## Pick what you are making

- [Feature video](https://getreely.co/docs/feature-videos) — Your real feature, driven and recorded on a phone. A walkthrough people can follow.
- [Teaser](https://getreely.co/docs/teasers) — Motion graphics: copy beats, flying phones, a music bed. A launch spot.

## Then direct it

Everything about the look is a sentence, not a setting. The [Directing](https://getreely.co/docs/directing/flow) pages list every lever with the wording that reaches it — the flow itself, captions, branding, the phone, the camera, transitions, sound, and text.

> Reely is a paid Mac app. An active subscription includes the editor, agent workflow, rendering, and unlimited exports. See [Plans](https://getreely.co/docs/plans).

## Built for agents

These docs are AI-native. Every page is available as clean Markdown — append `.md` to any URL, or use the **Copy as Markdown** and **Open** buttons at the top of each page. Point an agent at `llms.txt` for an index of the whole site, or `llms-full.txt` for everything in one file.

| Endpoint | What it is |
| --- | --- |
| [/llms.txt](https://getreely.co/llms.txt) | One line per page — how an agent picks the right one |
| [/llms-full.txt](https://getreely.co/llms-full.txt) | Every page, in reading order, in a single file |
| `/docs/<page>.md` | That page as Markdown, served as `text/markdown` |

The Markdown is generated from the same source the page renders from, so the two never drift.

---

# Install & connect (https://getreely.co/docs/install)

> Install Reely on macOS and connect it to Claude Code, Cursor, Codex, VS Code, Gemini CLI and other coding agents with one tap.

Reely is a macOS app that drives your local Xcode and iOS Simulators. Setup is two steps: install the app, then connect the agents you use.

## Before you start

- A Mac with the Xcode 26 toolchain and iOS Simulators installed.
- At least one supported coding agent, installed and signed in.
- An active Reely subscription and the license key delivered after checkout.

## 1. Subscribe, install, and activate

Choose a plan on the Reely site. After checkout, the thank-you page delivers the Mac app and your license key. Drag **Reely.app** into Applications and launch it.

Click **Activate Reely** and paste the key from checkout. Reely requires an active license before it opens projects, installs the agent tools, records, renders, or exports.

![Reely welcome screen with the option to activate a license key](https://getreely.co/docs/license.avif)

## 2. Connect your agents

The welcome screen has a **Set up agents** card. One tap installs the video engine and wires it into every agent you pick — you never touch a config file or a terminal.

You will be asked for your password once, so the engine can be placed where your agents can reach it.

![Reely welcome screen with the Set up agents card](https://getreely.co/docs/install.avif)

The picker lists every agent it finds on your Mac, with the detected ones pre-selected. Then choose a scope: **Install Globally** for every project, or **Install for a Project…** for a single repo.

Supported agents: **Claude Code**, **Cursor**, **Codex**, **Windsurf**, **VS Code**, **Gemini CLI**, **Cline**, and **OpenCode**.

![Reely agent picker showing detected coding agents](https://getreely.co/docs/agents.avif)

| Scope | What it covers |
| --- | --- |
| Install Globally | Every project on this Mac. The engine goes on your PATH and each selected agent learns how to direct Reely. |
| Install for a Project… | One iOS project folder you pick. Same wiring, scoped to that repo — choose this if you would rather not touch your global agent config. |

> All writes are non-destructive — any agents, tools, or permissions you already had are preserved.

## 3. Check it worked

Open an iOS project in your agent and ask for a video. If the agent starts asking you which iPhone to use, the wiring is live — that question only comes from Reely.

Nothing happens? See [Troubleshooting](https://getreely.co/docs/troubleshooting).

---

# Your first video (https://getreely.co/docs/first-video)

> Make your first Reely video: what to say to your agent, what it does, how long it takes, and where the file lands.

Open your iOS project in your connected agent and describe the video. One sentence is enough to start.

**Prompt:** `Make a reel of the onboarding flow.`

## What happens next

1. **It asks you a few things.** Which iPhone, whether there is music, and how to record. See [What the agent asks](https://getreely.co/docs/agent-questions).
2. **It reads your feature.** It traces the real screens and the order they appear in, straight from your source.
3. **It rebuilds the screens.** A clean, self-contained copy of your UI — the same colors, fonts, icons, and copy — so the recording is deterministic and has no loading spinners in it.
4. **It shows you the screens before recording.** Look at them. This is the single biggest lever on quality: anything wrong here is wrong in the video.
5. **It records and composites.** The feature is driven on a real iOS Simulator with its own animations, then the look is composited on top.

## How long it takes

The first run on a project is the slow one — a cold build can take several minutes. Later runs reuse that build. Re-rendering the *look* of an existing recording is fast, because nothing has to be recorded again.

## Where the video lands

Wherever you ask. Say the path in the prompt, or let the agent choose a sensible one and tell you.

**Prompt:** `Make a reel of onboarding and save it to marketing/launch.mp4.`

## Then make it better

Watch it, then say what is off in plain language. The agent keeps the work it has already done and re-renders — you are not starting over.

- “Hold longer on the confirmation screen.”
- “Add captions, benefit-led, under six words.”
- “Brand it from our app and make it 9:16.”
- “The zoom is too aggressive — make it gentler.”

> If Reely refuses the command, activate your license or renew the subscription before retrying. Productive commands stop before recording or rendering begins.

---

# What the agent asks (https://getreely.co/docs/agent-questions)

> Reely requires your agent to ask three questions before it starts: which iPhone, whether there is music, and how to record. Here is what each answer changes.

Three decisions are yours, not the agent’s, so it has to ask before it starts. Answer them in your first prompt and it goes straight to work.

## Which iPhone

The hardware that appears in the video, and its finish. There is no default worth guessing — a phone in the wrong color reads as a stock mockup. See [The phone](https://getreely.co/docs/directing/device) for the full list.

**Prompt:** `Use an iPhone Air in Sky Blue.`

## Music, or none

The track’s tempo decides how long every scene is and where the cuts land, so it has to be settled before anything is timed — not added at the end. Give a path to an audio file, or say no music.

**Prompt:** `Use assets/track.m4a for the music.`

> Videos are silent unless you ask for sound, and bringing your own licensed track is the only option — Reely does not supply music.

## One take, or scene by scene

How the feature gets recorded. It changes what a retake costs later.

| Choice | Good for | Trade-off |
| --- | --- | --- |
| Scene by scene | Long flows, anything cut to music, work you expect to revise. | More recording passes up front; re-shooting one beat is cheap. |
| One continuous take | Short flows and quick first drafts. | Simplest to manage; any change re-records the whole thing. |

If there is music, prefer scene by scene — it lets each action land on a beat.

## Answer all three at once

**Prompt:** `Make a launch teaser for the checkout flow — iPhone 17 Pro in Cosmic Orange, music at assets/track.m4a, record each scene separately.`

_No questions asked — it starts immediately._

---

# Feature videos (https://getreely.co/docs/feature-videos)

> A feature video walks through your app doing the thing. How to ask for one, what makes it look real, and how to change it afterwards.

A feature video shows your app actually working: real screens, real transitions, in the order someone would meet them. It is the walkthrough — for a launch post, a docs page, an investor update, or a sales demo.

**Prompt:** `Make a reel of the checkout flow.`

## Why it looks real

Given your source, your agent rebuilds the screens — the same colors, type, icons, and copy — and Reely drives that rebuild with the app’s own animations. Nothing is faked frame by frame, so pushes, sheets, and springs move exactly as they do on device.

The rebuild also removes the things that ruin a take: network waits, spinners, empty states, and stale data. Every screen is settled before the camera rolls. To hold it to the real thing, see [Accuracy](https://getreely.co/docs/directing/accuracy).

> Source is not required. Screenshots or a screen recording work too — Reely builds the video around what you give it. Source just buys you real motion instead of stills.

## What you can steer

| Lever | Ask for it like |
| --- | --- |
| [The flow](https://getreely.co/docs/directing/flow) | “Skip the permission screen, hold on the receipt.” |
| [Captions](https://getreely.co/docs/directing/captions) | “Add captions in our own font.” |
| [Branding](https://getreely.co/docs/directing/branding) | “Brand it from our app.” |
| [Canvas](https://getreely.co/docs/directing/format) | “Make it 9:16 for Stories.” |
| [The phone](https://getreely.co/docs/directing/device) | “Put it on a 3D iPhone 17 Pro.” |
| [Camera](https://getreely.co/docs/directing/camera) | “Punch in on each tap, gently.” |
| [Transitions](https://getreely.co/docs/directing/transitions) | “Use a push between screens.” |
| [Sound](https://getreely.co/docs/directing/sound) | “Put our track under it.” |

## Changing it

Say what is off and ask again. Most changes are a fast re-render of the recording you already have — only changes to the flow itself (different screens, different order, different pacing) need a new one.

## Put it inside a teaser

The strongest launch videos are both: a [teaser](https://getreely.co/docs/teasers)’s copy and motion, with a phone that plays the real recorded feature instead of a static screenshot.

**Prompt:** `Make a launch teaser and show the real checkout flow on the phone.`

---

# Teasers (https://getreely.co/docs/teasers)

> A teaser is the launch spot: copy beats, a phone that moves, transitions and music. How it is built and how to direct one.

A teaser is the launch spot: cut beats of copy, a phone that moves, and a track underneath. It sells the idea rather than explaining the mechanics.

**Prompt:** `Make a 15-second launch teaser for our new checkout.`

## How a teaser is built

- **Scenes** play one after another. Each is a beat — a headline, a feature, the logo.
- **Layers** stack inside a scene: text, a phone, an image, footage, a shape, a background.
- **Transitions** join scenes, overlapping them so the cut is a move rather than a jump.
- **Music** underneath, with the cuts landing on the beat.

## The phone in a teaser

The phone can hold a still screenshot or play a real recording of your feature — the second is what makes a Reely teaser accurate where stock mockups are not. It can sit flat as a mockup or exist as 3D hardware in a studio, and it can move: entrances, exits, hero moves and multi-phone formations, all browsable in the app. See [Device motion](https://getreely.co/docs/presets/device-motion).

**Prompt:** `Open on the phone doing a Rise Yaw 360, then park it left with the copy beside it.`

## Cut it to music

Give the agent a track and it measures the tempo, the first beat, and the drop, then times every scene to that grid. Ask for the reveal to land on the drop and it will. See [Sound & music](https://getreely.co/docs/directing/sound).

## What you get

A video file **and** a Reely project you can reopen — scenes, timing, copy, colors and motion all still editable, previewed by the same renderer that produced the file. See [Editing in Reely](https://getreely.co/docs/editing).

## Which one do I want?

This is the only real difference. Both are made the same way, from the same inputs — your source, screenshots, or a screen recording — and both can carry music, run six seconds or sixty, and use every look control in [Directing](https://getreely.co/docs/directing/flow). Pick by what you want the video to say.

|  | Feature video | Teaser |
| --- | --- | --- |
| It says | “Here is how it works” | “Here is why you should care” |
| Shape | One continuous journey through the app | Cut beats: hook, product, payoff |
| The phone | Center frame, playing the flow | Moves, parks, sometimes several at once |
| The words | Captions narrating each step | Headlines making a claim |
| Reach for it when | Someone needs to understand the feature | Someone needs to notice the product |

> Not sure? Describe the video you want and let the agent pick the shape. You can ask for the other one afterwards from the same material.

---

# The flow (https://getreely.co/docs/directing/flow)

> Direct which screens appear in your app video, in what order, and how long each one holds — all in plain English.

The flow is the shot list: which screens the video walks through, in what order, and how long it rests on each one. It is the one thing worth being explicit about — everything else is a look you can change later.

## Name the journey

Say where it starts and where it ends. The agent traces the path between them through your real navigation, including the interstitial screens you forget about — permission sheets, confirmations, empty states.

**Prompt:** `Start at the empty cart and end on the order confirmation.`

> Every screen change is its own beat. A three-slide carousel is two swipes, not one — if a middle screen never appears in the video, that is the thing to point at.

## Cut what does not earn its place

- “Skip the login — start signed in.”
- “Don’t show the cookie sheet.”
- “Cut everything before the checkout button.”

## Control the pacing

Each beat has a moment before the action and a moment after it, so the eye can find the control and then read the result. Adjust either in words.

| You want | Say |
| --- | --- |
| More time on a result | “Hold longer on the confirmation.” |
| Less dead air | “Tighten the pauses, keep it moving.” |
| A calmer overall read | “Slow the whole thing down about 20%.” |
| A specific length | “Keep it under 15 seconds.” |

A screen with its own animation — a list staggering in, a sheet springing up — is held long enough for that animation to finish before the next beat starts. If something feels clipped, say so and the hold grows.

## Typing, scrolling, gestures

Text is typed into the real field, scrolls glide at a readable speed and can stop where you want, and swipes and long-presses play with their touch indicator.

**Prompt:** `Type “Weekend in Lisbon” into the search field, then scroll the results slowly to the third card.`

> Forms gate their own buttons. If a submit button looks dead in the video, it is because a required field was never filled — ask for the field to be filled first.

---

# Accuracy (https://getreely.co/docs/directing/accuracy)

> Make the video match your real app: give screenshots as the visual bar, review the rebuilt screens before recording, and correct what drifted.

The video is only as good as the screens it records. Two habits get you from “that looks like some app” to “that is our app.”

## 1. Give screenshots

Attach screenshots of the real screens. They become the bar: exact colors, spacing, corner radii, shadows, type, and — the thing code alone gets wrong — whether something is a floating card or an edge-to-edge sheet.

**Prompt:** `Make a reel of onboarding — match these screenshots exactly.`

Screenshots win over source when they disagree. Without them, the agent works from your code alone, which is usually right about structure and occasionally wrong about style.

## 2. Look at the screens before recording

Reely renders every screen as a still image before it records anything. Ask to see them. It costs one extra pass and it is the only moment where a wrong shade, a missing row, or a dropped progress bar is cheap to fix.

**Prompt:** `Show me the rebuilt screens before you record.`

## Correcting what drifted

Point at the specific thing. Vague notes produce vague fixes.

| Instead of | Say |
| --- | --- |
| “It looks off” | “The card background should be #F7F7F9, not white.” |
| “Wrong font” | “Headings are Inter Semibold, not the system font.” |
| “Something is missing” | “The progress bar at the top is missing on every screen.” |
| “Spacing is weird” | “The list rows are too tall — 56pt, not 72.” |

## Things worth calling out early

- **Persistent chrome** — a tab bar, nav header, progress bar or mini-player that must appear on every screen.
- **Custom icons** — anything that is not a system symbol, so it is not silently approximated.
- **Real copy** — if the mock invents wording, say the strings must come from the app verbatim.
- **Realistic data** — the names, prices, and avatars you actually want on camera.

---

# Captions (https://getreely.co/docs/directing/captions)

> Add self-narrating captions to an app video: how the copy is written, where captions sit, and how to set the typeface.

Captions narrate the video: a short line per key beat, timed to the action. Your agent writes the copy — it already knows what the feature does — so you steer the intent, not the wording.

**Prompt:** `Add captions that explain each step.`

## Steering the copy

Captions are short by design — under six words, so the bar never wraps into a paragraph — and they narrate only what is on screen. Tell the agent the register you want.

| You want | Say |
| --- | --- |
| Marketing punch | “Benefit-led captions, like a product launch.” |
| Plain and factual | “Neutral captions — describe what happens, no hype.” |
| Fewer of them | “Only caption the three most important beats.” |
| Your own words | “Use exactly these lines: … , … , …” |

> Captions appear automatically when the video is authored with caption copy. Say “no captions” to suppress them, or “add captions” to force them on.

## The typeface

Captions can be set in your app’s own font, a font file from your repo, or one of ten built-in faces.

| Choice | Ask for it like |
| --- | --- |
| Your app’s embedded font | “Set the captions in our app’s font.” |
| A font file in your repo | “Use Sources/DS/Fonts/Inter-Medium.ttf for captions.” |
| A built-in face | “Use Avenir Next for the captions.” |
| The system font | “Use the system font for captions.” |

- Helvetica Neue
- Avenir Next
- Futura
- Gill Sans
- Optima
- Georgia
- Palatino
- Baskerville
- American Typewriter
- Menlo

## Where captions sit

By default they sit as a lower third under the phone. On a 16:9 canvas they move **beside** the phone instead: it parks to one side and the copy takes the freed margin, alternating sides between groups of captions. That is what makes a landscape video read like a product page rather than a phone with a stripe under it.

**Prompt:** `Make it 16:9 with captions beside the phone.`

Colors follow your brand when the video is [branded from your app](https://getreely.co/docs/directing/branding), or you can name them outright.

---

# Branding (https://getreely.co/docs/directing/branding)

> Theme an app video from your product’s own colors, icon and font — automatically, or from a specific app bundle.

Reely can read your app’s own brand — palette, icon, and embedded font — and theme the video with it: the background canvas, the caption colors, and the shadow under the phone.

**Prompt:** `Brand the reel with our app’s colors and font.`

## Where the brand comes from

| Source | When to use it |
| --- | --- |
| The app being recorded | The default. Good enough for most videos. |
| Your shipping .app bundle | The truest match — it reads the exact palette and icon users install. |
| An asset catalog or icon file | When the built app is not around but the artwork is. |

**Prompt:** `Brand it from our shipping MyApp.app.`

## What branding touches

- **Background** — the canvas behind the phone is derived from the palette.
- **Captions** — bar and text colors, plus the app’s own font if it embeds one.
- **Contact shadow** — tinted to sit in the same light as the canvas.

> A dark app produces a **light** canvas by design — the phone has to separate from what is behind it. If you want dark-on-dark anyway, name the [background](https://getreely.co/docs/directing/background) directly; an explicit background always wins over the extracted one.

## Overriding pieces

Branding is a starting point, not a lock. Any piece can be replaced in the same sentence.

**Prompt:** `Brand it from our app, but use a graphite background and keep the captions white.`

---

# Background (https://getreely.co/docs/directing/background)

> Set the canvas behind the phone: seven built-in backgrounds, any hex color, a gradient, or your own image.

The background is the canvas the phone sits on. It is the fastest way to change the mood of a video, and the easiest thing to get wrong — it should separate the phone from the frame, not compete with the screen.

## Built in

- Default
- Aurora
- Ocean
- Graphite
- Sunset
- Coral
- Mint

**Prompt:** `Use the Graphite background.`

## Your own

| Kind | Ask for it like |
| --- | --- |
| A solid color | “Make the background #1E2A44.” |
| A gradient | “Use a gradient from #1E2A44 to #0B0E17.” |
| An angled gradient | “Gradient from #FF4DC4 to #7A4DFF at 45 degrees.” |
| An image | “Use marketing/bg.jpg as the background.” |
| From your app | “Take the background from our app’s colors.” |

> A background you name explicitly always wins over one derived from [branding](https://getreely.co/docs/directing/branding).

## Choosing one that works

- Light app → darker canvas. Dark app → lighter canvas. Contrast is what makes the phone read as an object.
- Keep it quiet. A busy photograph behind a busy UI reads as noise at social-feed size.
- If captions sit on the canvas, the canvas has to stay legible under text — see [Captions](https://getreely.co/docs/directing/captions).

---

# Canvas & format (https://getreely.co/docs/directing/format)

> Choose the output shape: native portrait, 9:16 vertical for social, or 16:9 horizontal with the phone centered.

The canvas is the shape of the finished file. Pick it by where the video is going — it changes composition, not just crop.

| Canvas | Size | Use it for |
| --- | --- | --- |
| Native portrait | The phone’s own size | Docs, changelogs, embeds, anywhere tall is fine. |
| Vertical | 1080 × 1920 (9:16) | Stories, Reels, TikTok, App Store previews. |
| Horizontal | 1920 × 1080 (16:9) | Landing pages, YouTube, decks, X posts. |

**Prompt:** `Make it 9:16 for Stories.`

## What changes with the shape

- **Vertical** keeps the phone tall and centered, with canvas above and below for captions.
- **Horizontal** centers the portrait phone on a wide canvas and gives you real margin either side — which is where captions go, beside the phone rather than under it.
- **Native** is the recording’s own size with padding around it: the tightest crop, the least room for copy.

> Deciding late is fine — the canvas is a re-render of the existing recording, not a re-shoot.

## Making the same video twice

**Prompt:** `Export this again as 16:9 for the landing page.`

---

# The phone (https://getreely.co/docs/directing/device)

> Pick the hardware in your video: a flat phone mockup or a real 3D iPhone in a studio, in any of its finishes.

Your recording plays on a phone. That phone can be a flat mockup — clean, fast, neutral — or real 3D hardware in a lit studio that can tilt, turn, and catch light.

## Flat or 3D

|  | Flat mockup | 3D hardware |
| --- | --- | --- |
| Reads as | A product screenshot | A product shot |
| Best for | Docs, changelogs, quick clips | Launches, hero sections, teasers |
| Can rotate and catch light | No | Yes |
| Flip transitions | No | Yes |

**Prompt:** `Put it on a 3D iPhone 17 Pro in Cosmic Orange.`

## Models and finishes

| Model | Finishes |
| --- | --- |
| iPhone 17 | Black · White · Mist Blue · Sage · Lavender |
| iPhone 17 Pro | Silver · Cosmic Orange · Deep Blue |
| iPhone 17 Pro Max | Silver · Cosmic Orange · Deep Blue |
| iPhone Air | Space Black · Cloud White · Light Gold · Sky Blue |

> Your agent has to ask which model and finish before it starts — say it in the first prompt to skip the question. See [What the agent asks](https://getreely.co/docs/agent-questions).

## The studio

A 3D phone sits in a lit product studio. You can direct the light and the ground the way you would a photo shoot.

| Knob | Ask for it like |
| --- | --- |
| Brighter or darker | “Brighten the studio a stop.” |
| Contrast | “Softer contrast — less punchy.” |
| Where the light comes from | “Rotate the light so the highlight runs down the right edge.” |
| Floating or resting | “Rest it on a surface instead of floating.” |
| Shadow | “Add a contact shadow under it.” |
| Focus falloff | “Add a little depth of field.” |
| Your own environment | “Light it with studio/warm.exr.” |

## Making it move

The phone can enter, move, and leave through named choreography — and one phone can become a whole formation. Browse the library with live previews in the Reely app, or see [Device motion](https://getreely.co/docs/presets/device-motion).

---

# Camera (https://getreely.co/docs/directing/camera)

> Ask for camera movement in an app video — punch-ins toward each tap — and tune how far, how fast, and how tight it frames.

App videos are **flat by default**: the whole screen, no camera movement. That is deliberate — a moving camera over a UI that is already animating reads as busy. Ask for movement when the UI is dense enough that the viewer needs help finding the point.

**Prompt:** `Zoom into each tap, Screen Studio style.`

## How it behaves

The camera moves like one calm operator who already knows the flow: it glides toward the control about to be touched, arrives before the tap, holds while the result reads, and keeps both the control and the touch indicator in frame. It punches in on real beats only, never on every step.

## Tuning it

| It feels | Say |
| --- | --- |
| Too aggressive | “Make the zoom gentler.” |
| Too twitchy | “Fewer punch-ins — only the important beats.” |
| Too slow to arrive | “Move to each target a bit quicker.” |
| Too tight | “Pull back — keep the whole card in frame.” |
| Like it is drifting | “Settle sooner and hold still while I read.” |
| Wrong subject | “Frame the Continue button, not the header.” |

> Beats that are very close together share one framing on purpose. If two taps in a row got a single move, that is why — spacing them out in the [flow](https://getreely.co/docs/directing/flow) gives each its own.

## Flat by choice

To go back to no movement at all, say so — the padded canvas, cuts, and captions all still apply.

**Prompt:** `Keep the camera flat — no zooming.`

---

# Transitions (https://getreely.co/docs/directing/transitions)

> The seven transition styles between screens and scenes — what each one means, and the restraint budget that keeps a video from looking cheap.

A transition hides the moment one screen becomes another and gives the cut a direction. Reely picks them by what the step means; you can override any of them by name.

| Style | What it says | Use on |
| --- | --- | --- |
| **Push** | We moved sideways in a stack | Navigation, tabs, pager swipes |
| **Wipe** | The state changed | Sheets, modals, mode switches |
| **Cross Zoom** | We dove into the detail | Opening a detail or dashboard |
| **Flip** | Look at the whole product | 3D videos only — the phone turns through its back |
| **Dreamy Zoom** | Something dramatic | An accent. One per video. |
| **Crosswarp** | Something dramatic | An accent. One per video. |
| **Ripple** | Something dramatic | An accent. One per video. |

**Prompt:** `Use a push between the list and the detail, and a wipe when the sheet opens.`

## The budget

Two quiet transitions beat five loud ones. Reely holds itself to at most two per video, at most one flip, and at most one accent — the rule that separates a launch video from a slideshow.

- Do not transition an in-place tap, a text entry, a scroll, or a toggle — nothing changed screens.
- Do not use the same style twice in a row.
- The flip is the biggest move there is. One, or none.

## Timing

| You want | Say |
| --- | --- |
| Calm and slow | “Gentle transitions.” |
| Crisp and quick | “Snappy transitions.” |
| A little overshoot | “Bouncy transitions.” |
| None at all | “Hard cuts between screens.” |

> Transitions can carry a sound. They are silent unless you ask — see [Sound & music](https://getreely.co/docs/directing/sound).

---

# Sound & music (https://getreely.co/docs/directing/sound)

> Add a music bed to a teaser, cut the video to the beat, and put sound effects on transitions.

Videos are silent unless you ask. Any video can carry a music bed — and once there is music, the cuts should land on it.

## A music bed

Give the agent a path to an audio file. It has to know the track **before** it times anything, because the tempo decides how long each scene is.

**Prompt:** `Use assets/track.m4a as the music bed.`

## Cutting to the beat

Reely measures the track — tempo, where the first beat lands, and where the drop is — and then times scenes in beats rather than seconds. Every cut lands on the music instead of near it.

| You want | Say |
| --- | --- |
| Cuts on the beat | “Cut every scene on the beat.” |
| The reveal on the drop | “Land the product reveal on the drop.” |
| Faster cutting | “Two beats per scene instead of four.” |
| The action on a beat | “Make the tap land on a beat.” |

> Bring your own licensed track. Reely does not supply music.

## Transition sound effects

Screen changes can carry a short effect — a **whoosh**, a **whip**, or a **ding**. Off unless you ask, because they date a video fast.

**Prompt:** `Add a whoosh on each screen transition.`

## Volume and ducking

- “Bring the music down — it is fighting the captions.”
- “Mute the music for the last scene.”
- “Fade the track out over the final two seconds.”

---

# Text & titles (https://getreely.co/docs/directing/text)

> Add kinetic type and title cards: animated headlines, emphasized words, and the wording that reaches each style.

Type is how a video says the thing the UI cannot. It appears two ways: **title cards** between beats, and **copy beats** inside a teaser scene.

**Prompt:** `Open with a title card that says “Checkout, rebuilt.”`

## How text animates

Text does not just fade in. It animates by a named style — words popping in sequence, lines rising, characters cascading, a headline resolving out of blur. Every style has speed, intensity, and weight you can push on. The full list is in [Text animations](https://getreely.co/docs/presets/text-animations).

| You want | Say |
| --- | --- |
| Words landing one by one | “Animate the headline word by word.” |
| A calm editorial rise | “Let the lines rise in softly.” |
| Something loud | “Slam the headline in.” |
| Lyric-style fill | “Fill the words in like karaoke, on the beat.” |
| No animation at all | “Just cut the text in — no animation.” |

## Emphasis

Single words can carry their own color or weight, so the line has a point rather than a uniform shout.

**Prompt:** `Headline “Checkout in one tap” — put the accent color on “one tap”.`

## Text inside an app video

A recorded feature video can carry kinetic type too — title cards between beats, and animated lines over the footage. It is off unless you ask, and it is a different intent from [captions](https://getreely.co/docs/directing/captions): captions narrate, kinetic type sells.

**Prompt:** `Add kinetic titles between the sections, medium intensity.`

## Keeping it readable

- One idea per beat. If a line needs a second read, it needs to be two beats.
- Hold long enough to read — roughly a third of a second plus a beat per word.
- Text over footage needs separation: a scrim, a darker grade, or a park to one side.
- One loud thing per scene. A slam headline over a spinning phone is two.

---

# Device motion (https://getreely.co/docs/presets/device-motion)

> Move the phone in your video by name — entrances, exits, in-scene moves, showcases and multi-phone formations, all browsable with live previews in Reely.

The phone can enter, move, and leave by name. Every move is calibrated so the default needs no tuning: say the name and it plays at its intended length and trajectory.

**Prompt:** `Bring the phone in with a Rise Yaw 360, then hold it on a slow Idle Drift.`

## Browse them in Reely

Open the **preset gallery** in the Reely app to see the whole library with a live preview of each move — rendered by the same engine that makes your video, not a canned clip. That is the fastest way to choose one, and the name you see there is the name you say to your agent.

> You do not need to memorize anything. Describing the motion works too — “bring it up from the bottom and settle”, “spin it once”, “park it left and hold” — the agent picks the closest move.

## What the library covers

| Group | What it is | Examples |
| --- | --- | --- |
| Entrances | How the phone arrives | Rise Up · Drop Bounce · Slingshot · Billboard Flip |
| Exits | How it leaves — usually the mirror of the entrance, a notch quicker | Sink Down · Blast Off · Fold Away |
| In-scene moves | What it does while the copy is read — parking, scanning, breathing, holding a lean | Closeup Scan · Hover Float · Breathe Zoom |
| Showcases | Hero moves that are the shot, not the accompaniment | Pirouette · Gimbal Arc · Carousel Orbit |
| Formations | One phone becomes many — spreads, orbits, cascades, handoffs | Fan deck · Orbit carousel · Colorway domino |

Moves are marked **2D** or **3D** in the gallery. 2D slides, scales and spins the flat mockup and works anywhere; 3D rotates real hardware in the studio and needs a 3D phone — see [The phone](https://getreely.co/docs/directing/device).

## Tuning a move

| You want | Say |
| --- | --- |
| A different length | “Make the Dolly In take two seconds.” |
| More or less of it | “Half the intensity on that Wobble Jelly.” |
| The other direction | “Slide it in from the right instead.” |
| A later start | “Hold, then start the move a beat in.” |
| More or fewer phones | “Fan deck with seven screens.” |

> A move overwrites the phone’s other motion for that scene, but keeps the model and finish you picked. A formation expands into individual phones you can then edit one at a time.

## Using them well

- One loud move per scene. A showcase spin under a slam headline is two things fighting.
- Formations are the loudest thing in the frame — one per video, with a scene to itself.
- Entrances and exits should agree: if it rose in, let it sink out.

---

# Text animations (https://getreely.co/docs/presets/text-animations)

> The thirteen ways type can animate in a Reely video — word pops, line rises, cascades, karaoke fills — and how to steer speed, intensity and weight.

Every text beat animates by a named style. Pick by the feeling you want, then push it with speed, intensity, and weight.

| Style | What it does | Feels |
| --- | --- | --- |
| **Word pop** | Words appear in sequence, each with a small pop | Energetic, conversational |
| **Line rise** | Lines rise into place behind a soft mask | Editorial, calm |
| **Blur in** | The line resolves out of blur | Cinematic, premium |
| **Char cascade** | Characters arrive one after another | Technical, playful |
| **Tracking in** | Letter spacing tightens as it fades up | Fashion, wordmarks |
| **Slam** | The line lands hard and settles | Loud, punchy |
| **Fade up** | A plain fade with a small rise | Neutral, safe |
| **Karaoke fill** | Color fills word by word | Musical, on-beat |
| **Slide up / down / left / right** | The block travels in from one side | Directional, clean |
| **None** | Cuts in at full opacity, cuts out | Hard, deliberate |

**Prompt:** `Headline in blur in, slow, low intensity.`

## The three dials

| Dial | Values | What it changes |
| --- | --- | --- |
| Speed | slow · medium · fast | How quickly the animation completes |
| Intensity | low · medium · high | How far it travels, blurs, or overshoots |
| Weight | light → heavy | The type weight the beat resolves to |

## Choosing

- Long headline? Use a whole-block style (**Line rise**, **Blur in**, a slide) — per-character styles turn a long line into a queue.
- Short and punchy? **Word pop** or **Slam**.
- Cutting to music? **Karaoke fill** on the beat.
- One loud style per scene. If the phone is doing a showcase move, let the type be quiet.

> Styles are also how [title cards](https://getreely.co/docs/directing/text) animate inside a recorded app video.

---

# Looks & effects (https://getreely.co/docs/presets/looks)

> Nine image effects — blur, tint, duotone, vignette, glow, grain, pixelate and chromatic aberration — for grading any layer in a video.

Any layer — footage, a photo, a shape, the phone — can be graded. Effects are how a stock screenshot starts to look like it belongs to your brand.

| Effect | Use it to |
| --- | --- |
| **Blur** | Push something behind the focal point, or open a scene out of soft focus |
| **Color** | Fix exposure, saturation and contrast — the everyday grade |
| **Tint** | Pull an image toward a brand hue |
| **Duotone** | Force a photo into two brand colors — the strongest unifier there is |
| **Vignette** | Darken the edges so the eye stays center |
| **Glow** | Bloom the highlights for a premium, lit feel |
| **Grain** | Break up flat gradients and add film texture |
| **Pixelate** | Obscure something, or go deliberately lo-fi |
| **Chromatic aberration** | A lens-fringe accent on a hard cut or an impact |

**Prompt:** `Duotone the background photo in our brand pink and near-black.`

## Grading footage to match

The most common use is making borrowed imagery agree with your palette: tint or duotone it, drop the saturation, add a vignette, and it stops looking like stock.

**Prompt:** `Desaturate the hero shot and add a soft vignette so the headline reads.`

## Restraint

- One or two effects per layer. Stacked effects read as a filter, not a grade.
- Never blur and fade the same thing at once — the fade does the work and the blur just costs clarity.
- Grain and glow are per-video decisions: apply them everywhere or nowhere, so scenes match.

---

# Editing in Reely (https://getreely.co/docs/editing)

> Open a teaser project in the Reely app to scrub, retime scenes, edit copy and motion, and re-export — previewed by the same renderer that writes the file.

A teaser comes back as a project you can reopen, not just a file. Double-click it and the whole thing is editable — and what you see while scrubbing is the same renderer that writes the export, so the preview is the video.

> Feature videos are rendered files. To change one, ask your agent again — see [Feature videos](https://getreely.co/docs/feature-videos).

## The timeline

One flat timeline holds every element of every scene, packed into shared lanes and colored by kind — phones, type, shapes, images. Drag a bar to slide an element in time, drag its edge to trim it, drag it across a scene boundary to move it. The music sits underneath as a single strip.

- The ruler scrubs; zoom stretches the time axis.
- Selecting an element moves the playhead into its window, so you always land on the frame you meant.
- Scene length is a menu choice in the header rather than a drag — it rebuilds the structure around it.

## What you can change

| Panel | Covers |
| --- | --- |
| General | Theme, background, the music track, volume and mute |
| Scene | Duration, the studio environment, exposure, contrast, shadow, depth of field, grounding |
| Element | Copy, font, weight, size, tracking, color, position, and the asset itself |
| Motion | How each element enters and exits, and the curve it uses |
| Keyframes | Direct control of opacity, position, scale, rotation and blur over time |

## The preset gallery

Every phone move and formation is browsable with a live preview, rendered by the export path rather than a canned clip. It is also the fastest way to learn the names — what you see here is what you say to your agent. See [Device motion](https://getreely.co/docs/presets/device-motion).

## Working with your agent

Editing by hand and asking the agent are not exclusive. A good loop: let the agent build the structure, tune the details by hand, then ask for the next structural change.

- **Undo/redo** covers your edits; **Save** writes back to the project.
- A second project can be merged in, appending its scenes to the end.

---

# Exporting (https://getreely.co/docs/export)

> Export a Reely video: video or GIF, the four codecs, canvas size, frame rate, and license requirements.

Export writes the finished file. It is included with every active Reely subscription, along with the editor, agent workflow, recording, preview, and rendering.

> There is no resolution picker: **video always exports at 4K**, scaled from your canvas. One less decision, and the file is always big enough for a landing page or a store listing.

## The settings

| Setting | Options | Pick |
| --- | --- | --- |
| Format | Video · GIF | GIF for a README or a chat; video for everything else |
| Codec | HEVC · H.264 · ProRes 422 HQ · ProRes 4444 | HEVC for quality per megabyte, H.264 for maximum compatibility, ProRes when it goes into another edit |
| Quality | Compact · Balanced · High | HEVC only — the others always render at full quality |
| Container | MP4 · MOV | MP4 unless you picked ProRes, which requires MOV |
| Canvas | A preset, or your own width × height | The shape of the frame — see [Canvas & format](https://getreely.co/docs/directing/format) |
| Frame rate | 24 · 30 · 60 | 30 for most things; 60 when motion is fast |

**Quality** only applies to HEVC, because it is the only codec with a meaningful size/detail trade-off: Compact is smallest and the one to share, Balanced keeps more detail at a moderate size, High is maximum quality and the largest file. ProRes uses its own fixed master profile, and H.264 always renders at full quality.

> GIF is a different animal: silent, downscaled and frame-capped on purpose so the file stays sendable. For anything that needs to look sharp, export video.

## Where each one goes

- **Social (Stories, Reels, TikTok)** — H.264, MP4, 9:16.
- **Landing page hero** — HEVC, MP4. Compact if it autoplays on the page.
- **App Store preview** — H.264, MP4, 9:16.
- **README or changelog** — GIF.
- **Handing to an editor** — ProRes 422 HQ, MOV.

## Exporting from your agent

You do not have to open the app at all — ask for the file and the path, and it is written when the render finishes.

**Prompt:** `Export it as H.264 to marketing/launch.mp4.`

## If export is refused

That is the license gate, not an export-format error. Activate your key or renew the subscription, then retry. Existing project files remain on your Mac. See [Plans](https://getreely.co/docs/plans).

---

# Recipes (https://getreely.co/docs/recipes)

> Complete prompts for the videos teams actually ship: App Store teasers, launch announcements, docs walkthroughs, social clips, changelog snippets and sales demos.

Six finished prompts. Each one answers the questions the agent would otherwise ask, so it starts immediately. Swap the specifics for yours.

## App Store preview

Vertical, captioned, branded, and short enough to hold attention in a store listing.

**Prompt:** `Make a 20-second App Store preview of the onboarding flow. 9:16, iPhone 17 Pro in Deep Blue, brand it from our app, captions that are benefit-led and under six words. No music. Record scene by scene.`

## Launch-day announcement

A teaser with the real feature playing on the phone — copy beats, one hero move, cut to the track.

**Prompt:** `Make a 15-second launch teaser for our new checkout, with the real checkout flow playing on the phone. iPhone Air in Sky Blue, music at assets/track.m4a, land the reveal on the drop. Open with a title card that says “Checkout, rebuilt.” Record scene by scene.`

## Walkthrough for the docs

Flat, quiet, native size. The video is a reference, so nothing should compete with the UI.

**Prompt:** `Make a walkthrough of creating a project, from the empty state to the saved project. Flat camera, no transitions, no music, native portrait, graphite background, plain neutral captions. One continuous take.`

## 9:16 social clip

One feature, one idea, fast enough to survive a feed.

**Prompt:** `Make an 8-second vertical clip of just the search-to-result moment. iPhone 17 in Sage, punch in on the search field, snappy transitions, one caption: “Find anything, instantly.” Music at assets/track.m4a.`

## Changelog snippet

Small, embeddable, and cheap to remake every release.

**Prompt:** `Make a 6-second clip of the new filter sheet opening and applying. Native portrait, flat camera, no captions, no sound. Export it as a GIF to docs/changelog/filters.gif.`

## Sales demo

Landscape, captioned beside the phone, and long enough to tell the whole story.

**Prompt:** `Make a 40-second walkthrough of the full admin flow for a sales deck. 16:9 with captions beside the phone, 3D iPhone 17 Pro Max in Silver resting on a surface, brand it from our shipping Admin.app, gentle transitions. Record scene by scene.`

> Long flows are worth recording scene by scene — a note from the room turns into one re-shot beat rather than a whole new take.

---

# Plans & licensing (https://getreely.co/docs/plans)

> What a Reely subscription includes, which commands need a license, and what happens when a subscription ends.

Reely is a paid Mac app with no free tier or trial. An active subscription unlocks the complete editor and agent workflow, including recording, rendering, and unlimited exports.

| Included | With a subscription |
| --- | --- |
| Rebuilding and recording screens | Unlimited |
| Authoring and rendering teasers | Unlimited |
| The Reely editor and live preview | Included |
| Every effect, preset, codec, and format | Included |
| Productive CLI and agent commands | Included |
| Exporting finished files | Unlimited |

Only setup and inspection remain available without a license: activation, installation, validation, marks, motion-preset listings, and frame measurement. Commands that create or change video output refuse before doing work.

## If your subscription ends

Your project files stay on your Mac and are not deleted. Renew the subscription to open, edit, render, or export them again.

## Separate costs Reely does not add

- **The writing.** Your agent does the authoring on your own agent subscription — Reely adds no model cost.
- **Your footage.** Recording and rendering happen on your Mac. Nothing is uploaded.

Current pricing is on the [main site](https://getreely.co/#pricing).

---

# Troubleshooting (https://getreely.co/docs/troubleshooting)

> Fixes for the common Reely problems: the agent cannot find Reely, a run hangs, the Simulator misbehaves, or the video is missing a screen.

The handful of things that actually go wrong, and what each one means.

## The agent does not seem to know about Reely

It was never connected, or it was connected for a different project. Open Reely, use **Set up agents**, and pick **Install Globally** so every project is covered. Then restart the agent so it picks up the new tools.

## The first run takes forever

A cold build of an iOS project takes minutes, and some agents give up waiting before it finishes. The work keeps going — ask again and the second attempt reuses the build. If your agent times out repeatedly, raise its tool timeout.

## Recording produces a frozen or black video

Usually a wedged Simulator from an earlier session. Quit the Simulator entirely and run again. Closing other Simulator windows before a recording also avoids a stuck recorder.

## A screen never appears in the video

A screen change was collapsed into one step — most often an interstitial sheet, or two swipes treated as one. Name the missing screen explicitly and ask for it to be its own beat. See [The flow](https://getreely.co/docs/directing/flow).

## A tap lands on a dead button

The button was disabled because a required field was not filled yet. Ask for every field to be filled before its submit step.

## The screens do not look like my app

Give screenshots and ask to see the rebuilt screens before recording. That single review catches almost every fidelity problem — see [Accuracy](https://getreely.co/docs/directing/accuracy).

## Export is refused

That is the license gate. Activate your key or renew the subscription, then retry. Existing project files remain on your Mac — see [Plans](https://getreely.co/docs/plans).

## Something else

Tell your agent what you saw and what you expected. It has the run output and can usually diagnose it faster than you can reproduce it.