Feedback Dialog
Feedback dialog with a Bug, Idea, or Other type toggle, a message textarea, an optional screenshot attachment, and honest per-type routing copy.
Feedback dialog with a Bug, Idea, or Other type toggle, a message textarea, an optional screenshot attachment, and honest per-type routing copy.
The Application Collection unlocks the source for every Application block. All Access unlocks every Collection.
Already purchased? Log in
Feedback Dialog is the in-app feedback surface, shown as a static scrim-plus-card blueprint with the subtitle Tell us what you noticed. We read every message. A Bug/Idea/Other type toggle renders Bug as active (aria-pressed on each button), a free-text Textarea follows with the placeholder Describe what happened or what you would like to see, then a dashed attach-screenshot drop zone (PNG or JPEG, max 8 MB, Optional badge). The routing note at the bottom names the path: Bugs go straight to the on-call engineer. Ideas are batched into Monday's product review. Either way you get a reply within two business days.
Types are one const array with an active flag. The routing note uses strong tags with font-medium rather than generic body copy so the two paths read at a glance.
Reach for this block from a persistent feedback button in the app shell or help menu. Wire the active toggle state to local state, the file drop to your upload endpoint, and the Send feedback button to your feedback API with the selected type.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the general product feedback collector. Other feedback dialogs:
Tip: name where each type goes before the send button; honest routing copy is what makes users trust the form is actually read.