How to announce a new feature without interrupting your users
Most announcements arrive while the user is busy with something else. Size the message to the change, show it to the people it concerns, and give it an end date.

You shipped something. You want people to know. The user, meanwhile, opened your app to finish a task, and a window in the middle of the screen is now between them and that task.
Announcing a feature in the product is still the best place to do it, because that is where it gets used. The craft is in doing it at a volume that matches the change. This post gives you a ladder to choose from and the settings that keep an announcement from overstaying.
Match the size of the message to the size of the change
Think of in-app announcements as a ladder. Start at the bottom and climb only when the rung below is not enough.
| Rung | What the user experiences | Use it when |
|---|---|---|
| Badge | A small “New” label on a menu item or button. | The feature is easy to understand once found. |
| Highlight | One short tip pointing at the feature, shown once. | The feature needs a sentence of explanation. |
| Banner | A bar at the top or bottom of the page. | The news is not about one element, or has a deadline. |
| Popup | A window on the screen. | Everyone on that page needs to know before they continue. |
| Tour | A guided walkthrough of several steps. | The feature is a flow, and the user asked to be shown. |
Badge: let people find it on their own
A badge interrupts nobody. It marks the new thing where it lives and waits. In Stepsome, click + in the editor bar, choose New badge and click the menu item, button or heading. Pick a preset (New, Beta, Updated, Soon, Pro) or type your own text, and choose whether it sits after the text, before it or on the corner.
A badge is enough more often than teams expect. If the menu item is called “Reports” and the feature is reports, the label has already done the explaining.
Highlight: one sentence, once
When the feature needs a line of context, use a highlight. It points at the element with a short text and a Got it button. Three settings make it polite:
- When it shows: Once. Each visitor sees it a single time. After Got it, the ✕ or a click on the feature itself, it does not come back.
- Delay. Set how many seconds after the page opens it appears, so it does not land in the same instant as the page.
- Snooze. Let visitors put it off for 1 day, 3 days or 1 week instead of dismissing it. Someone in the middle of a task can say “later” and mean it.
You can also start a highlight On event: when the visitor clicks, types in, hovers over or submits an element you pick. A highlight about a new export option can wait until someone opens the export menu, which is the moment they care.
Banner: for news with a deadline
Some announcements are not about an element at all: a webinar, a price change, planned maintenance. A banner says it across the top or bottom of the page without covering anyone’s work.
- Start from a preset under Look: Announcement, Promotion, Important or Notice.
- With Push page, a full-width banner moves your page aside instead of sitting on top of it.
- Choose how it closes: Closed for good, Back on the next visit, or Can’t be closed. Keep the last one for things like scheduled downtime.
- The button can open a link, start a tour or close the banner.
Popup: only when everyone needs to know
A popup stops the user. That is justified when continuing without the information would cause confusion: the navigation moved, a workflow changed, something they rely on is going away.
If you use one, make it earn the interruption. A popup has room for blocks: an image, a GIF or short clip of the feature in use, a video embed and an extra button. A few seconds of the feature in motion explain more than a paragraph. You can record that clip from your own app; see How to make a demo video of your web app.
Then offer depth as a choice. Give a button the action Start a tour under Also, label it “Show me how”, and the walkthrough only runs for the people who ask.
Show it only to the people it concerns
An announcement about an admin setting is noise to everyone who is not an admin. Narrow it down:
- On pages. Limit the item to the part of the app the feature is in, with a pattern such as
/app/reports/*. - Audience. If your app passes traits, for example
Stepsome.identify({ plan: 'pro', role: 'admin' }), fill in a User trait and Is one of to show the item to those users only. Fill in both fields: a trait without values matches nobody. - Language. Duplicate the item per language and fill in Language on each copy, so nobody gets an announcement they cannot read.
Give it an end date on the day you make it
“New” stops being true. Announcements that never leave teach users to ignore the next one.
- For a badge, Hide after removes it after a date, and Hide once clicked removes it for a visitor as soon as they have clicked the element.
- For everything else, Schedule has From and Until dates, plus daily hours in each visitor’s own time.
A release checklist
- Decide the rung. Could a badge do it? If not, a highlight? Climb only as far as you need.
- Write one sentence that says what the user can do now, not what you built.
- Limit it to the pages and the audience it concerns.
- Set the end: Hide after, or a Schedule with an Until date.
- Preview it in the editor, set it to Published, download the site file and deploy.
- After a week, check how many people saw it and how many dismissed it early. How to measure user onboarding explains where those numbers come from.
Not sure which pattern fits a message that is not an announcement? Product tour, tooltip, highlight or checklist: which one when compares all eight.


