Blog
How to hear what people ask for, decide what to build, and tell them when it shipped: guides for teams that build software.
Roadmap and changelog
Changelog vs release notes: what each is for
The difference between a changelog and release notes, an example of each, how to write entries people read, and why the people who asked should hear first.
Elie BaierRead the postFeature requests
Duplicate feature requests: find them before votes split
How duplicate feature requests hide what users want most, how to catch them while people type, and what a merge must keep: votes, comments and followers.
Developers
Add a feedback widget to Next.js, with users signed in
Put a feedback widget in a Next.js app with your users already signed in: a route handler signs a short-lived token, and a client component hands it over.
Comparisons
Canny pricing explained: what tracked users cost you
How Canny's price grows with every customer who posts, votes or comments: its tiers, a worked example for an in-app widget, and what each plan includes.
Feature requests
Feature request template: a GitHub issue form you can copy
A feature request template that asks for the problem before the solution, as a GitHub issue form to copy, then the same questions for a feedback board.
Feature requests
GitHub issues for feature requests: enough, or add a board?
When GitHub issues are all you need for feature requests, when your customers need a board instead, and what keeping both in step should do for you.
Developers
MCP server for user feedback: what to let your agent do
Connect Claude Code, Codex or Claude to your users' feature requests through MCP: the tools an agent needs, what it should never do, and how to keep it safe.
Swingback is a user feedback tool to collect feature requests, plan the roadmap and announce what shipped.