EaseKitDocs
Tutorials · Your first product launch animation
Documentation

Your first product launch animation

From one prompt to a finished MP4: describe it, steer it with feedback, tune the feel and render a video.

In this walkthrough you make a short launch clip for a fictional app: the app icon lands, the name and a tagline follow, and a phone screen tilts into view. You'll write one prompt, steer the result with feedback chips and the strength dial, tune the overall feel, check quality, and render an MP4. It takes about fifteen minutes.

You'll useWhere
The chat and composerLeft side of the window
Feedback chips and the strength dialUnder the stage, and under each AI answer
Refine → Tuning and Camera⌥⌘4
Quality and Audit tabsInspector (⌥⌘5)
Render⌘E

1. Set up the session

  1. Press ⌘N for a new session.
  2. Open the composer's Add menu → Context and choose Product teaser. Leave it on Auto-detect if you prefer; EaseKit usually recognizes a teaser from the prompt.
  3. Optional: attach your real app icon with Add → Attach image… (images need an API key provider). Without one, the AI draws a placeholder mark.

2. Write the first prompt

Give the AI what moves, where it lives and how it should feel. Paste this, or write your own:

A 6-second 16:9 launch clip for “Tempo”, a focus timer app. The app icon drops in and settles with a soft spring, the name “Tempo” types on below it, then the tagline “Deep work, one block at a time” fades up. After a beat, a phone with the timer screen tilts up from below while the logo moves aside. Calm and premium, dark background, one warm accent color. Hold the last frame for a second.
  1. Press Return to send.
  2. Watch the chat: the AI plans, builds the layers, renders and runs the quality check. Fixes for any blockers happen before it answers.
  3. The stage plays version 1. Its score shows in the Versions strip.
Version 1 of the launch clip on the stage, with the score in the Versions strip

Read the change note under the answer and open Why it moves like this in the Layers tab. It lists the decisions the AI made, such as “the icon lands on a 0.55 s spring so it feels physical, not bouncy”.

3. Steer it with feedback

Play it a few times at 1×, then at 0.25× from the speed menu in the transport bar. Most first versions need one or two corrections. Use the chips for common symptoms:

If it feels…ClickWhat happens
Busy, everything at onceToo hecticMore stagger, calmer curves, less travel
SluggishFeels heavyShorter durations, livelier curves
FlatMore punchStronger accents and overshoot
Hard to readText too fast to readLonger holds on text
  1. Click Text too fast to read if the tagline disappears before you've read it. The chip is sent to the AI as a message.
  2. For something specific, type it: “The phone should arrive 0.3 s later and tilt less.”
  3. If a change went too far, click the change note under the answer. In How much of this change?, drag the dial to 60 % and watch the stage update, then click Keep 60 %.

4. Change one part precisely

  1. Click the tagline on the stage (click again to go inside a group, or ⌘-click to reach it directly).
  2. Press ⌘L. The composer shows Refers to with the layer's @id.
  3. Type “use the accent color and a slightly larger size” and send. Only the referenced layer changes.

To keep a layer exactly as it is through later AI turns, select it and click the lock icon (Lock for AI) in the inspector's header.

5. Tune the overall feel

  1. Press ⌥⌘4 to show Refine.
  2. Drag Speed to about 0.9× for a calmer pace, and Stagger up to 1.2× so the elements separate more.
  3. Watch the score next to the Tuning title update live.
  4. Click Apply. The tuned animation becomes a new version.

In the same panel, the Camera presets add depth. Try Dolly in for a slow move closer, or Hero tilt for a straightening tilt. Click Off to remove the camera again.

Refine: tuning dials and a camera preset on the launch clip

6. Check quality

  1. Open the Quality tab. The score ring and the six questions show what passes.
  2. Expand Findings. Each one has a suggestion, like “Hold the end frame at least 0.5 s”.
  3. Open the Audit tab. It replays the animation like a test run and marks jumps, hard starts and per-frame speed. Turn on Boxes and Paths to see them on the stage.
  4. Click Fix with AI to send the audit findings to the chat, or fix them by hand.

7. Render the MP4

  1. Press ⌘E to open Render.
  2. Set Resolution to 1× (the canvas is already 1920 × 1080; the sheet shows the pixel size).
  3. Set Frame rate to 30 (or 60 for very smooth UI motion) and Codec to H.264 so it plays everywhere.
  4. Check the estimate under the settings, for example “MP4 · 6.0 s · about 12 MB”.
  5. Click Render Video or press Return, and choose where to save it.
The Render sheet with video settings for the launch clip

You should now have an MP4 that plays in QuickTime, Slack or any social app. Press ⌘S to set a checkpoint on this version, so you can find it again.

Variations

  • Vertical cut: “Make a 9:16 version for stories” creates a new version at 1080 × 1920; the AI re-lays out the scene.
  • With music: add a track with ⇧⌘A, then ask “put the icon landing and the phone arrival on beats”. See A social loop with sequences, transitions and music.
  • Same feel, next clip: Session → New Session in Same Style (⇧⌘N) carries this clip's timing and palette into a new one.
  • GIF for Slack: Render → GIF (25 fps).