How to Install the SnapState Chrome Extension
SnapState uses a Chrome extension so reporters can capture authenticated web app states from the browser they already use.
Before public launch
If SnapState is still in beta, use the beta signup flow instead of claiming the extension is publicly listed. Invite early users, share installation instructions directly, and collect feedback on capture reliability.
The public version of this page can be updated once the Chrome Web Store listing is live.
- Join the beta or request access.
- Install the extension from the approved distribution path.
- Pin SnapState in the browser toolbar for quick capture.
Capture your first state
Open an internal web app, staging environment, or test account. Click SnapState, review privacy settings, capture the page, redact sensitive information, and generate a link.
Share the link with one teammate and ask them whether the snapshot answered the questions a screenshot usually creates.
Permissions
The extension needs permission to read the active page when you capture. Richer diagnostics may require site-specific access so SnapState can observe recent network or console context.
Keep the permission explanation plain. Users should know what is captured and why.
Why this workflow is stateful
The common pattern across product, QA, support, design, and engineering is that the visible UI is only one part of the problem. The state behind it can include route, role, account data, filters, feature flags, viewport, recent requests, and comments from the person who found it.
That is why screenshots often create more messages. They preserve the appearance but lose the surrounding conditions that make the state actionable.
How to test this with your team
Pick one recurring workflow where screenshots routinely lead to questions. For one week, ask reporters to capture a SnapState when the state is visible and to add one sentence describing expected behavior.
At the end of the week, review whether the recipient had enough context to act. Look at clarification replies, repeated screenshots, unnecessary meetings, and whether the final decision stayed attached to the captured state.
Practical checklist
- Capture while the state is visible, before refreshing or navigating away.
- Write expected behavior and actual behavior in plain language.
- Redact fields the recipient does not need to see.
- Share the snapshot in the existing ticket or channel.
- Resolve comments or capture a new state when the issue changes.
Common mistakes to avoid
- Capturing too late, after the important state has disappeared.
- Sharing private data that was not needed for the decision.
- Letting the real discussion move back into chat instead of keeping it on the snapshot.