Offline votes disappear after relaunch
In Progress76 votes · General Feedback
76 votes7 repliesTeam replied
Feedback Board Software
Feedback board software for small teams and iOS apps.
Gleam gives users one clear feedback board for feature requests, bug reports, votes, comments, and status updates. Your team gets the signal in one place instead of stitching it together by hand.
Customer-facing feedback
A public conversation that stays structured behind the scenes.
gleam.land/feedback
Users can vote, comment, and follow progress without seeing the admin UI.
Search requests
Crash reports need automatic device context
Under ReviewThree affected builds with scoped device metadata.
23 votes4 replies
Dark mode for customer portal
Completed37 votes · Portal
37 votes12 replies
The problem
What breaks without a follow-up path
When feature requests land in app reviews, DMs, support email, and private notes, you cannot tell which issues are isolated complaints and which ones are blocking retention.
The solution
How Gleam handles it
Create a lightweight public or private feedback board for every project. Gleam groups similar requests, keeps votes and comments attached, and gives each post a status users can understand.
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.
Public and private boards
Votes and threaded comments
Merge duplicate requests
Board-level submission controls
Status and category tracking
Guest-friendly feedback capture
Use cases
Where Feedback Board fits in the product loop.
These are the situations where the feature should be visible to users or connected to an internal product workflow.
Replace scattered intake
Use a board when requests are split across support email, app reviews, chat, and private notes. A single feedback surface gives users a known place to submit ideas and gives the team one source of truth for triage.
Validate repeated demand
Votes, comments, and duplicate reports help separate one-off complaints from problems many users share. Product teams can review the request history before moving work into roadmap planning.
Close the requester loop
When a request changes status, the same post can carry the reply, roadmap link, shipped update, and follow-up notification. Users can see that their feedback remained attached to the work.
Workflow
From signal to follow-through.
1
Collect
Users submit a request from your portal, app, or SDK entry point.
2
Clarify
Votes, comments, duplicate reports, and board context stay attached.
3
Prioritize
The team sees which requests are urgent, repeated, or tied to churn risk.
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.
Choose public or private boards intentionally
Public boards reduce repeated support questions and let users vote together. Private boards are better for internal beta programs, sensitive B2B accounts, or feedback that should not expose roadmap direction.
Keep statuses understandable
A small status set is easier for users to trust. Use labels such as Open, Under Review, Planned, In Progress, and Completed before adding custom internal workflow language.
Start with one default board
Most early products should begin with one General Feedback board. Add separate boards only when categories need different moderation rules, owners, or submission guidance.
Outcomes
Why teams use Feedback Board inside Gleam.
Higher quality user signal
Less manual triage
Visible status for every feature request
More features