-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session recording engagement improvements #5507
Comments
Potential approach suggestion by @joethreepwood:
|
I think the answer needs to be more "first-principles" here - our sessions page (which drives session recordings) bad and we don't know the proper use-case for it. Essentially #4884 While we can improve engagement here by "polishing" and adding features, unless we know what and for whom we're building we're kind of polishing a turd and making it harder to make large changes. :) Focussing on auxilary features just makes it seem like we're making progress when we're not. |
100% agreed! I just wanted to open this issue to document the discussion we have around this, but we definitely need to figure out the role of session recordings first. Will update once I have more context on that. |
This (and relevant context) was initially brought up by @joethreepwood on https://github.com/PostHog/product-internal/issues/127.
We've had feedback that session recording is an attractive feature to new users, but also that the experience isn't keeping users engaged. Feedback from a specific user: "Anything that summarizes is good. There's not enough time to watch them all."
This issue is intended as discussion for potential solutions on how to improve engagement for this feature. How can we enable users to keep coming back?
Part of "Shore-up Session Recording" theme from Diagnosing causes milestone (#5506)
The text was updated successfully, but these errors were encountered: