Publish icon rename and deprecation notices
API/DeveloperWhen an icon is renamed, removed, or aliased, I want a visible changelog entry and a machine-readable deprecation notice so CI pipelines do not break silently.
Capture requests, validate demand, publish your roadmap, and announce shipped work from one branded customer feedback hub.
5.0 rating from early adopters
Help us shape the future of the product.
When an icon is renamed, removed, or aliased, I want a visible changelog entry and a machine-readable deprecation notice so CI pipelines do not break silently.
Preset transparent background, padding, and square canvas sizes so exports are ready for decks and social previews without extra editing.
Keep filters in the URL so the page can refresh or be shared without losing the current search state.
See what we are working on and what is coming next.
Give new teams a guided checklist so they can invite users, customize branding, and publish their first request board faster.
Notify the right people when a request moves to complete.
Refine smaller-screen behavior without hiding the core information.
Release notes can include rich text and linked requests.
New updates and improvements to FeatureNest.
Updated the icon picker, added deprecation messaging, and linked the release to the customer requests behind it.
Patched the login flow and cleaned up the auth experience before the next release train.
Capture reproducible issues, screenshots, and the context needed to fix them fast.
Uploading a large PNG on Safari fails after selection; the input remains stuck while the request is submitted.
Filters drop out of the URL, making it hard to refresh the page or hand the exact state to another teammate.
The floating feedback widget sits too close to the footer and needs extra spacing on small screens.
Match the portal to your product with logo, colors, footer links, and custom domain controls.
JPG, PNG, GIF or WEBP. 1MB max.
This color will be used for buttons, links, and active states.
Feature requests, roadmap updates, changelog posts, and bug reports all connect to a single workflow that keeps your team moving.
FeatureNest helps your team reply faster, show progress clearly, and turn customer feedback into something people actually trust.
"FeatureNest turned scattered feedback into a single place our whole team can act on."
"We replaced three tools with one workflow and cut our response time in half."
"The public roadmap became the first page customers check when they want an update."
FeatureNest is designed to blend in. Maintain your brand identity while leveraging powerful feedback tools without writing complex custom infrastructure.
Authenticate users automatically using JWT. They never have to create a separate account to leave feedback.
Customize colors, typography, and layout to perfectly match your brand guidelines.
Embed the feedback portal directly within your application interface via an iframe or floating widget.
A few quick answers about how the home-page workflow works and what teams can do with it.
Customers can submit feature requests, report bugs, vote on ideas, follow updates, and read your roadmap or changelog in one place.
Yes. You can match the portal to your product with custom colors, logo, footer links, and a custom domain.
No. FeatureNest supports lightweight workflows so customers can interact without a separate product account.
Yes. You can write changelog entries, connect them to requests, and notify the people who asked for the work.
Yes. You can add an embeddable widget so users can send feedback without leaving your app.
Join hundreds of forward-thinking teams who use FeatureNest to build products their customers actually want.