EaseKitDocs
Tutorials · Reviewing with your team
Documentation

Reviewing with your team

Leave notes on the stage, share a link your team can comment on, and let the AI work through the feedback.

Motion review works best on the moment itself: “this card arrives too late”, pinned to the frame where it happens. EaseKit has comments on the stage, share links where viewers comment without an account, and one list that collects both. In this walkthrough you annotate your own draft, share it, collect feedback, and have the AI address it. About fifteen minutes plus waiting for your team.

1. Leave your own notes

  1. Open the session and click into the stage.
  2. Press ⌥⌘C (or click Comment in the toolbar, or choose Stage → Comment Mode). The pointer turns into a speech bubble.
  3. Scrub to the moment you want to discuss. Click to pin a spot, or drag to mark a rectangle. Playback pauses there.
  4. Type in the composer at the pin, for example “Does the title need a longer hold?”, and click Post (⌘↩). esc cancels.
  5. Press ⌥⌘C again to leave comment mode.
A comment area on the stage with its thread open

Comments show as numbered pins. Outside comment mode they appear within half a second of their moment; turn on View → Show Comments to see them all the time. Your name comes from Settings → General → Comments (empty uses your Mac user name).

  1. Press ⌘E to open Render.
  2. Turn on Include my comments (shown when the session has open stage comments). Your notes go to the new link with their pins and areas.
  3. Optional: turn on Share Link: allow viewers to download the project, so another EaseKit user can open it.
  4. Click Share Link. EaseKit uploads the animation and copies the link; the tile reads “Link copied to clipboard”.
  5. Paste the link in your team channel.
The share page with comments on the scrubber

3. What your team does

  • They open the link in any browser. The animation plays full-bleed with a scrubber and Replay.
  • They enter a name (remembered in their browser) and write a comment. It's pinned to the playhead.
  • Pin or mark an area lets them click a spot or drag a rectangle on the frame.
  • They can Edit or Delete their own comments from the same browser; edited comments say so.
  • They can Reply in any thread, and write @AI to ask EaseKit's AI; it answers while your app is open.
  • If you allowed downloads, they see Open in EaseKit and Download.

4. Read the feedback in EaseKit

  1. Open the Comments tab in the inspector. A badge shows how many are new.
  2. The list holds your stage comments and the share comments together, open ones first, each in timeline order. Filter by All, Open or Resolved.
  3. Click a comment. The playhead jumps to its moment; a stage comment opens its thread, a share comment flashes its pin or area on the stage.

The tab refreshes every 30 seconds while it's open, and every five minutes otherwise.

The Comments tab with stage and share comments

5. Let the AI address it

  1. When feedback arrives, the chat shows a card like “3 new comments on v2”. Click Address with AI — or write “Go through the open comments and address them.”
  2. The AI already sees every open comment on each turn: its time and text, the layers inside an area or under a pin at that moment, and the thread.
  3. It answers with a new version and replies in each thread, for example “Moved the title 12 pt up at 0.8 s — v3”, labelled EaseKit AI. Comments it fully fixed are marked Addressed.
  4. Review the result. Use the strength dial or ⌥⌘Z if something went too far.

6. Resolve and reply

  • Stage comments: click the pin and use ✓ to resolve, the reply field to answer (⌘↩), the pencil to edit your own text. All of it is undoable with ⌘Z.
  • Share comments: Resolve and Reply right from the Comments tab; your replies show on the share page.
  • Check what the AI marked Addressed, then resolve it — or reply if it isn't right yet.
  • In the links footer, Open as Owner (Resolve on the Web) opens the page with owner rights, so you can resolve and delete there too.
  • When the review is done, Stop Following Comments for that link.

7. Share the next round

Share a new link for the revised version. Each link stays tied to the version it was shared from (the Comments tab shows it as v5), so old feedback doesn't get mixed up with the new cut.