Open joethreepwood opened 5 months ago
Example of one way this could be useful: We could encourage activation by linking directly to these templates from the onboarding emails. A one-click way to immediately show people rageclickers and new user replays.
One thing to call out here is that we specifically haven't worked on playlists as a team for a short while. At their core playlists are just a collection of saved filters with the added functionality of being able to pin certain recordings. We are curious to learn whether people can replace the "saving" functionality of pinning by adding individual recordings to Notebooks.
The idea of having named queries exactly like you're proposing is something we certainly need to improve for people. The simple filters was the first attempt at making it easier for people to find the sessions they want, I think the next chunk of work will be in helping people find the valuable sessions.
One of my goals this quarter is basically to make it easier for users to get started. I've created some best practices to help with that, one of which involves creating template functionality for each product.
You may be asking: Why does replays need templates?
Why does replays need templates?
Session replays has perhaps the most busy UI of all our products. Giving users a quick way to access some common queries as templates would help us demonstrate the value of the feature more quickly, and give us something we can link directly to in content.
No other replay tools I've seen include a template functionality, so this would also be a competitive differentiation. We're open source too, so this is something users could build on and add to.
Finally, if we have templates working across all features then we potentially become able to link them together in such a way as to make PostHog support many different metric frameworks at once.
You're probaby thinking: would templates for session replays look like? Glad you asked.
What would replay templates look like?
One proposal for replay templates is to create some default playlists for users which are pinned to the top of their playlist list from the start. These would be common playlists which enable them to effortlessly jump straight to things we imagine they'd want to check.
Initial template proposals:
console.error
in their console logs in the last 14 days)In order to collect the right event there seem to be two possible solutions:
Alternatives and feedback
Both are welcome from @PostHog/team-replay