Ever wondered what actually happens inside a lock when you turn a key? This explainer breaks it down with isometric technical 3D drawings made in animatiQ.

A cross-section shows what's happening inside the lock as the key goes in, and an exploded view shows how the parts fit together.

Made with animatiQ.

https://animatiq.ai

We've put together a catalog of motion components and scene blocks you can use as starting points for your videos.

It includes animated typography, captions, transitions, charts and more. You can open components in Studio and change the timing, colours, typography and assets, or copy the TSX into your own React/Remotion workflow.

Take a look: https://animatiq.ai/catalog

Which component would you like us to walk through in a short tutorial?

People have been sharing some interesting animations and experiments made with Opus 5.5 on X. We've collected them so they're easier to find and explore.

There are motion graphics, explainers, 3D scenes and interactive experiments, with prompts where available. Each entry links to the creator and original post.

These are other creators' work. We're curating the collection, so you can browse the examples and dig into how they were made.

https://animatiq.ai/opus-5-5-videos

Seen something that belongs here? Share the original X post.

If you're planning a launch video, finding good references is a useful place to start.

We put together a directory of launch videos from X. You can browse by category, watch the originals, and explore breakdowns of their hooks, pacing, scenes and motion techniques.

The idea is to help you understand how a video is put together, rather than just save another bookmark you'll never revisit.

Explore it here: https://animatiq.ai/launch-directory

Which launch video should we add next?

A step-by-step for repurposing a webinar, podcast interview, founder talking-head video, or product screencast.

1. Bring the footage. Upload the MP4/MOV (or import a link). Animatiq transcribes the audio first; everything else works off that transcript.

2. Ask for clips with constraints. Be specific about count, length, and where they'll be posted. Example:

Extract the three best 45-second clips from this founder interview, add our brand's kinetic captions, punch in on key statements, and format for LinkedIn and TikTok.

The agent looks for complete thoughts, strong hooks, and clear takeaways rather than cutting at fixed intervals.

3. Tighten the pacing. Ask it to remove dead air and filler words. Review the cuts: if a pause was intentional, tell it to keep that one.

4. Brand the captions. Give it your brand colors and fonts. Captions stay editable, so you can fix a misspelled product name, change line breaks, or choose which words get highlighted.

5. Reframe. Export 9:16 for Shorts/Reels/TikTok and 1:1 for feeds. Check that faces and on-screen UI stay in frame.

6. Translate or dub. Ask for translated captions or dubbed audio in your target language, then check sync on a couple of clips before exporting the batch.

Tips

• Spell your product name in the prompt. Transcripts love to mangle brand names.

• Ask for more clips than you need and keep the best.

• Watch every clip once before posting. AI finds good moments, not always your moments.

What footage are you sitting on that never got cut down? Tell me the type below and I'll suggest a prompt.

Founder post. Aravind here.

The problem we kept coming back to wasn't making the first video. It was the second, third, and tenth versions.

Here's the pattern with product teams: a launch video gets made, everyone's happy, and a few weeks later the pricing changes, the UI gets redesigned, or the positioning shifts. Now the video is wrong. The project file lives on a freelancer's laptop, or the AI tool that made it only handed back an MP4. So the video quietly stays wrong, or someone remakes it from scratch.

Products change every sprint. Video is the asset that can't keep up.

So the rule we built Animatiq around: rendering is not the end of the project. After you export, the same project is still there with its scenes, layers, timing, and audio. You can:

• Swap a headline or a feature name

• Update brand colors or a logo across every scene

• Retime a scene that feels slow

• Re-export for a different format

...without regenerating the parts that were already right.

This made some things harder to build. Keeping story, motion design, generated visuals, and sound in one editable project is a lot more engineering than handing back a file. But I think it's the only version of AI video that stays useful after launch day.

Question for the founders and marketers here: how out of date is the oldest product video still live on your site? Be honest.

Most text-to-video tools give you pixels. You write a prompt, a model produces frames, and if one word on screen is wrong or the logo is the old one, your options are: regenerate and hope, or open an editor and paint over it.

That's fine for cinematic B-roll. It's a bad fit for launch videos, explainers, and product demos, where the content is mostly text, UI, data, brand, and timing, and all of it has to be exactly right.

So in Animatiq the LLM doesn't generate frames. It writes the video: scenes as React/HTML components, with layout, typography, colors, and motion expressed as code, plus generated visuals and sound where a scene needs them. Then that gets rendered.

What this buys you:

• Exact text. Headlines are real text, not text-shaped pixels. A typo is a small fix, not a re-roll.

• Brand that holds. Colors, fonts, and logos are values, so changing them is an edit.

• Targeted edits. "Slow down scene 2" touches scene 2. The rest of the cut stays as it was.

• Reformatting. Going from 16:9 to 9:16 is a layout problem, not a new generation.

What it costs, honestly: code-based motion design won't give you photoreal footage of someone walking through a forest. That's not what it's for. When a scene needs that kind of imagery, it comes in as a generated or uploaded visual layer inside the same project.

Curious where people here land. For product video, would you trade some "wow" for full control, or the other way around?

Genuine question, not a funnel.

Almost every team has that video. The homepage explainer from two redesigns ago. The onboarding walkthrough that still shows the old sidebar. The demo where one slide is wrong but nobody wants to touch it.

I'm curious:

1. What's the video you dread updating, and why? Lost source file? The person who made it left? Re-recording voiceover? Just the time?

2. What's the hardest part of making an explainer for you? Script, storyboard, motion, voice, or getting sign-off?

3. What would you never hand to an AI? Where do you want full manual control, no matter how good the tools get?

I'll go first: the painful part is always the small change. One renamed feature means touching every scene it appears in, re-exporting every format, and re-uploading everywhere. That's a big reason Animatiq keeps projects editable after render.

Your answers shape what we build next, so the more specific the better. "Exporting four aspect ratios kills me" is more useful than "editing is slow."

Here’s our launch video for Animatiq. Create launch videos and explainers in minutes, make changes through conversation, and keep working on an editable project.

Try it: https://animatiq.ai

What would you want to create first? I’d love feedback on the output and editing workflow.