Replay Team

Replay Team

See what we're building
At Manoel's in-person onboarding in Rowarth, UK

People

What we're building

  • Android session recording

    There are many recording tools out there for web and different tools for mobile -- but few for both. So, we are considering a mobile recording solution for Android devices.

    Project updates

    No updates yet. Engineers are currently hard at work, so check back soon!

  • iOS session recording

    There are many recording tools out there for web and different tools for mobile -- but few for both. So, we are considering a mobile recording solution for iOS devices.

    Project updates

    No updates yet. Engineers are currently hard at work, so check back soon!

  • Error tracking

    We've seen multiple user signals that error tracking is a tool people want within PostHog. Network response status and speed, Errors, Events, and Replay overlap to give a full picture of what's happening in the user's app.

    The basics would be:

    • Exception autocapture in posthog-js
    • Users being...
    Project updates

    No updates yet. Engineers are currently hard at work, so check back soon!

Roadmap

Recently shipped

Mobile recording beta now available

We've now released our mobile recording features from alpha, into public beta. There's no need to opt-in, just follow the docs to get started.

Mobile recording is currently available for Android and iOS, and comes with a number of options. Namely, you can decide if you want to record in wireframe mode, screenshot mode, and whether to capture network requests. No matter what you choose, we default to a restrictive configuration with automatic masking.

Goals

🎯 Goal 1: People think of PostHog as a mobile solution

  • Mobile replay for React Native
  • Launch & charge for mobile replay
  • Lots of content on how to use PostHog on Mobile

🎯 Goal 2: Error tracking in beta

  • the top 5 features implemented
    • SDKs capture errors in one front-end and one back-end language (almost certainly JS and Python)
    • Stack traces are actionable and human-readable
    • Similar errors are grouped together
    • High-volume errors trigger the Alerting system
    • Integrated with other products such as Session replay
  • real customers using it and giving us feedback
  • integrated with CDP for notifications
  • integrated with replay for investigation

Goal 3: Hire two more people into the team

  • as a goal because hiring takes time
  • we want to add two people to the team so that we can stop choosing between what to work on

Follow along in our Q3 MegaIssue

Handbook

Areas of responsibility

  • Session Replay - recording browser or mobile sessions to be replayed later
  • Toolbar - a floating helper on your web app that helps to toggle feature flags, display heatmaps and provide contextual analysis
  • Mobile SDKs - the knowledge to level these up are in our team
  • Notebooks - a way to explore your data in a free format environment, for example to add comments to a session replay

A note on notebooks

(pun intended)

We own Notebooks the platform, but we aren't actively working on it while it beds in and customers show us what they use it for. We'll provide bugfixes to notebooks (the platform) and support to teams wanting to change their products in notebooks. But feature requests for existing products within notebooks (e.g. insights in notebooks) go to the team that own the product not to us.

Slack channel

#team-replay

Feature ownership

You can find out more about the features we own here