Tell customers what shipped.
Publish releases to a public changelog, embed a what's-new feed in your product, and let BuildBetter tell the people who actually asked for each feature.
Shipping notes that reach someone
A changelog nobody reads is a changelog nobody reads.
Public changelog boards
Publish releases to a board customers can visit and follow. Run separate boards per product line when one feed would be noise.
Embed it in your product
Drop a lightweight what's-new badge and release feed into your own app with a public board key. Customers see what changed without leaving.
Tell the people who asked
BuildBetter matches shipped features back to the customers who requested them and drafts the message, so a release note becomes a real conversation.
New, Improved, Fixed
Label entries so customers can skim for what matters to them instead of reading everything to find the one line they care about.
Publishing is the start of the loop
Announcing a feature and telling the customer who asked for it are different jobs. The changelog handles the first. Releases handles the second, matching what shipped against every request in your feedback.
Details that decide whether it's used
Small things, but they're why embedded feeds get ignored.
Unread tracking
The embedded badge knows what a given user has already seen, so returning customers see what's new to them.
A board per product
Separate changelogs for separate products or apps, each with its own slug and audience.
Isolated styling
The embed won't inherit or fight your CSS, so it looks intentional inside your product instead of pasted in.
