Add in-app feedback system (PoC) - #4212
Draft
gcsecsey wants to merge 3 commits into
Draft
Conversation
…gnostics Lets any user send feedback to the team from the crash screen, Help menu, or a new Settings tab, attaching app logs and version info by default. Feedback is tagged with the WordPress.com identity when signed in, or a stable anonymous installation id plus an optional email when not, so the team can follow up. The handler resolves identity in the main process so the flow also works on the crash screen, where the app's providers are unmounted. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DSA8NGg9t8wwwo72QjjcDa
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
This is a PoC, meant more as a discussion starter than a merge-ready change. We can and should iterate on this idea before landing this.
Related issues
How AI was used in this PR
I used Claude to iterate on the idea and to implement the client flow, the toolbar entry point, and the tests. I've reviewed the code myself and verified the full end-to-end round trip against my sandbox.
Proposed Changes
Studio users hit errors and crashes while often logged out, so we have no reliable way to identify them or follow up. The only feedback paths today are external GitHub issue links in the Help menu and a "contact support" link on the crash screen — high friction, no logs, no identity, no way to close the loop with the reporter.
This PR adds a low-friction, in-app feedback flow, which posts a structured, identity-tagged payload (with optional app logs + diagnostics) to a WordPress.com backend.
useAuth()and Redux hooks throw. The handler reads the auth token itself, and the renderer only sends user-authored content — so the same form works both in-app and on the crash screen.Reviewers should look most closely at the crash-screen provider handling, the default-ON logs toggle (privacy), and the identity/payload shape.
Testing Instructions
Full end-to-end needs the backend endpoint, see the testing steps of 228442-ghe-Automattic/wpcom. You can still verify the UI and the outgoing request shape:
npm start200and that the payload carries the expected identity + metadata