21–30 of 240 posts
Looks very useful for developers but I am not a fan of being on a website that has a keylogger installed onto it. I know this is not the first tool to do this, but the thought of every single thing I do getting stored by some third party tool is a bit scary.
Our company has just grown to where it isn't just some engineers and a few sales guys. Now we're trying to keep engineers working efficiently. / accurately, and the support team is ramping up. Making it easy for the sales or support guys to log a good ticket or bug is a never ending challenge. This looks like a great option.
I worked in support for ages and later moved to an engineering role, it's a mountain to climb to get good communication / reproducing things accurately enough for the engineers to really take action effectively.
"network tab" isn't it a security concern to record API calls? Also how future proof it is with Google changing Chrome addons permissions / API etc...?
Great concern! We do two things to address that: The first is nothing gets recorded and saved (or even sent to our backend) until the user actively chooses to log a bug. So it’s like actively choosing to save a HAR file when there’s a bug. The second is we scrub all network requests on the client side for anything that resembles PII or sensitive data. We just don’t want it on our servers. Is there anything else you t…
I have some feedback on your homepage & messaging.
Initially scrolling the home page I thought it was a tool for viewing customer bug sessions, similar to TrackJS or Sentry.
Reading this post it became clear this is for product managers and/or team members to file bugs. The line "Built for everyone" on the home page threw me off.
I think if you make the distinction that this is an internal tool for teams vs. an external tool for tracking customer issues it might help make this messaging clearer.
I'm not sure of your plans (perhaps you also intend for external users to use it) this was just my first pass impression.
I think this is a great tool. The structured format combined with the information provided by the extension are what make it valuable to me. The last minute feature is also nice as re-creating bugs can be a PITA.
As a dev, I would ideally also want to be able to view stack traces with source maps, but having a consistent structured format combined with the extension data is enough of a value prop to start using it.
"network tab" isn't it a security concern to record API calls? Also how future proof it is with Google changing Chrome addons permissions / API etc...?
Great concern! We do two things to address that: The first is nothing gets recorded and saved (or even sent to our backend) until the user actively chooses to log a bug. So it’s like actively choosing to save a HAR file when there’s a bug. The second is we scrub all network requests on the client side for anything that resembles PII or sensitive data. We just don’t want it on our servers. Is there anything else you t…
Edit: it looks like this is already the case!
Looks very useful for developers but I am not a fan of being on a website that has a keylogger installed onto it. I know this is not the first tool to do this, but the thought of every single thing I do getting stored by some third party tool is a bit scary.
I generally agree with you. I think there's a few important things to note:
- Since Jam is a browser extension, its functionality only applies to the user that installed it (i.e., only you, not everyone that visits website X) - All captured data stays locally in your browser until _you choose_ to submit a bug and its details* - You can choose which sites the extension is enabled on if you want to further limit the scope of functionality - We have some user preferences to enable/disable certain functionality of Jam already, and I'm confident we'll add more over time!
* to be fully transparent: we _do_ collect application telemetry so we can identify bugs and performance issues, but we take great care in reporting information that is centered around what our application is doing, not what it is capturing.
Nice work, looks like you've got some big names using it too, congrats. I have some feedback on your homepage & messaging. Initially scrolling the home page I thought it was a tool for viewing customer bug sessions, similar to TrackJS or Sentry. Reading this post it became clear this is for product managers and/or team members to file bugs. The line "Built for everyone" on the home page threw me off. I think if you m…
And that's really nice to hear, thank you so much! Stack traces with source maps. I agree. We integrate now with logging tools like Sentry and I wonder if we can just use sourcemaps from that.
Landingpage tip: Show your real product at least once, in a screenshot, in a video. Currently all images, videos are stylized which makes me think you are hidding something or at least I do not know what I will get.