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!

Roadmap

Recently shipped

Client-side capture rate limiting added

We've added some new rate limiting systems to help to protect our users, ourselves, and (more importantly) our users, from abnormal client behaviour. That could mean anything from an accidental loop in the code, to someone running some strange scripts in the browser, to a bug.

This new rate limiting -- the details of which we're being deliberately coy about -- is relaxed enough that it should only trigger in one of these infinite loop or DDOS scenarios, but as always let us know if you have any feedback.

Goals

🎯 Goal 1: Quality and Consolidation for Session Replay (web & mobile)

Why?

We've done a lot of investigation and preparation work and we want to capitalize on that

  • Mobile replay out of beta for Android/iOS
  • Make capture and playback as complete, performant and easy as possible
  • Build the best UX for finding and playing recordings

🎯 Goal 2: Error tracking MVP

Why? PostHog is "The single platform to analyze, test, observe, and deploy new features". Having network timings, network payloads, and console errors in Session Replay is a great developer tool. We want to learn by doing to understand how we could capture and expose even more information here to help people dig into what is happening with their products

  • Building on top of the existing $exception ingestion
  • Getting it in the hands of real users, so that we can collect feedback on how to best solve their problems
  • This can't be a fully featured error tracking product at first release but it can be a valuable increment
  • see https://github.com/PostHog/product-internal/pull/569

Goal 3: Hire two more people into the team (1 full-stack/product and 1 mobile engineer)

Why? We want to do even more than we already do, but with just three engineers if someone were to be ill we lose a third of our throughput. Let's reduce the bus factor by adding 2 amazing new colleagues

Follow along in our Q2 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