Announce shipped requests
Use updates when a feature request is completed and the people who voted or commented should hear about it. The announcement can explain what changed and link back to the original context.
Changelog Software
Changelog software that tells users what shipped.
Publish changelog posts, connect them to shipped feature requests, and show users that their input changed the product.
app.gleam.land / My Project / Updates
3 linked draftsUpdates
ChangelogSearch updates...
Release queue
Drafts stay linked to shipped requests.
AllDraftScheduledSent
April product update
Release queue3 shipped requests
NNia
2Apr 24
In-app push for shipped work
ChangelogNotify requesters
KKai
3Apr 23
Custom update center
ChangelogAnnouncements · inbox API
SSam
4Apr 22
The problem
What breaks without a follow-up path
Shipping quietly wastes the best retention moment. If users never hear that their request shipped, they assume the product is standing still.
The solution
How Gleam handles it
Write updates from the same workflow that tracks feedback and roadmap status. Link shipped requests, target the right users, and keep a readable changelog for everyone else.
Capabilities
Built for the daily shipping rhythm.
Each product area is designed to stay lightweight enough for a small team, while keeping the data structured enough for automation, reporting, and agent-assisted work.
Changelog posts
Targeted announcements
Linked shipped requests
In-app push notifications
In-app update surface
SDK APIs for custom update centers
Email delivery
Draft-friendly updates
Use cases
Where Updates fits in the product loop.
These are the situations where the feature should be visible to users or connected to an internal product workflow.
Keep product momentum visible
A changelog gives prospective and current users a record of progress. It is especially useful for small teams that ship often but do not want every release to become a separate campaign.
Target the right audience
Not every update belongs in front of every user. Gleam can keep broad release notes public while using targeted notifications for requesters, followers, or users affected by a specific change.
Workflow
From signal to follow-through.
1
Draft
Start from shipped roadmap items or feedback that changed status.
2
Target
Choose everyone, specific followers, or users tied to a request.
3
Publish
Send the update and keep it visible in the public changelog.
Implementation
Operational details that matter before launch.
Gleam is designed to start small, but each feature still has a few product decisions worth making before inviting users.
Write from the user's outcome
Good changelog copy starts with what the user can do now, then explains the shipped request. Avoid internal project names unless they help users understand the change.
Connect updates to feedback
A shipped feature is more credible when the update links back to the request, voters, or roadmap context. That link turns release communication into proof that feedback was heard.
Use drafts for release coordination
Draft updates before marking work as shipped. That gives product, support, and engineering one place to review the copy before users receive notifications.
Outcomes
Why teams use Updates inside Gleam.
Visible product momentum
Better release communication
Reusable changelog history
More features