Reactions
Let users react with emojis on changelog entries and comments — a lightweight way to signal nuance beyond a binary upvote.
Reactions vs. Votes
ProductBridge has two engagement primitives — they look similar but serve different purposes:
| Votes | Reactions | |
|---|---|---|
| Signal | "I want this" | "How this made me feel" |
| Per user | One per post (binary) | Multiple per entity, one per emoji |
| Where | Feedback posts, roadmap posts | Changelog entries, comments |
| Authentication | Required | Required (no anonymous reactions) |
| Best for | Prioritization | Nuanced sentiment |
Use votes when you want a clean prioritization signal — "how many people want this feature." Use reactions when you want richer feedback — "did this changelog land well? did people find it exciting, confusing, frustrating?"
The Reaction Set
ProductBridge ships with a fixed set of 10 emoji reactions, available everywhere reactions are supported:
| Emoji | Common Meaning |
|---|---|
| 👍 | Approval, agreement |
| 👎 | Disapproval |
| ❤️ | Love it |
| 😍 | Strong positive |
| 🎉 | Celebrating |
| 😂 | Funny |
| 🤔 | Thinking, considering |
| 😢 | Sad, disappointed |
| 🔥 | Excited, fire emoji |
| 🚀 | Excited to ship / use |
This set is the same across all reactable surfaces today. Custom emoji and per-surface visibility toggles aren't supported yet.
Where Reactions Appear
| Surface | Reactions On |
|---|---|
| Changelog entries | The post itself — readers can react to a release announcement |
| Comments | Individual comments on feedback, roadmap, or changelog posts |
Who Can React
Only signed-in users can react — anonymous visitors see existing reactions and counts but can't add their own.
This means:
- End users who created an account (via the public portal or identity verification) can react
- Team members can react on behalf of their workspace
- Anonymous portal visitors see reactions but are prompted to sign in if they try to react
One Reaction Per User Per Emoji
A user can attach multiple different reactions to the same entity, but only one of each kind. So:
- ✅ You can react with 👍 and 🎉 to a single changelog post
- ❌ You can't react with 👍 twice on the same post
Clicking your own existing reaction removes it (toggles off).
When to Use Reactions
Reactions shine when you want feedback richer than a binary vote but lower-effort than a comment:
Gauge how customers feel about each release. A flood of 🎉 reactions on a feature launch is meaningful sentiment data; a quiet 🤔 spike tells you something didn't land.
Let readers signal agreement without piling on duplicate "+1" comments. Reactions keep threads readable.
On internal/team-only boards, reactions are a quick way to indicate "I agree, no need to add a comment."
The 10-emoji set strikes a balance between expressiveness and scannability. If you have strong opinions about which emojis would serve your community better, let us know — we may add per-workspace customization in the future.
Last updated 4 days ago
Built with Documentation.AI