Home | Setup | Tutorial | Data Collection | API


What is PlayerZero?

PlayerZero brings the user directly to the developer when an issue happens within a web application. By reproducing experiences via simulation, the user can “take you” to their issue on your local environment — so you can validate your hunch and see it happen for yourself. Addressing production bug reports is frustrating and arduous; so much gets lost in the annoying game of telephone between those who feel (support) and those who fix (engineering).

PlayerZero gives you all the context you need when a user reports an issue(cursor movements, API mocks, etc) so you can debug fast and build faster. Take it one step further and share a replay with your team, communicate in context, and validate fixes.

PlayerZero has two unique use cases for logging user errors:

  1. Production usage
  2. Internal usage

How PlayerZero is used in your workflow (For Production Usage):

  1. A user runs into an issue on your web app.

  2. The user reports the issue to your team through a pre-existing channel. (Email, chat, phone call, etc)

  3. Your support team makes a note of the issue and reports the bug to the engineering team. (Jira, Zendesk, Slack, Teams, etc.)

  4. Behind the scenes, PlayerZero packages and logs the context for the entire user session leading up to the reported error.

    Frame 421.png

    The logged session includes context for the error, a “play” button for quick simulation as well as a sharable link for easy curation.

    Frame 419.png

  5. A developer picks up the link, dives into the session and runs the user session as a simulation in any environment; they can navigate step by step and interact with the browser like a real user session. This is more than a playback, this is a simulation.

    v7rsotgub8gzoytonhq9xzz5pfvq.gif

How PlayerZero is used in your workflow (For Internal Usage):

  1. A team member(CS, engineering, executive, etc) is using the product and finds a bug.

  2. The team member copies the session link by clicking the “copy session link” widget at the bottom right of the screen (this widget can be turned on/off for the environment level as needed).

    Frame 422.png

  3. The team member sends the link to the engineering team for review.

  4. Behind the scenes, PlayerZero packages and logs the context for the entire user session leading up to the reported error.

    Frame 421.png

    The logged session includes context for the error, a “play” button for quick simulation as well as a sharable link for easy curation.

    Frame 419.png

  5. A developer picks up the link, dives into the session and runs the user session as a simulation in any environment; they can navigate step by step and interact with the browser like a real user session. This is more than a playback, this is a simulation.

    v7rsotgub8gzoytonhq9xzz5pfvq.gif

Next step: Get setup to start using PlayerZero


More Pages:

Setup: Getting started with PlayerZero

Tutorial: Simulate a user experience with PlayerZero

Data: What PlayerZero collects and why

API