The end-user recording aspect makes this an absolute non-starter for me. Nor would I use any product implementing your tool.
The way the industry is normalizing a complete abandonment of user privacy absolutely boggles my mind.
And not only do you want to watch everything I do (note I don't care whether the scope is just your app or my whole screen), you want to ship that off to your partners who sell you tokens.
To anyone considering this tool my advice is simple: First take a hard look at your processes and consider ways to become better at actually listening to your users.
I've filed countless bug reports over time. Some companies handle them with efficiency and gratitude. But I'm saddened at how many large corporations just lose them to the void - in some cases it becomes clear nobody gives a shit - and in other cases, it's despite the apparent best intentions of their support staff and developers. Eg. After finally managing to get the attention of an Amazon exec rep, a website bug I reported found its way to a developer. The bug was confirmed and both seemed genuinely grateful, but for whatever reason the bug still exists today - many months later - despite several "it should be fixed now" turnarounds. I can only guess their processes for testing and deploying a fix are borked.
Could you address this with an AI bandaid? Maybe. But in nearly every case I've seen - and I've consulted for decades in this space - it's a symptom of corporate culture or business process. Start there.
hey! thanks for the feedback. Only for web right now - mobile is on the roadmap.
As for privacy, I get where the concerns are coming from. But as somebody who has used session recording before - it is such a helpful tool to understand how your customers are using your product and struggling.
Also, all the data you get from a session recording - is data you already have (or could easily get).
As for the culture - I completely agree with you. This is why companies like Linear stand out (https://linear.app/now/zero-bugs-policy). One of my beliefs for starting Opslane is that we can get more companies to understand the bugs that matter and help improve the papercuts in their product.
Most people won't file bugs, they'll just churn. If you don't know what bugs they encounter then you'll never fix their churn. That some people file bugs does not mean that fixing those will fix most of your churn.
PostHog has this feature today. They have the concept of "Scouts", which are agents that scour ingested event data, replay sessions, and possibly also other kinds of data (though I haven't looked into what that means in practice), triage what they see, and put up PRs against them.
Update: I hope that didn't come across as a detraction; it's cool that you're building this. PostHog is open source, so if you haven't looked at their implementation yet, take a look, maybe it'll be useful to you!
Great product, is it only for web or does mobile work? How are you recording the sessions?
Also I wouldn't listen to people talking about privacy and so on, they're on your website and app, there is no suggestion of privacy just as when you walk into a store and they record you, excepting submission of sensitive information into the app. Many if not most conpanies already record sessions, that's why it's a feature in many tools like Posthog, Microsoft Clarity, Hotjar etc. And feeding them into AI directly is very useful to fix bugs as they occur without manually going through them.
As for privacy, I get where the concerns are coming from. But as somebody who has used session recording before - it is such a helpful tool to understand how your customers are using your product and struggling.
Also, all the data you get from a session recording - is data you already have (or could easily get).
The end-user recording aspect makes this an absolute non-starter for me. Nor would I use any product implementing your tool.
The way the industry is normalizing a complete abandonment of user privacy absolutely boggles my mind.
And not only do you want to watch everything I do (note I don't care whether the scope is just your app or my whole screen), you want to ship that off to your partners who sell you tokens.
To anyone considering this tool my advice is simple: First take a hard look at your processes and consider ways to become better at actually listening to your users.
I've filed countless bug reports over time. Some companies handle them with efficiency and gratitude. But I'm saddened at how many large corporations just lose them to the void - in some cases it becomes clear nobody gives a shit - and in other cases, it's despite the apparent best intentions of their support staff and developers. Eg. After finally managing to get the attention of an Amazon exec rep, a website bug I reported found its way to a developer. The bug was confirmed and both seemed genuinely grateful, but for whatever reason the bug still exists today - many months later - despite several "it should be fixed now" turnarounds. I can only guess their processes for testing and deploying a fix are borked.
Could you address this with an AI bandaid? Maybe. But in nearly every case I've seen - and I've consulted for decades in this space - it's a symptom of corporate culture or business process. Start there.
hey, thanks for the feedback.
hey! thanks for the feedback. Only for web right now - mobile is on the roadmap.
As for privacy, I get where the concerns are coming from. But as somebody who has used session recording before - it is such a helpful tool to understand how your customers are using your product and struggling.
Also, all the data you get from a session recording - is data you already have (or could easily get).
As for the culture - I completely agree with you. This is why companies like Linear stand out (https://linear.app/now/zero-bugs-policy). One of my beliefs for starting Opslane is that we can get more companies to understand the bugs that matter and help improve the papercuts in their product.
Most people won't file bugs, they'll just churn. If you don't know what bugs they encounter then you'll never fix their churn. That some people file bugs does not mean that fixing those will fix most of your churn.
Yes, but for many this still goes way too far privacy-wise to be a consideration.
> The end-user recording aspect makes this an absolute non-starter for me. Nor would I use any product implementing your tool.
Me as well, seems like we are losing that battle but I take the view I only lose when I stop fighting it.
PostHog has this feature today. They have the concept of "Scouts", which are agents that scour ingested event data, replay sessions, and possibly also other kinds of data (though I haven't looked into what that means in practice), triage what they see, and put up PRs against them.
Update: I hope that didn't come across as a detraction; it's cool that you're building this. PostHog is open source, so if you haven't looked at their implementation yet, take a look, maybe it'll be useful to you!
Thanks for the comment! I did come across posthog and it's a good validation that it is an important problem to solve!
Great product, is it only for web or does mobile work? How are you recording the sessions?
Also I wouldn't listen to people talking about privacy and so on, they're on your website and app, there is no suggestion of privacy just as when you walk into a store and they record you, excepting submission of sensitive information into the app. Many if not most conpanies already record sessions, that's why it's a feature in many tools like Posthog, Microsoft Clarity, Hotjar etc. And feeding them into AI directly is very useful to fix bugs as they occur without manually going through them.
hey! thanks for the feedback. Only for web right now - mobile is on the roadmap.
We are recording sessions using rrweb (https://github.com/rrweb-io/rrweb)
As for privacy, I get where the concerns are coming from. But as somebody who has used session recording before - it is such a helpful tool to understand how your customers are using your product and struggling.
Also, all the data you get from a session recording - is data you already have (or could easily get).
> Opslane is continuously learning about your product. Every investigation begins with what it knows about your product.
What does this mean in practice and how does it make your product better?
Since opslane watches all user session recordings, we know which screens and actions are more important. We use this to prioritize issues.