> For the complete documentation index, see [llms.txt](https://docs.supademo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.supademo.com/use-cases/marketing-and-growth/product-updates-and-releases.md).

# Product Updates & Releases

How to announce product updates with Supademo: interactive release demos embedded in changelogs, launch pages, and emails, translated and measured per feature.

A product update demo is a short interactive walkthrough that shows customers exactly what changed in a release, embedded wherever the announcement lives: the changelog, the launch page, the announcement email, the in-app banner. Release notes tell people a feature exists; an embedded Supademo has them clicking through it within the announcement itself, and its analytics tell you which updates customers actually tried.

## How to build it in Supademo

1. Record the new feature as a [guided demo](/create/by-demo-type/guided-screenshot-and-video-demos.md), 8 to 15 steps: the problem it solves, the workflow, the payoff. One feature per demo.
2. Open with a [chapter](/customize/chapters.md) naming what shipped and who it is for, and add an AI voiceover so the announcement narrates itself on mute-by-default surfaces.
3. Embed the demo in the changelog entry and launch post. For email, export a [GIF](/share/exports.md) of the key moment and link it to the demo, since email clients cannot render the embed.
4. For multi-feature releases, bundle the demos into a [Showcase](https://docs.supademo.com/share/multi-demo-sharing/showcase-collection) so customers pick the updates relevant to them instead of scrolling past the rest.
5. Reach existing users in the product: add the demo to your Demo Hub under a "What's new" category, or trigger it as an in-app tour.
6. For global customer bases, generate [AI translations](https://docs.supademo.com/customize/personalize/ai-translations-hub) so the same launch demo reads and speaks each market's language from one link.
7. Compare [analytics](/analyze/session-metrics.md) across releases: views, completion, and per-step drop-off per update tell marketing which stories land and show product early adoption signals.

Keep release demos ungated. Their job is awareness and adoption; a form in front of a changelog only suppresses both.

**Example:** This feature announcement demo walks through the improved product-addition experience in Shopify — showing the change in action, step by step, instead of describing it in a changelog paragraph.

[**See the Shopify feature announcement demo →**](https://app.supademo.com/demo/cm7m29mp01oafddumrtgx7ksh)

## Recommended setup

| Decision           | Recommendation                                                                                       |
| ------------------ | ---------------------------------------------------------------------------------------------------- |
| Demo type          | Guided screenshot or video demo, 8 to 15 steps, one feature each                                     |
| Sharing method     | Inline embed in changelog and launch page; Showcase for multi-feature launches; GIF export for email |
| Analytics to watch | Views and completion per release demo, per-step drop-off, UTM source of launch traffic               |

## Frequently asked questions

### How do I make an interactive changelog?

Embed a short Supademo in each changelog entry alongside the written notes. The embed works in any CMS or docs platform, the demo stays current because edits propagate to every embed, and per-entry analytics show which releases customers explored rather than scrolled past.

### Can I include an interactive demo in a launch email?

Not as a live embed, since email clients do not run embedded apps. Export a GIF of the demo's strongest moment, place it in the email, and link it to the demo's share link with UTM parameters. The animation earns the click; the demo and its analytics take over from there.

### How do I measure whether customers adopted a new feature announcement?

Watch the release demo's completion rate and per-step drop-off in Supa[demo analytics](/analyze/general-analytics.md), segmented by UTM source across changelog, email, and social. High views with early drop-off means the announcement pulled interest the feature story did not hold, which is a messaging fix, not a reach problem.