Are you wondering how you can improve your developer documentation and onboarding? If you’re a user experience researcher or developer advocate who wants to learn more about how developers use your product, you should use Paircast to test your developer experience.

Paircast is the first screen recording tool for developers. Paircast combines screen recording, code tracking, and bug reporting into a single app. For the first time, you can see a developer’s point-of-view as they get started with your product.

With Paircast, you can run remote unmoderated developer experience tests:

  • Guide new developers through custom tasks
  • Gain insight from video replays of comments, bugs, and fatal errors
  • Get a copy of every line of source code, time spent in each application, and voice transcripts from developers

Paircast was developed with help from companies like AWS, SAP, Sinch, and Cosiac. We created Paircast to help operate our own tests at Haxor, and now we’re releasing it for everyone! This guide will show you how you can run your own developer experience test with Paircast.

Try the finished example

For this tutorial, we’ll recreate a test of Tesseract.js. Tesseract.js is a javascript library for recognizing text from images. This is a nice quick example that won’t take more than 15 minutes.

Try the Tesseract.js Test

How it works

Developers download and install Paircast. Paircast acts like any normal screen recorder, but it also asks the developer to choose a directory where they code.

Developers will enter your Invite Key into the application. That key will pop up a prompt with instructions you configure. More on this in part 2.

Developers complete the task in their own IDE using their preferred tool-sets. You get to see how developers use your product in the wild!

As developers complete the test, they can record comments, bugs, and errors they encounter. Every issue they post will create a 2-minute highlight you can jump to in the replay.

Set up your own DX test

Ready to create your own test?

Continue to Part 2: Set Up