A feature announcement video should be 20 to 45 seconds and cover one feature: the problem it solves, the feature in use, and where to find it. Lead with what the user can now do, not with the name of the feature.
Release videos are easy to skip because they read like change logs. The ones people watch answer a single question: what can I do now that I could not do before?
The structure
- Result first (3 seconds). "Share a report in one click" beats "Introducing Report Sharing".
- Before and after (5 to 10 seconds). Show the old way briefly, then the new one.
- The feature in use (15 to 25 seconds). One clean path through the interface. Slow the cursor and zoom into the part that matters.
- Where to find it (3 to 5 seconds). A clear call to action, such as "Open Settings and turn it on".
Design tips
- Use motion to guide the eye to the new control, not to decorate.
- Keep text short and large enough for a phone.
- Match the animation style to your product, so the video feels part of it. See UI animation for app promo videos.
Reuse
Cut the same video into a square version for LinkedIn and a vertical one for Reels, Shorts and stories. For examples of UI animation, see my CashFish project.
Common mistakes to avoid
- Opening with the feature name instead of the benefit
- Showing every setting and option
- Using fast clicks viewers cannot follow
Frequently asked questions
How long should a feature announcement video be?
Often 20 to 45 seconds, covering one feature. If a release has several features, make one short video for each.
Should I use voice-over?
It helps, but add captions too, since many viewers watch without sound.
Where should I publish it?
In your release notes, in the product itself, on social channels and in emails to existing users.
Can you animate my feature screens?
Yes. See my UI animation approach.
