Browser Push Notifications
Reach users with timely updates when the app is not open.
What it adds
Web push subscriptions per device, with permission handled carefully and dead subscriptions cleaned up.
What your agent is told to do
5
What your agent is told to do
5-
1
Register a service worker and store each push subscription against the user, with the device it came from and when it was last used.
-
2
Ask for permission only after a user action that implies they want it — enabling push in settings, or opting in on a record. Never on page load.
-
3
Show your own explanation before triggering the browser prompt, and let the user decline yours without burning the browser permission, which they cannot easily undo.
-
4
Deep-link each notification to the relevant record and re-check authorization when it opens; the notification may be hours old.
-
5
Do NOT put private content in the notification body. It renders on a locked screen anyone can see.
Edge cases it handles
6
Edge cases it handles
6- Denied, dismissed, revoked, and unsupported are four different states and need four different UI outcomes.
- A subscription rejected by the push provider is dead — delete it rather than retrying it forever.
- A user with three devices should get one notification per device, and opening it on one should not leave it unread on the others.
- If the app is already open and focused on the relevant record, suppress the push and update in place.
- Push preferences must live on the existing notification preference model as another channel, not as an isolated toggle.
- Signing out on a device must remove that device's subscription, or the next user of that machine receives someone else's notifications.
Definition of done
8
Definition of done
8- Permission is requested only after an explicit user action, behind an in-app explanation.
- Subscriptions are stored per device and removed on sign-out.
- Denied, revoked, and unsupported states each have their own handling.
- Provider-rejected subscriptions are deleted automatically.
- Notifications deep-link and re-check authorization on open.
- Push is a channel on the existing preference model.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Prize Wheel Giveaway
Prize Wheel Giveaway
Run a spin-the-wheel giveaway where each entrant gets one spin and a recorded prize.
What it does
A giveaway with a wheel interface, one server-decided spin per entrant, and a durable record of every result.
How it works
- 1 Decide the outcome on the server before the wheel starts turning. The request returns a prize, the animation lands on it, and the client is only ever playing back a result it was given.
- 2 Model prizes with explicit weights and optional stock counts, and let an operator edit them without a deploy. A giveaway whose odds live in code cannot be corrected once it is live.
- 3 Tie an entry to an account where the app has one, and where it does not, combine the strongest identifiers available and treat a single spin as the hard limit across all of them.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/prize-wheel-giveaway
Poll Widget
Poll Widget
Ask a one-question poll anywhere in the app and show the results as soon as someone votes.
What it does
An embeddable single-question poll with a vote control and a results view revealed after voting.
How it works
- 1 Keep it to one question with a small set of options. The moment it grows a second question it is a survey and belongs in the survey feature instead.
- 2 Record the vote on the server and return the updated tallies in the same response, so the results the voter sees are the real counts rather than an optimistic local guess that may disagree after a refresh.
- 3 Hold voting open to signed-out visitors if the poll is public, and identify them well enough to prevent casual repeat voting without demanding an account for a single click.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/poll-widget
Announcement Bar
Announcement Bar
Put a timed message across the top of the site without shipping a deploy.
What it does
An operator-configured, dismissible strip at the top of public pages, with scheduling and a link.
How it works
- 1 Extend the existing Service Incident Banner rather than adding a second bar. It already handles scheduling, targeting, dismissal, and severity; this is a marketing-styled variant of the same component, and two independent bars will eventually stack on top of each other.
- 2 Let an operator set the message, an optional link, background and text colours, and a start and end time from an admin screen. Requiring a deploy to run a weekend promotion means it goes live late.
- 3 Insert the bar into the document flow so it pushes fixed headers and sticky navigation down. Overlaying it on top of the header hides navigation on exactly the pages people arrived on.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/announcement-bar
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.