There are three ways to tell users what changed in your product: an announcement, a changelog entry, and a What's new panel. They look similar and do different jobs. This guide explains which to use when. I am building JustOneCX (disclosure), so the examples use its features, but the split is useful with any tool.
What is each one for?
| Tool | For | Seen by |
|---|---|---|
| Announcement | Something a specific group should see now | The people you target, once |
| Changelog entry | The permanent record of what shipped | Anyone who looks |
| What's new panel | A way to find the record inside your app | Any signed-in user, any time |
An announcement is a nudge. The changelog is the record. The panel is the door to the record.
How does an announcement work?
An announcement is a message in your product: a new feature, a maintenance notice, a promotion. It can be a modal, a slide-out, a banner or a changelog popover.
- A banner is pinned to the top of the page and needs no target element, so it suits maintenance notices.
- A visitor who dismisses it does not see it again.
- It can have a call-to-action button that opens a link or starts a tour.
- You set a schedule and targeting: everyone, or a segment, and how often.
Use Preview in the builder to click through it before it goes live.
How does the changelog work?
A changelog is the list of what you published, newest first. Visitors can mark an entry helpful, which gives you a cheap signal about what to write more of.
You can show it three ways: embedded in your own site, on your own subdomain such as roadmap.yourcompany.com, or on a hosted page with no code. All three show the same content.
What does the What's new panel add?
It is an in-app panel with your changelog (or roadmap) and a badge for unread entries. A button needs no code:
<button data-justonecx-whats-new>What's new</button> The SDK sets an unread count on the button and adds a badge when there are new entries. It works on elements your framework renders later.
How should you combine them?
- Ship a feature. Write the changelog entry first. It is the permanent source.
- Tell the right people. If a group needs to know now, send an announcement to that segment with a button that opens the entry or starts a tour.
- Leave the door open. The What's new button lets anyone find the entry later.
Do not announce everything. Announcements stack up, and frequency caps exist for that reason. If every release is a modal, users learn to close modals.
A small checklist
- Is the message for a group or for everyone?
- Does it need action now, or is it just a record?
- Did you preview it?
- Is the changelog entry written before the announcement goes out?
What next?
Read the guides for announcements and the What's new widget. If you want to see the builder, you can book a demo.